Today's Dep Isues
by M Galvin
Hi Everyone,
I finally had the time to get fc3t1 setup and up2date. It took almost a
full day to get all the updates installed but I must say that it went
fairly well for such an early release stage.
Anyway, this is the dep problem i ran into this morning.
...
Test install failed because of package conflicts:
file /usr/share/man/man5/resolver.5.gz from install of man-pages-1.67-2
conflicts with file from package
bind-utils-9.2.4-EL4_1
...
This happens when bind is updated BEFORE the man pages. Is there a way i
can just force the man page rpm install since this is just a
documentation update?
Thanks,
Matt
19 years, 8 months
gnome-volume-manager vs. automount w/ usb memory stick
by Dr. Steve
Not sure if this is the right place to ask, but I'll ask anyway. Prior
to installing gnome-volume-manager, I had an entry in /etc/auto.mnt that
would mount device sda1, either my camera or my usb memory stick as
/mnt/camera. Although I had to be root to write to the memory stick, the
complete file name would always be displayed when listing the directory.
With gnome-volume-manager deployed, the memory stick mounts as usbdisk
(haven't looked to see which directory it's in) and is writable by an
ordinary user, but all I see is a truncated 8.3 msdos-style file name.
I'd really like to see the complete file name. Is there a simple way to
do this?
TIA
--
Steven I. Usdansky
19 years, 8 months
Problem with sound volume
by Julien Olivier
Hi
I've just installed FC2, and immediately upgraded it to yesterday's
Rawhide.
Apart from a few glinches that I've reported to bugzilla, I'm
experiencing a strange bug.
My laptop is a Fujitsu/Siemens Lifebook S6210. It doesn't have any
hardware way to control the sound volume. So, I tried to change the
volume using the "Volume Control" applet, but it failed.
I went to the applet's preferences and changed the audio channel from
"volume" to "PCM". After that, I could control the volume.
Later on, I noticed that my laptop had special keys to control the
volume. As expected, they didn't work right out of the box.
So, I opened the "keyboard shortcuts" preferences and associated said
keys to the "volume mute", "volume down" and "volume up" sound
functions.
After pressing the keys, a graphic appeared of my screen showing that I
was muting, pumping down or pumping up the volume. The only problem is
that those functions control the "volume" channel, not the "PCM"
channel, and are - consequently - useless for me.
So, my questions are:
- Why can't I change the volume by controlling the "volume" channel ?
Is it a bug that should be filed ? Against which package ? Or is it a
hardware limitation that can't be detected ?
- Is there a way to change the action of the "volume mute", "volume
down", "volume up" keyboard shortcuts so that they control the "PCM"
channel instead of "volume" channel.
Thanks !
--
Julien Olivier <julo(a)altern.org>
19 years, 8 months
problem with hal-0.2.97.cvs20040823-1.i386.rpm
by Jef Spaleta
Anyone seen the haldaemon initscript from hal-0.2.97.cvs20040823-1.i386.rpm
taking a cup of coffee or longer length of time to return when run?
The hanging happens at boot up if haldeamon is enabled
And by hand after bootup with haldaemon is disabled at boot up.
I've reverted back to hal-0.2.97.cvs20040819-1.i386.rpm and I can't
reproduce the problem.
And here's the kicker.... if i have hal-0.2.97.cvs20040819 daemon
running when i try to install
hal-0.2.97.cvs20040823 the package install process stalls as well
since whatever the post/pre (un)install script being activated in
that process makes a call to service haldaemon which hangs just like i
see at boot up with hal-0.2.97.cvs20040819 installed. Very not
cool.... very not not cool when this happens during a yum update and
stopping yum leaving the system with duplicate packages installed
since yum's transaction didn't complete.
Anyone else seeing this? Before I dig into the script logic looking
for a smoking gun?
-jef
19 years, 8 months
Kernel 525 Changed Behavior
by Steve G
Hi,
I was watching kernel 525 boot up. My machine is dual boot. The boot partition is
sda1, build partition sda2, swap is sda5, and my test partition is sda3.
I create a special fstab for testing which just includes sda3 and sda5. This way
the system doesn't know anything about my build partition.
On the way up, it tried to do a restore context of every single partition. This
is kind of scary seeing as the kernels I use for building Oops whenever they
access a disk that has had SE Linux running.
You simply cannot do a restore context on every partition because it will break
people's machines. Also, there should be some record of it and its results in the
system messages log. Looking through the log, you see nothing about the restore
context. There were clearly some failure messages hitting the screen, but nothing
in the logs !
-Steve Grubb
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
19 years, 8 months
Bug in Up2date resolution when packages marked skipped --attachment
by Jim Cornette
Adding attachment -
I noticed that when a package may have many different elements, such as
xorg-x11, updating will fail because deps might be needed from the
excluded list.
I had this happen because of adding xorg-x11 to my skipped packages
recently. The package that caused the conflict was
xorg-x11-deprecated-libs-6.7.9
What happened was a pop-up appeared indicating what will be attached to
this message. Since this package was marked on the skipped list, it
would not resolve.
As you can imagine, with the pop-up dialog box, it scrolled off of the
top and bottom of the screen.
I did not search bugzilla regarding this sort of error. I don't think
that too many excluded packages would contain so many rpms per program.
I removed xorg-x11 from the skipped programs list and installation
continued normally.
If someone needed "watched" packages added to their skipped lists, this
might be some problem that is worth looking into.
attached pop-up with xorg-x11* added to skipped package list.
If this is by design, maybe some method for determining the group the
program belong to when skipped programs selected might be a nice add-on
feature.
Jim
There was a package dependency problem. The message was:
To solve all dependencies for the RPMs you have selected, The following
packages you have marked to exclude would have to be added to the set:
Package Name Reason For Skipping
======================================================================
kernel-2.6.8-1.526 Pkg name/pattern
kernel-2.6.8-1.526 Pkg name/pattern
kernel-BOOT-2.4.22-1.2193.nptl Pkg name/pattern
kernel-debuginfo-2.6.8-1.526 Pkg name/pattern
kernel-debuginfo-2.6.8-1.526 Pkg name/pattern
kernel-doc-2.6.5-1.358 Pkg name/pattern
kernel-doc-2.6.8-1.526 Pkg name/pattern
kernel-module-nvidia-2.6.7-1.4 Pkg name/pattern
kernel-module-nvidia-2.6.7-1.4 Pkg name/pattern
kernel-module-nvidia-2.6.7-1.4 Pkg name/pattern
kernel-module-nvidia-2.6.7-1.4 Pkg name/pattern
kernel-smp-2.6.8-1.526 Pkg name/pattern
kernel-smp-2.6.8-1.526 Pkg name/pattern
kernel-source-2.6.5-1.358 Pkg name/pattern
kernel-source-2.6.6-1.383 Pkg name/pattern
kernel-sourcecode-2.6.8-1.521 Pkg name/pattern
kernel-utils-2.4-12.1.142 Pkg name/pattern
kernel-utils-debuginfo-2.4-12. Pkg name/pattern
xorg-x11-6.7.99.902-4 Pkg name/pattern
xorg-x11-100dpi-fonts-6.7.99.9 Pkg name/pattern
xorg-x11-75dpi-fonts-6.7.99.90 Pkg name/pattern
xorg-x11-ISO8859-14-100dpi-fon Pkg name/pattern
xorg-x11-ISO8859-14-75dpi-font Pkg name/pattern
xorg-x11-ISO8859-15-100dpi-fon Pkg name/pattern
xorg-x11-ISO8859-15-75dpi-font Pkg name/pattern
xorg-x11-ISO8859-2-100dpi-font Pkg name/pattern
xorg-x11-ISO8859-2-75dpi-fonts Pkg name/pattern
xorg-x11-ISO8859-9-100dpi-font Pkg name/pattern
xorg-x11-ISO8859-9-75dpi-fonts Pkg name/pattern
xorg-x11-Mesa-libGL-6.7.99.902 Pkg name/pattern
xorg-x11-Mesa-libGLU-6.7.99.90 Pkg name/pattern
xorg-x11-Xdmx-6.7.99.902-4 Pkg name/pattern
xorg-x11-Xnest-6.7.99.902-4 Pkg name/pattern
xorg-x11-Xvfb-6.7.99.902-4 Pkg name/pattern
xorg-x11-base-fonts-6.7.99.902 Pkg name/pattern
xorg-x11-cyrillic-fonts-6.7.99 Pkg name/pattern
xorg-x11-deprecated-libs-6.7.9 Pkg name/pattern
xorg-x11-deprecated-libs-devel Pkg name/pattern
xorg-x11-devel-6.7.99.902-4 Pkg name/pattern
xorg-x11-doc-6.7.99.902-4 Pkg name/pattern
xorg-x11-font-utils-6.7.99.902 Pkg name/pattern
xorg-x11-libs-6.7.99.902-4 Pkg name/pattern
xorg-x11-libs-data-6.7.99.902- Pkg name/pattern
xorg-x11-sdk-6.7.99.902-4 Pkg name/pattern
xorg-x11-syriac-fonts-6.7.99.9 Pkg name/pattern
xorg-x11-tools-6.7.99.902-4 Pkg name/pattern
xorg-x11-truetype-fonts-6.7.99 Pkg name/pattern
xorg-x11-twm-6.7.99.902-4 Pkg name/pattern
xorg-x11-xauth-6.7.99.902-4 Pkg name/pattern
xorg-x11-xdm-6.7.99.902-4 Pkg name/pattern
xorg-x11-xfs-6.7.99.902-4 Pkg name/pattern
Unresolvable chain of dependencies:
xorg-x11 6.7.99.902-4 requires libXp.so.6
xorg-x11-tools 6.7.99.902-4 requires libXp.so.6
Please modify your package selections and try again.
19 years, 8 months
kernel 525 Oopsfest
by Steve G
Hi,
I just upgraded to kernel 525 and it Oops 9 times on the way up. Every single one
was on udev:
Aug 24 16:38:09 buildhost kernel: [<c017a9a8>] fcntl_setlk+0x14/0x285
Aug 24 16:38:09 buildhost kernel: [<c0173be1>] open_namei+0x2bf/0x571
Aug 24 16:38:09 buildhost kernel: [<c0161624>] dentry_open+0xe0/0x180
Aug 24 16:38:09 buildhost kernel: [<c016153e>] filp_open+0x37/0x3d
Aug 24 16:38:09 buildhost kernel: [<c02fd2dc>] __cond_resched+0x14/0x3b
Aug 24 16:38:09 buildhost kernel: [<c01767f9>] do_fcntl+0x1d4/0x21d
Aug 24 16:38:09 buildhost kernel: [<c017690f>] sys_fcntl64+0x6f/0x80
Aug 24 16:38:09 buildhost kernel: [<c02feab7>] syscall_call+0x7/0xb
Is this a known problem? Is it fixed in later builds? Do you want it in bugzilla?
The bad part is that each had a different pid and they seemed to Oops in parallel
and during other system initialization...which makes it hard to pick out the
Oopses. The system did actually make it all the way up.
-Steve Grubb
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
19 years, 8 months
Process memory map in fedora
by John Muir
Hi,
I'm wondering what changes were put into the fedora kernel and glibc (?)
to enable the process memory map change that I have observed between
another Linux distribution (Mandrake 9.2), and Fedora Core 2.
I believe that the 'flexible-mmap' patch that is part of the -mm kernel
at the moment is involved. Are there any other changes such as in ld.so?
The memory maps in question are output below.
Thanks,
..John
Mandrake 9.2:
[muirj@muirj-1 patches]$ pmap -x $$
23024: /bin/bash
Address kB Resident Shared Private Permissions Name
08048000 608 - 0 608 read/exec bash
080e0000 24 - 0 24 read/write bash
080e6000 424 - 0 424 read/write/exec [ anon ]
40000000 76 - 0 76 read/exec ld-2.3.2.so
40013000 4 - 0 4 read/write ld-2.3.2.so
40014000 4 - 0 4 read/write [ anon ]
40015000 4 - 0 4 read
LC_IDENTIFICATION
40016000 4 - 0 4 read LC_MEASUREMENT
40017000 4 - 0 4 read LC_TELEPHONE
40018000 4 - 0 4 read LC_ADDRESS
40019000 4 - 0 4 read LC_NAME
4001a000 4 - 0 4 read LC_PAPER
4001b000 4 - 0 4 read
SYS_LC_MESSAGES
4001c000 4 - 0 4 read LC_MONETARY
4001d000 24 - 0 24 read LC_COLLATE
40023000 4 - 0 4 read LC_TIME
40024000 12 - 0 12 read/exec
libtermcap.so.2.0.8
40027000 4 - 0 4 read/write
libtermcap.so.2.0.8
40028000 8 - 0 8 read/exec libdl-2.3.2.so
4002a000 4 - 0 4 read/write libdl-2.3.2.so
4002b000 1192 - 0 1192 read/exec libc-2.3.2.so
40155000 12 - 0 12 read/write libc-2.3.2.so
40158000 16 - 0 16 read/write [ anon ]
4015c000 4 - 0 4 read LC_NUMERIC
4015d000 176 - 0 176 read LC_CTYPE
40189000 4 - 0 4 read/exec ISO8859-1.so
4018a000 4 - 0 4 read/write ISO8859-1.so
40198000 32 - 0 32 read/exec
libnss_files-2.3.2.so
401a0000 4 - 0 4 read/write
libnss_files-2.3.2.so
bfffa000 24 - 0 24 read/write/exec [ anon ]
-------- ------ ------ ------ ------
total kB 2696 - 0 2696
Fedora Core 2:
4085: -bash
Address Kbytes RSS Anon Locked Mode Mapping
002e0000 40 - - - r-x-- libnss_files-2.3.3.so
002ea000 4 - - - r---- libnss_files-2.3.3.so
002eb000 4 - - - rw--- libnss_files-2.3.3.so
00b09000 84 - - - r-x-- ld-2.3.3.so
00b1e000 4 - - - r---- ld-2.3.3.so
00b1f000 4 - - - rw--- ld-2.3.3.so
00b22000 1108 - - - r-x-- libc-2.3.3.so
00c37000 8 - - - r---- libc-2.3.3.so
00c39000 8 - - - rw--- libc-2.3.3.so
00c3b000 8 - - - rw--- [ anon ]
00c3f000 8 - - - r-x-- libdl-2.3.3.so
00c41000 4 - - - r---- libdl-2.3.3.so
00c42000 4 - - - rw--- libdl-2.3.3.so
00c87000 12 - - - r-x-- libtermcap.so.2.0.8
00c8a000 4 - - - rw--- libtermcap.so.2.0.8
00dbb000 4 - - - r-x-- [ anon ]
08047000 556 - - - r-x-- bash
080d2000 24 - - - rw--- bash
080d8000 16 - - - rw--- [ anon ]
0818b000 132 - - - rw--- [ anon ]
f6e3c000 4 - - - rw--- [ anon ]
f6e3d000 24 - - - r--s- gconv-modules.cache
f6e43000 2048 - - - r---- locale-archive
f7050000 8 - - - rw--- [ anon ]
feefe000 1032 - - - rw--- [ stack ]
ffffd000 4 - - - ----- [ anon ]
19 years, 8 months
Sound modules no longer loading at boot up with latest rawhide updates
by Jef Spaleta
So i was running kernel-smp-2.6.7-1.517 from rawhide without a problem.
I synced to todays rawhide tree and booted into kernel-smp-2.6.8-1.525
and i noticed the sound modules were not being loadded at boot time.
Going back to the kernel-smp-2.6.7-1.517 and things work as expected,
but i was planning to do that test again after i write this email.
If I modprobe snd-card-0, the modules load and everything is right
with the world.
So anyone else seeing sound modules no longer loading automagically?
my modprobe.conf has:
alias snd-card-0 snd-emu10k1
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 &&
/usr/sbin/alsactl restore
>/dev/null 2>&1 || :
remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
/sbin/modprobe -r -
-ignore-remove snd-emu10k1
-jef
19 years, 8 months