After kernel 1275 fixed the "constant" rebooting problem on x86_64 system, I
was eager to see how soon the other major problem could be fixed -- segfault
when running 32 bit applications.
Since rawhide had not been updated yet, I thought I would look to see if davej
had any new kernel on people.redhat.com ... sure enough, there was kernel
After downloading, I looked at the change log and it said that a fix for 32
bit applications was included. After installation and reboot I tested .. 32
bit applications now work (no segfault).
This also means that vmware-config.pl works again for those interested.
I have a dell inspiron 2650 with rawhide on it. For the most part it is running
flawlessly, however I keep seeing the following messages in the logs:
Apr 28 21:36:55 bullwinkle pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Apr 28 21:37:30 bullwinkle last message repeated 7 times
Apr 28 21:38:35 bullwinkle last message repeated 13 times
Apr 28 21:39:40 bullwinkle last message repeated 13 times
Apr 28 21:40:44 bullwinkle last message repeated 13 times
Apr 28 21:41:09 bullwinkle last message repeated 5 times
Apr 28 21:41:11 bullwinkle ntpd: synchronized to 192.168.0.2, stratum 2
Apr 28 21:41:14 bullwinkle pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Apr 28 21:41:49 bullwinkle last message repeated 7 times
Apr 28 21:42:54 bullwinkle last message repeated 13 times
Apr 28 21:43:19 bullwinkle last message repeated 5 times
Apr 28 21:43:22 bullwinkle ntpd: kernel time sync enabled 0001
Apr 28 21:43:24 bullwinkle pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Apr 28 21:43:55 bullwinkle last message repeated 6 times
Apr 28 21:45:00 bullwinkle last message repeated 13 times
Apr 28 21:46:05 bullwinkle last message repeated 13 times
Apr 28 21:47:10 bullwinkle last message repeated 13 times
Apr 28 21:48:15 bullwinkle last message repeated 13 times
Apr 28 21:49:20 bullwinkle last message repeated 13 times
Apr 28 21:50:25 bullwinkle last message repeated 13 times
Apr 28 21:51:30 bullwinkle last message repeated 13 times
Apr 28 21:51:55 bullwinkle last message repeated 5 times
Apr 28 21:51:56 bullwinkle kernel: codec_semaphore: semaphore is not ready [0x1][0x300300]
Apr 28 21:51:56 bullwinkle kernel: codec_read 0: semaphore is not ready for register 0x2c
Apr 28 21:52:00 bullwinkle pam_timestamp_check: pam_timestamp: `/' owner UID != 0
Apr 28 21:52:30 bullwinkle last message repeated 6 times
Any idea what is causing the pam_timestamp or the codec_semaphore messages or
how to fix them?
Tom Diehl tdiehl(a)rogueind.com Spamtrap address mtd123(a)rogueind.com
Why no more rawhide report/refresh? Waiting for test3?
I have seen from roadmap that on 27th of April "Translation deadline
(data provided) test3 devel freeze" and on 9th of May "test3,
translation build freeze (builds completed)" but cannot understand when
test 3 will be released...
I just tried out K3b and burnt a couple of CD's today. The burning
works just fine, however when it spawns artsd to play the "trumpet"
sound, artsd spikes to 100%CPU and fails to play anything.
Can someone try this out and see if it something specific to my box or
an issue with the distro?
I don't know whether this is off-topic, because inkscape is in extras,
but here it is:
Using inkscape, several functions crash the program. For example, when I
press Shift+Ctrl+F to open the dialog where I can change how an object
is filled or select the Keyboard shortcut help from the menu, it
crashes. Some other dialogs, for example the Text + Font dialog opens
correctly. I have installed inkscape via yum from extras-development and
have a fully updated FC4-test2 system.
When I run inkscape and press Shift+Ctrl+F, I get the following output
in my console:
[simon@simon ~]$ inkscape
*** glibc detected *** inkscape: free(): invalid pointer:
======= Backtrace: =========
======= Memory map: ========
00400000-00804000 r-xp 00000000 08:08
00903000-00937000 rw-p 00403000 08:08
00937000-01fb4000 rw-p 00937000 00:00 0
31b0400000-31b0408000 r-xp 00000000 08:08
31b0408000-31b0508000 ---p 00008000 08:08
31b0508000-31b0509000 rw-p 00008000 08:08
31b0600000-31b0603000 r-xp 00000000 08:08
31b0603000-31b0702000 ---p 00003000 08:08
31b0702000-31b0703000 rw-p 00002000 08:08
31b0800000-31b0809000 r-xp 00000000 08:08
31b0809000-31b0909000 ---p 00009000 08:08
31b0909000-31b090a000 rw-p 00009000 08:08
31b0a00000-31b0a14000 r-xp 00000000 08:08
31b0a14000-31b0b13000 ---p 00014000 08:08
31b0b13000-31b0b14000 rw-p 00013000 08:08
31b0c00000-31b0c0b000 r-xp 00000000 08:08
31b0c0b000-31b0d0b000 ---p 0000b000 08:08
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can
I don't know how long the USPS has been offering "click-n-ship" via
java, but they do - and it works in Linux - so I no longer have any need
to have windows (which I was using for PayPal shipping labels)
So I did an http install of rawhide on my IBM Thinkpad 600.
This is a 700 MHz PIII with 256 MB of ram (unfortunately in two 128
chips - so to max it out, I need to buy two new chips :( )
boot.iso, graphical install using my local rawhide mirror, it went
flawlessly. The fonts looked a little weird, but I actually expected
that. The "time remaining" is whacked, imho it should be removed - it
never has been accurate on any machine I have ever installed on.
I was impressed - since it was docked, my USB keyboard and mouse (Apple
Pro keyboard - best USB keyboard I've ever owned) were completely usable
during the install, they weren't for the initial boot prompt, but that's
expected. A certain other operating system does not make them available
until after I have logged in once and it detects the new hardware (and
then it works for login).
First boot went flawlessly, this seems to have been the least
troublesome test install I have done so far.
Post install - it didn't know what my monitor was.
So 800x600 is the best I could get. A thinkpad 600 isn't exactly
bleeding edge hardware. I was able to reconfigure it manually choosing
generic lcd 1024x, and that seems to work.
I could not find a way to shut down the box w/o opening a terminal
window. There is no shutdown option from menu or gdm.
virtual consoles are completely broken - I believe I've seen that
reported already though. I will check to see if there is a bug open for
my chipset (I think there is).
Playing test sound failed, but that I'm filing under the category of I
personally don't really give a damn.