Re: KDE 3.3 logout crashes my system

2004-09-05 Thread [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi, 

I recently installed kde 3.3 from sid and have had a couple of strange
problems. I was wondering if anyone else has had similar issues.
Biggest problem.
Every time I logout of kde, my system completely locks up. I have tried
launching KDE from gdm, or from just a console and had the same result.
After confirming that I want to logout, the screen goes blank, but a
mouse pointer is still visible, but unresponsive. The system does not
respond to keyboard input such as ctrl-alt-F1, ctrl-alt-backspace or
ctrl-alt-del. Furthermore, I cannot ssh to the box from another
computer. The system must be rebooted to resolve the situation. 

Occasionally, I can bypass this problem by using ctrl-alt-backspace to
kill X rather than logging out, however, this does not seem to work
every time.
Another problem is that for some reason, this process ruins mozilla
firefox's bookmarks.html file. Often, after reboot firefox no longer has
any of the bookmarks that it once had, but sometimes it will have maybe
1/3 of them intact, with the others missing. This does not occur
every time the system hangs, but in all cases, mozilla was not running
when I tried to logout of the system.
A similar problem seems to manifest in xmms. Sometimes after attempting
to logout from KDE 3.3, xmms seems to have forgotten some or all of its
preferences.
Usually, when I have problems with sid, I just wait a few days, and a
new package is available fixing the problem. I decided to join this list
as I haven't been able to find reports of this problem or similar
problems when searching the mailing list archives or on google.
My system is an AMD Athlon XP system with 768 MB of ram, using the
2.4.26 kernel built from the source package. My installation of Gentoo
on the same system does not seem to have the same problems, however, it
is using the newer 2.6.7 kernel (I'm not sure it this is a kernel issue,
but I thought it worth mentioning since the entire system locks up).
Curious if these problems are isolated to myself or if others have seen
similar problems.
Thanks
Jason

Hi,
I have had the same problems. I have done two things (after many other 
trials):
At first I disabled the KDE sound system, then I replaced my personal 
/etc/kde3/kdm/kdmrc with the maintainers version from the package (after 
lockout, so it is not overwritten by KDE).
Then suddenly all my problems were gone. After this I re-enabled the 
sound KDE sound system and the problems were still away. So, at this 
point, I can not determine what was the real reason for this terrible 
lookout problem. But I think it has to do with the KDE sound system, 
because I did not have the problem at every lockout (Sound System Auto 
suspend was 4 seconds). May be sometimes the auto suspend time was reached ?

More information, which was not helpful for me can be found at:
http://mailman.linuxtag.org/pipermail/debian-knoppix/2003-September/003963.html
My File system is: reiserfs
My Sound card is: C-media CM8738
I hope, my information is helpful
Felix
--
remove N_O_ and _S_P_A_M to send an email to me!



Re: KDE 3.3 logout crashes my system

2004-09-05 Thread Rishi
> > I recently installed kde 3.3 from sid and have had a couple of strange
> > problems. I was wondering if anyone else has had similar issues.

I would love to know how to install kde 3.3 on my system. ;-)

I tried 'apt-get install kde' and it says already has the latest
version installed. (3.1.2)

Rishi




Re: kde sound logoff crash workaround

2004-09-05 Thread [EMAIL PROTECTED]
Francisco Vera wrote:
I responded to you in your previous report because I have the same problem.
Now I changed my kernel from 2.4.27-1-k7 to 2.6.8-1-k7 (debian sid), this 
apparently solved the problem.

I also uninstalled kdm, now I run startx to enter kde. Using startx with my 
previous kernel also crashed my system.

Now I tried to play sounds (as you mentioned) NO sounds.
We are not alone with this problem:
http://bugs.kde.org/show_bug.cgi?id=88401
Regards,
Francisco

Hi,
I have had the same problems. Like other people in this mailing list 
[EMAIL PROTECTED] 08/19/04 wrote:

Hi, 

I recently installed kde 3.3 from sid and have had a couple of strange
problems. I was wondering if anyone else has had similar issues.
Biggest problem.
Every time I logout of kde, my system completely locks up. I have tried
launching KDE from gdm, or from just a console and had the same result.
After confirming that I want to logout, the screen goes blank, but a
mouse pointer is still visible, but unresponsive. The system does not
respond to keyboard input such as ctrl-alt-F1, ctrl-alt-backspace or
ctrl-alt-del. Furthermore, I cannot ssh to the box from another
computer. The system must be rebooted to resolve the situation. 

Occasionally, I can bypass this problem by using ctrl-alt-backspace to
kill X rather than logging out, however, this does not seem to work
every time.
Another problem is that for some reason, this process ruins mozilla
firefox's bookmarks.html file. Often, after reboot firefox no longer has
any of the bookmarks that it once had, but sometimes it will have maybe
1/3 of them intact, with the others missing. This does not occur
every time the system hangs, but in all cases, mozilla was not running
when I tried to logout of the system.
A similar problem seems to manifest in xmms. Sometimes after attempting
to logout from KDE 3.3, xmms seems to have forgotten some or all of its
preferences.
Usually, when I have problems with sid, I just wait a few days, and a
new package is available fixing the problem. I decided to join this list
as I haven't been able to find reports of this problem or similar
problems when searching the mailing list archives or on google.
My system is an AMD Athlon XP system with 768 MB of ram, using the
2.4.26 kernel built from the source package. My installation of Gentoo
on the same system does not seem to have the same problems, however, it
is using the newer 2.6.7 kernel (I'm not sure it this is a kernel issue,
but I thought it worth mentioning since the entire system locks up).
Curious if these problems are isolated to myself or if others have seen
similar problems.
Thanks
Jason

I have done two things (after many other trials):
At first I disabled the KDE sound system, then I replaced my personal 
/etc/kde3/kdm/kdmrc with the maintainers version from the package (after 
lockout, so it is not overwritten by KDE).
Then suddenly all my problems were gone. After this I re-enabled the 
sound KDE sound system and the problems were still away. So, at this 
point, I can not determine what was the real reason for this terrible 
lookout problem. But I think it has to do with the KDE sound system, 
because I did not have the problem at every lockout (Sound System Auto 
suspend was 4 seconds). May be sometimes the auto suspend time was reached ?

More information, which was not helpful for me can be found at:
http://mailman.linuxtag.org/pipermail/debian-knoppix/2003-September/003963.html
My File system is: reiserfs
My Sound card is: C-media CM8738
My Kernel is: 2.4.27 (copiled by my self)
I hope, my information is helpful
Felix
--
remove N_O_ and _S_P_A_M to send an email to me!



Re: Frozen bubble problem solved

2004-09-05 Thread Derek Broughton
On September 3, 2004 03:39 pm, Robert Tilley wrote:
> What follows is a log of my failed attempts to deal with the frozen-bubble
> package on my system.  The dependency problems I was experiencing were
> preventing all updates.
> 
> mv: cannot stat `/usr/games/frozen-bubble.wav': No such file or directory
> dpkg: warning - old post-removal script returned error exit status 1
> dpkg - trying script from the new package instead ...
> dpkg: error
> processing /var/cache/apt/archives/frozen-bubble-data_1.0.0-6_all.deb
> (--unpack):
>  there is no script in the new version of the package - giving up
> preinst called with unknown argument `abort-upgrade'

Packaging problem.  It doesn't properly handle the (non)-existence of the wav 
file in the postrm script, then doesn't seem to even _have_ a postrm in the 
new package, and finally it doesn't know what to do with a 'abort-upgrade' 
argument in the preinst script of the new package.
-- 
derek