Screensaver in KDE?
by Mike Leahy
Has anyone had a problem opening the Screensaver settings in the KDE
control settings? When I try to open it from the main desktop menu, I
get a dialogue saying:
"The specified library screensaver could not be found
The Diagnostic is:
libGL.so.1: cannot enable executable stack as shared object requires:
Permision denied
Possible reasons:
- An error occurred during your last KDE upgrade leaving an orphaned
control module
- You have old third party modules lying around."
Any clues as to what might cause and/or fix this? I did notice error
messages while running yum updates a couple days ago (sorry, I didn't
save them), but nothing seemed particularly fatal at the time, and the
updates seemed to complete regardless.
Mike
18 years, 2 months
rawhide report: 20060130 changes
by Build System
Updated Packages:
xorg-x11-server-1.0.1-1
-----------------------
* Wed Jan 18 2006 Mike A. Harris <mharris(a)redhat.com> 1.0.1-1
- Updated to xserver 1.0.1 from X11R7.0
Broken deps for i386
----------------------------------------------------------
GFS-kernel - 2.6.14.1-20051219.162641.FC5.9.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
GFS-kernel - 2.6.14.1-20051219.162641.FC5.9.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
GFS-kernel-smp - 2.6.14.1-20051219.162641.FC5.9.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
GFS-kernel-smp - 2.6.14.1-20051219.162641.FC5.9.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
cman-kernel - 2.6.14.1-20051219.162641.FC5.10.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
cman-kernel - 2.6.14.1-20051219.162641.FC5.10.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
cman-kernel-smp - 2.6.14.1-20051219.162641.FC5.10.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
cman-kernel-smp - 2.6.14.1-20051219.162641.FC5.10.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
dlm-kernel - 2.6.14.1-20051219.162641.FC5.8.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
dlm-kernel - 2.6.14.1-20051219.162641.FC5.8.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
dlm-kernel-smp - 2.6.14.1-20051219.162641.FC5.8.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
dlm-kernel-smp - 2.6.14.1-20051219.162641.FC5.8.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
gnbd-kernel - 2.6.14.0-20051108.134753.FC5.14.i686 requires kernel = 0:2.6.15-1.1826.2.10_FC5
gnbd-kernel - 2.6.14.0-20051108.134753.FC5.14.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5
gnbd-kernel-smp - 2.6.14.0-20051108.134753.FC5.14.i686 requires /lib/modules/2.6.15-1.1826.2.10_FC5smp
gnbd-kernel-smp - 2.6.14.0-20051108.134753.FC5.14.i686 requires kernel-smp = 0:2.6.15-1.1826.2.10_FC5
Broken deps for ia64
----------------------------------------------------------
rgmanager - 1.9.31-3.ia64 requires ccs
Broken deps for ppc
----------------------------------------------------------
ccs-devel - 1.0.2-3.1.ppc requires ccs = 0:1.0.2-3.1
gulm - 1.0.4-2.FC5.1.ppc requires ccs
Broken deps for ppc64
----------------------------------------------------------
cman - 1.0.3-5.FC5.ppc64 requires cman-kernel-modules >= 0:2.6.11
dlm - 1.0.0-7.FC5.ppc64 requires dlm-kernel-modules >= 0:2.6.11
emacs - 21.4-5.ppc64 requires fonts-xorg-75dpi
gnbd - 1.0.1-2.ppc64 requires gnbd-kernel-modules >= 0:2.6.11
Broken deps for s390
----------------------------------------------------------
systemtap - 0.5.3-2.s390 requires kernel >= 0:2.6.9-11
systemtap - 0.5.3-2.s390 requires kernel-devel
Broken deps for s390x
----------------------------------------------------------
libvte-java - 0.11.11-7.s390x requires libgtkjava-2.8.so()(64bit)
libvte-java - 0.11.11-7.s390x requires libgtkjni-2.8.so()(64bit)
systemtap - 0.5.3-2.s390x requires kernel >= 0:2.6.9-11
systemtap - 0.5.3-2.s390x requires kernel-devel
Broken deps for x86_64
----------------------------------------------------------
GFS-kernel - 2.6.14.1-20051219.162641.FC5.9.x86_64 requires kernel = 0:2.6.15-1.1826.2.10_FC5
GFS-kernel - 2.6.14.1-20051219.162641.FC5.9.x86_64 requires /lib/modules/2.6.15-1.1826.2.10_FC5
cman-kernel - 2.6.14.1-20051219.162641.FC5.10.x86_64 requires kernel = 0:2.6.15-1.1826.2.10_FC5
cman-kernel - 2.6.14.1-20051219.162641.FC5.10.x86_64 requires /lib/modules/2.6.15-1.1826.2.10_FC5
dlm-kernel - 2.6.14.1-20051219.162641.FC5.8.x86_64 requires kernel = 0:2.6.15-1.1826.2.10_FC5
dlm-kernel - 2.6.14.1-20051219.162641.FC5.8.x86_64 requires /lib/modules/2.6.15-1.1826.2.10_FC5
gnbd-kernel - 2.6.14.0-20051108.134753.FC5.14.x86_64 requires kernel = 0:2.6.15-1.1826.2.10_FC5
gnbd-kernel - 2.6.14.0-20051108.134753.FC5.14.x86_64 requires /lib/modules/2.6.15-1.1826.2.10_FC5
18 years, 2 months
Hibernate issues on FC5T2...
by Mike Leahy
Hello list,
I've played around a bit with FC5T2, and I found that the hibernate
sort-of worked. On my first attempt it wouldn't un-hibernate. At some
point (after a reinstall) it worked fine. Since then, I have performed
all the updates using yum (I have updated everything as of 5 minutes
ago), and I've started using KDE for my desktop. However, when I try to
hibernate now, I get a blank screen, which eventually prints errors
indicating some problem accessing the fd0 device. I don't have a floppy
disk on my laptop, so the fact that it can't access it is no surprise.
If I wait long enough, I'm returned to the desktop with the following
output:
sudo /usr/sbin/pm-hibernate
GNU GRUB version 0.97 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> savedefault --default=0 --once
grub> /usr/sbin/pm-hibernate: line 24: echo: write error: No such device
Would this be related to any of the updates, and/or my switch to KDE? I
tried a bit of hacking around with the pm-hibernate script, that
certainly didn't improve anything. Any suggestions?
Mike
18 years, 2 months
nightly boot.iso installer hangs at step network
by David Timms
On a HP compaq nx9000 notebook, 512M ram, in text mode, using boot.iso
(from CD) (2005-01-30 ?) the installer hangs during/after the:
moving (1) to step networkdevicecheck
moving (1) to step network
This is occurring with either the network is set to dhcp or static
address in the installer. The terminal on Alt-F2 is still responsive:
top -d 1 shows
STATUS RSS PPID %CPU %MEM COMMAND
R 844 476 0.9 0.1 top
S 1972 334 0.0 11.3 anaconda
After ten+ minutes, there is no change.
18 years, 2 months
Question regarding openGL screensavers (with xorg ati driver)
by Andy Burns
Running current rawhide, with xorg drivers for my ATI card, I have
xscreensaver + extras + glextras installed, regardless of whether I use
xorg vesa drivers, xorg ati drivers or xorg ati drivers with EXA
extensions I can't get any of the openGL screensavers to start they all
give messages similar to ...
X error in glplanet:
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Serial number of failed request: 111
Current serial number in output stream: 112
I was beginning to think this might only be expected to work with the
ATI proprietary drivers, however yesterday I was tunneling X over SSH to
my laptop running cygwin/X and I noticed that the openGL screensavers
all worked that way (and with quite an impressive speed considering the
tunnel was over WiFi)
Is it expecting too much of the current xorg drivers to support GLX (I
thought MESA should at least step in as a software renderer as last
resort) or should I bugzilla this?
18 years, 2 months
SELinux still giving errors on boot-time
by Roger Grosswiler
Still there, see this:
SELinux: Completing initialization.
SELinux: Setting up existing superblocks.
SELinux: initialized (dev dm-0, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses
genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses
genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses
genfs_contexts
SELinux: initialized (dev inotifyfs, type inotifyfs), uses
genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
audit(1138275326.096:2): avc: denied { write } for pid=387
comm="restorecon" name="[982]" dev=pipefs ino=982
scontext=system_u:system_r:restorecon_t:s0
tcontext=system_u:system_r:restorecon_t:s0 tclass=fifo_file
audit(1138275326.108:3): avc: denied { read } for pid=386
comm="restorecon" name="[982]" dev=pipefs ino=982
scontext=system_u:system_r:restorecon_t:s0
tcontext=system_u:system_r:restorecon_t:s0 tclass=fifo_file
Roger
18 years, 2 months
HELP: "PCI: Fail to allocate mem resource
by Reg Clemens
What does this mean/imply?
Right after the "Uncompressing Linux" line of the boot, I see the line
PCI: Failed to allocate the mem resource #6:20000@48000000 for 0000:01:00.0
when I boot 2.6.15.1.
When I boot 2.6.11, there is no such message.
This is on an Intel D945Gnt motherboard with a 3.2GHz Pentium4.
This motherboard has online video/sound/ethernet, tho none of these work
with Linux (ok the video works marginally)
I have added an nvidia 6600 video card, a soundblaster 24 (not working yet)
and a D-Link ethernet adapter. I pulled everything but the video card but
still get the same error message...
Really would like to get this system working...
--
Reg.Clemens
reg(a)dwf.com
18 years, 2 months
FC5T2 - not ready for prime time.
by Reg Clemens
I know people work hard on these releases, but some bugs should
be obvious...
I downloaded the 5bin cds yesterday, and tried to install it in
an extra partition on my disk (3.2GHz Pentium4, 945Gnt Motherboard).
Probably 8 out of 10 times the installer died while I was picking
packages to install. Each time it would pop up a message box saying
something to the effect 'this is a bug' and describing how to report it.
OK, with repeated beating, on at least two attempts I got by the
'picking packages' bug and got to the actual install. In both cases
I got somewhere late on the 1st CD (the ribbon showed that I was about
50% installed), and now it complains about an unexpected interrupt,
pops up a message box and dies.
Not nice.
And WHAT WAS WRONG WITH THE PREVIOUS install program, it seems to have
worked fine ever since RedHat5 or 6. Why is it being replaced with
something that is not even debugged?
Guess Ill wait and give it another try when FC5T3 is available, but
this doesnt leave a very good feeling in my stomach... All I wanted
to do was see if this release supports the Intel 945 Motherboards
(It appears it does), but Im not going to try the support till I can
at least install a system. Sigh.
--
Reg.Clemens
reg(a)dwf.com
18 years, 2 months
