System: Linux 18.104.22.168-37.fc8 #1 SMP Fri Oct 26 12:36:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
GTK+ Theme: Nodoka
Icon Theme: Fedora
Sometimes Firefox crashes and I can save a debug file, beginning like
that (but many additional lines are not here)
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0
timeout: 0 it_real_value: 0 frequency: 0
----------- .xsession-errors (2010 sec old) ---------------------
** (totem-video-thumbnailer:9124): WARNING **: Add decoder pcm_zork
** (totem-video-thumbnailer:9124): WARNING **: Add decoder
adpcm_ima_amv (69651) please
** (totem-video-thumbnailer:9124): WARNING **: Add decoder adpcm_thp
** Message: don't know how to handle text/uri-list
** Message: Error: You do not have a decoder installed to handle this
file. You might need to install the necessary plugins.
gstplaybasebin.c(2215): prepare_output (): /play
** Message: Error: Errore interno nel flusso di dati.
gstbasesrc.c(1816): gst_base_src_loop (): /play/source:
streaming task paused, reason not-linked (-1)
totem-video-thumbnailer couln't open file 'file:///home/antonio/.Trash/mp3.ram'
Reason: You do not have a decoder installed to handle this file. You
might need to install the necessary plugins..
Who can decode it???
Skype : antoniomontag
Am I correct in my understanding that the pam-gnome-keyring module
should be enabled through gdm by default?
Even though I have set my keyring password to be the same as my login
password I still have to enter it twice (once at the gdm prompt and
again the first time I have to access something in my keyring).
Anyone else with the same problem?
Mads Villadsen <maxx(a)krakoa.dk>
xmaxima and wvxmaxima are not working. This happens
on the rawhide machines and on the livecd that I have
generated with livecd-creator. What should I do?
[students@localhost ~]$ rpm -qa maxima*
[students@localhost ~]$ rpm -qa Wxmaxima*
[students@localhost ~]$ rpm -qa wxmaxima*
[students@localhost ~]$ wxmaxima
** (wxmaxima:9191): WARNING **: IPP request failed
with status 1030
[students@localhost ~]$ wxmaxima
** (wxmaxima:9214): WARNING **: IPP request failed
with status 1030
[students@localhost ~]$ wxMaxima
bash: wxMaxima: command not found
[students@localhost ~]$ rpm -qa wxMaxima
[students@localhost ~]$ xmaxima
Maxima 5.13.0 http://maxima.sourceforge.net
Using Lisp SBCL 1.0.10
Distributed under the GNU Public License. See the file
Dedicated to the memory of William Schelter.
This is a development version of Maxima. The function
provides bug reporting information.
(%i1) jfa: starting server on port 4008
Maxima encountered a Lisp error:
Name service error in "getaddrinfo": -2 (Name or
service not known)
To reenable the Lisp debugger set *debugger-hook* to
(%i1) [students@localhost ~]$
Anbody else seeing this.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
in the middle of a "yum update" that's generating about 80 bazillion
"Requested Range Not Satisfiable due to unobtainable file length"
errors, then going on to try other mirrors.
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
Hans de Goede wrote:
> Build System wrote:
>> Updated Packages:
>> * Sun Oct 28 2007 Jeremy Katz <katzj(a)redhat.com> - 0.6.18-3
>> - Even better multilib fixing (#335161)
> How does this match with us being in freeze?
The bug in question has been marked as a blocker.
On Sun, 2007-10-28 at 11:00 -0500, "Fulko Hew" <fulko.hew(a)gmail.com>
> I decided to play with sleep and suspend on my Dell Inspiron 6400...
> Most things work, but during recovery from sleep, the screen was
> still dark/blank. So following the instructions on the quirk site, I tried:
> lshal | grep system.hardware
> and I get:
> [root@localhost log]# lshal | grep system.hardware
> system.hardware.primary_video.product = 10146 (0x27a2) (int)
> system.hardware.primary_video.vendor = 32902 (0x8086) (int)
> system.hardware.product = 'MM061' (string)
> system.hardware.serial = 'XXXXXX' (string)
> system.hardware.uuid = 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' (string)
> system.hardware.vendor = 'Dell Inc.' (string)
I have a dell inspiron 9400, and like you i also had an issue with resume from suspend ( blank screen, but the rest of it comes back up ok )
i only had a very brief click through f8 from the test-3 live image, and didnt really have time to dig in any deeper at the time, but this is one of those things that can really make or break the perception of a distro IMHO
( the rest of f8 looks pretty rock solid to me...)
FYI, my inspiron 9400 reports:
jasond@granite:~>lshal | grep hardware
system.hardware.product = 'MP061' (string)
system.hardware.serial = 'XXXXXX' (string) // hashed out - this is the service tag too eh?
system.hardware.uuid = 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' (string)
system.hardware.vendor = 'Dell Inc.' (string)
laptop_panel.brightness_in_hardware = false (bool)
my brief glance at the .fdi markup makes me think Fulko's remedy seems to me to be on the right track, but not to sure what goes on with all the 'merge' elements, especially given the lack of a common identifier in the system.hardware.product lines that lshal shows up.
i wonder also if newer latitude models will suffer from the same quirks quirk? :( (my wife runs an old latitude, perhaps after she nods off i'll try the live cd and see what that reports, lest she find out i'm quietly linuxing her laptop...)
perhaps the lower down code in hal needs to dig a little deeper to get the Inspiron string?
Oct 28 16:42:49 nbecker1 NetworkManager: <info> Activation
access point 'Auto SS23' has security, but secrets are required.
Oct 28 16:42:49 nbecker1 NetworkManager: <info> Activation (wlan0) Stage 2
5 (Device Configure) complete.
Oct 28 16:42:50 nbecker1 kernel: nm-applet: segfault at
rip 0000000000414e99 rsp 00007fffe171df50 error 4
Oct 28 16:42:50 nbecker1 NetworkManager: <WARN> get_secrets_cb(): Couldn't
get connection secrets: Message did not receive a reply (timeout by message
Which means I can't setup a new wireless connection. Note that for now, kde
is using this also, so I'm screwed.
The QA team went through the F8Blocker bug list today. The good news is
that a lot of the things that would have blocked the release are fixed -
we're down under 20 blocker bugs (not including trackers).
The current blocker list can be found here:
We need help testing and evaluating some of these bugs - some of them
only affect certain hardware or less-common software configurations. We
need to know how widespread the problems are in order to decide whether
a given problem is actually worth delaying the release to fix.
Please look through this list and see if there's anything you could help
In order by bug ID, here's a look at our current blocker bugs, with
* Bug 208607: ASSIGNED - kernel-maint(a)redhat.com
- mkinitrd: iSCSI root requires crc32c module
iSCSI is a tricky beast. This didn't work right in F7 either, so it's
not a new problem, just something we were planning to have fixed
properly for F8. Instead we will probably end up building crc32c into
the kernel so that iSCSI-root works properly.
If you've got iSCSI hardware, it would be excellent if you could help us
test installation (after we get this change in..). Adding yourself to
the CC list for the bug would be a great idea.
* Bug 242536: ASSIGNED - alan(a)redhat.com
- [pata_via] Anaconda failed after formatting the / partition
* Bug 242766: ASSIGNED - alan(a)redhat.com
- [pata_via via82c596a] hard drive not found during install attempt
If anyone has pata_via hardware, please speak up! We need to know how
much impact these bugs will have, testing help, etc.
* Bug 253892: ASSIGNED - vcrhonek(a)redhat.com
- There is no usable romanian keymap for the linux console
An earlier fix didn't work. It's unclear whether this actually prevents
Romanian users from using their systems (which would make it a blocker)
but the fix should be simple, so it stays for now.
* Bug 264901: NEW - notting(a)redhat.com
- oops, we have multiple sources of persistent network names active at
the same time
notting says that this is (more or less) fixed for things in the default
install. We're trying to work out ways to test it. This may get dropped
from the blocker list and fully fixed in F9-rawhide.
* Bug 311511: NEEDINFO - dcbw(a)redhat.com
- x86_64 iwl3945 NM crash after Keyring loop Deny
A fix for this has been committed, we're waiting for the reporter to
confirm. If you can confirm this fix, that would help.
* Bug 323371: ASSIGNED - dcbw(a)redhat.com
- NM 0.7 doesn't support WPA/WPA2 Enterprise (certificate-based
This is also fixed, in theory, but the original reporter is having
problems beyond WPA/WPA2 Enterprise. If you can confirm WPA or WPA2
Enterprise is working with current NetworkManager
(NetworkManager-0.7.0-0.3.svn3016.fc8, in koji or tomorrow's rawhide)
please comment on the bug.
* Bug 330931: NEEDINFO - katzj(a)redhat.com
- liveinst fails - sg devices confuse anaconda?
This involves some interesting hardware - Dell PowerEdge 2650 - so if
you have some of this hardware and can help test / debug, please grab a
copy of the LiveCD and give it a shot.
* Bug 335161: MODIFIED - triad(a)df.lth.se
- multilib file conflicts in gnokii
A fix for this has been committed and should show up in rawhide
* Bug 338551: NEW - davej(a)redhat.com
- kernel 22.214.171.124-23.fc8 does not boot anymore on SK8V
Again, this is a bug with specific hardware - if you have an SK8V
motherboard, we could use testing help.
* Bug 345841: MODIFIED - dwalsh(a)redhat.com
- SELinux denial from cron
This should be fixed in today's rawhide, hopefully the reporter will
retest and close the bug (COUGH COUGH JESSE COUGH SLACKER COUGH)
* Bug 346471: NEW - lvm-team(a)redhat.com
- F8T3 Live CD detects LVM groups inside RAID1, without using RAID1
This one is kind of nasty - LVM startup problems on the LiveCD can cause
it to mess around with one mirror of a RAID1 set, which could lead to
desynched mirrors and other badness. It's being investigated.
* Bug 348931: MODIFIED - ehabkost(a)redhat.com
- virt-install --nographics --paravirt is broken
There's a fix for this in the kernel-xen-2.6 package in today's rawhide.
If you're a xen user, testing and commenting on this bug would be much
A few more bugs have been added since the QA meeting - I'll comment
about them in a status report later this week.
Thanks for any help, and keep on testin', rawhiders!