I reported it last Sunday to bugs.kde.org and was told that a fix was in svn.
It hasn't seemed to trickle down yet, I guess.
I noticed that the problem has changed, so I DO hope that this is not the
Formerly, one could click followup to newsgroup and write a nice post, the try
to send and the program would crash and poof, all your work in writing the
post vanished with it.
Now, it crashes as soon as you try to right-click followup to newsgroup, so at
least you don't write a post for nothing.
I'm sseing issues too, I'll try to make time today to get useful
backtraces, and file bugs and/or look for dups where appropriate.
Unfortunately, it comes and goes.
Any assistance to id upstream bugs appreciated. I'll post my own
progress as I make any.
p.s. couldn't send a followup using knode->gmane, had to resort to
email via thunderbird.
as latest digikam has not offerd the geo GPS location setting with kde
4.1 I heard it was due to changes in marble from 4.1 to 4.2. But with
4.2 digikam is still not able to set geo GPS data. Is it possible,
that this is disabled during compile time?
When sending a message I get 8-10 seconds during which I can't read the next
message or do anything else. The 'sent' message is greyed out (probably from
un-focussed window) but it doesn't actually go for that period of time.
Any suggestions on where to start troubleshooting?
I haven't had Amarok work since Fedora 9. Today I got a big update to KDE, but still no sound from Amarok. I'm using Fedora 10, 32 bit version on a Shuttle XPC.
I thought I recalled something about an alsa plugin, but I have that already.
rpm -qa |grep pulse
Amarok is amarok-188.8.131.52-1.fc10.i386
When I launch Amarok and attempt to play a playlist of mp3 tunes stored in my home directory, the progress bar in Amarok goes at warp speed - a 5 minute tune plays in less than 5 seconds, and of course there's that whole no audio thing going on. Since this seems to be isolated just to Amarok, it could be related to the warp speed playback. Audio in all other applications seems to work just fine.
Thanks for any insights.
FYI... revised: https://bugzilla.redhat.com/show_bug.cgi?id=472634
after KDE 4.2 push yesterday. Previously with 4.1 Desktop effects
enabled appeared to work fine with nomodeset, but after 4.2 things
went south in a big way. Didn't matter if I used modeset or
nomodeset, X would loop. Most times I could SSH in and reboot the
system, but sometimes system completely locked up. Initially I had
opened against Radeon 200M, but now my desktop system is affected
(Radeon X300). Another report was with a Radeon X550 - so this seems
pretty pervasive with the Radeon chipset. Not sure what changed in
4.2 with desktop effects, but whatever was uncovered, triggered
badness. At this point it looks like KDE4.2 + Desktop Effects +
Radeon = Xorg Loop