I've got a few questions regarding the use of the 'games' user and group
for game packages. The resulting recommended practices will be posted
to the Extras/SIGs/Games wiki page.
Some games such as wesnoth and xpilot-ng come with server daemons. I
see three choices for the owner of these daemon processes:
1) root (ick!)
2) Allocate a separate '<gamename>' user for each package/daemon
3) Piggyback on the 'games' user
My preference would be #3. Are there any drawbacks to reusing the
'games' user to run various game daemons?
Two packages that I recently submitted for review ('rogue' and 'ularn')
use the 'games' group and a setgid executable so that all users have
access to the shared scoreboard file. Are there any security issues
that we need to be aware of when using setgid games?
Almost every package that I see in FE uses %defattr(-,root,root,-). Is
there any reason why we shouldn't be using %defattr(-,games,games,-) for
game packages (including documentation, manpages and such)?
With latest updates, I configured a printer while evolution and
openoffice were both opened.
The printer was configured as jet direct through System -->
Administration --> Printing menu.
After configuring and apply changes, in evolution I dinamically see
the new configured printer inside the printers list, in openoffice it
is not so.
Closing and reopening openoffice solves the problem.
[root@localhost ~]# yum install gnomebaker
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
--> Populating transaction set with selected packages. Please wait.
---> Package gnomebaker.i386 0:0.5.1-2.fc5 set to be updated
--> Running transaction check
--> Processing Dependency: libgstreamer-0.8.so.1 for package: gnomebaker
--> Finished Dependency Resolution
Error: Missing Dependency: libgstreamer-0.8.so.1 is needed by package
This is why I posted here. I am having trouble with gnome trash. ~.Trash
has items but the trash bin is empty. This only happen with current
rawhide. Anyone else see this?
> This is not a general Linux support list. Please, post to
> "fedora-list" or elsewhere.
> > Where are the file I delete from nautilus going? Because it's not going
> > in Trash.
> > --Louis
We're attempting to fix a problem in udev where /dev/cdrom creation is a
race between multiple optical devices in a system. To work around this
we will enumerate the devices as /dev/cdrom-hdc or /dev/cdrom-hdb.
However for compatibility reasons, we'll still create a /dev/cdrom, and
the last device found wins the race.
However in the udev package found in today's rawhide, /dev/cdrom is not
being created at all. This is fixed in a newer package, but did not
make the rawhide push. If you have issues with udev and /dev/cdrom,
please update to the udev package found here:
If you notice an application you use that depends on a /dev/cdrom entry,
please let us know so that we can investigate fixes for this improper
Release Engineer: Fedora
After updating my test3 rawhide to today updates, and after reading
about kexec, I decided to try it: impressive!
My system is a dual amd mp with serial ata pci card, scsi pci card and
other cards/devices, so bios startup phase is quite annoying,
especially at 01:39 AM... ;-)
And also my main bootloader is grub on CentOS 4 on first disk, with
option to chainload grub of FC5, installed in its root partition on
second hd... so two grub splash screens are too many at this time...
So my runnning kernel was 1955smp and just installed updates and in
particular the 1996smp kernel.
1) kexec -l /boot/vmlinuz-2.6.15-1.1996_FC5smp
root=/dev/sdb2 rhgb quiet"
to load new kernel into memory
2) shutdown 0
to put system in single user mode and stop various services
3) kexec -e
to reboot to the new loaded kernel
All has gone well with immediate boot up of the kernel!
Only one doubt:
at boot obviously the root filesystem appears uncleanly closed and so
I get the messages:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: sdb2: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 1263797
ext3_orphan_cleanup: deleting unreferenced inode 819283
ext3_orphan_cleanup: deleting unreferenced inode 819224
EXT3-fs: sdb2: 3 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Of course, as I was in init 1, "bowls were quite slow", but the orphan
clean up was not the marvellous message I like...
DO I have means to avoid this situation? Furthermore with FC5 you
don't get the option to check filesystem on unclean shutdown and so
only replay of journal is executed (correct?)
Thanks for your time
This is a daily reminder to everyone, but in particular people who
experience problems and report them before they read the mailing
list archives or query bugzilla for bug reports before filing a
We have switched from X.Org xkbdata to xkeyboard-config data, and
in the process the initial build that went into rawhide (1.0.1-5)
inadvertently had backward compatibility stuff disabled. This
problem has been resolved in 1.0.1-6, which should now be visible
in rawhide today.
If you experience *any* keyboard related problems or regressions
after updating, make sure you have xorg-x11-xkbdata-1.0.1-6 or
later installed before filing a bug report or asking for help.
After you're sure you have that version or newer installed, restart
X or reboot your system to ensure the changes take effect. You
may also need to reconfigure your keyboard with system-config-keyboard.
After verifying you're using 1.0.1-6 or later however, if you still
have problems, please do report them in bugzilla against the
"xorg-x11-xkbdata" component. I'll be reviewing xkbdata problems
closely between now and final build, and incorporating any fixes
I can muster up.
Thanks to everyone for testing the new bits out!
Mike A. Harris * Open Source Advocate * http://mharris.ca