When I run Red Hat GNOME, I get tonnes of assertions and bugs on
xconsole all the time. I figured I'd report some of them. They
don't mean much to me, but I didn't write the code. I'm guessing
they don't mean much to anyone unless they know what caused the
error, but I have no idea what caused it. I ran Korganizer in
GNOME, and KDE's cdplayer. It appears that it may be related to
that...
Gtk-WARNING **: gtk_signal_disconnect_by_data(): could not find
handler containing data (0x8177D18)
Gnome-CRITICAL **: file gnome-dentry.c: line 307
(gnome_desktop_entry_save): assertion `!dentry->is_kde' failed.
Gnome-CRITICAL **: file gnome-dentry.c: line 307
(gnome_desktop_entry_save): assertion `!dentry->is_kde' failed.
Gnome-CRITICAL **: file gnome-dentry.c: line 307
(gnome_desktop_entry_save): assertion `!dentry->is_kde' failed.
Also to note, if you start up KDE's cdplayer it will echo
messages to the console, logs, and pretty much any device or
media that can store data indicating:
Aug 8 00:23:51 asdf kernel: ATAPI device hdd:
Aug 8 00:23:51 asdf kernel: Unknown Error Type: No sense data
-- (Sense key=0x00)
Aug 8 00:23:51 asdf kernel: No additional sense information --
(asc=0x00, ascq=0x00)
Aug 8 00:23:51 asdf kernel: The failed "Read
Subchannel" packet command was:
Aug 8 00:23:51 asdf kernel: "42 02 40 01 00 00 00 00 10 00 00
00 "
Aug 8 00:23:52 asdf kernel: ATAPI device hdd:
Aug 8 00:23:52 asdf kernel: Unknown Error Type: No sense data
-- (Sense key=0x00)
Aug 8 00:23:52 asdf kernel: No additional sense information --
(asc=0x00, asc
It does that when no cd is in the player. It is nice to leave a
cdplayer application running without having a cd in there. It
doesn't appear to be possible in KDE cdplayer, not unless you
have a 400Mb /var/log directory....
Any ideas how to keep cdrom error messages active in the kernel
while simultaneously allowing useful applications to be ran? The
more annoying part though is the sound that it makes. Every
second or two as each error is reported to every console screen
and syslog, it appears syslog syncs to disk, so the hard disk
goes "kachug, kachug, kachug...." Impossible to use the machine
with that racket going on, and stuff scrolling up the
screen. Disabling the error printing via syslog means that
important errors will get lost while burning/copying cd's, etc...
I'm not sure what is at fault here, but I never noticed it
before...
TTYL
P.S. Should I toss these into Bugzilla?
P.S.S. Is it possible to change your bugzilla password? I'd
like to have something more paletteable. Cryptic is good, but
I'd prefer my own cryptic invention over a random one.
--
Mike A. Harris Linux advocate
Computer Consultant GNU advocate
Capslock Consulting Open Source advocate
... Our continuing mission: To seek out knowledge of C, to explore
strange UNIX commands, and to boldly code where no one has man page 4.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
