Bug 163505 - Hangs on Startup, while splash screen is displaying K logo.
Summary: Hangs on Startup, while splash screen is displaying K logo.
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-08 07:11 UTC by Jim Spaloss
Modified: 2008-06-18 18:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Spaloss 2008-06-08 07:11:47 UTC
Version:           4.1 Beta 1 (using Devel)
Installed from:    Compiled sources
OS:                Linux

Sometimes complains about audio device Intel ICH3, "falling back to ICH3". Mouse pointer moves, but nothing is clickable. Clock hangs. Keyboard is unresponsive. Can't kill X-Server. Shut down via power buttton. 
System is Toshiba Laptop, Nvidia GeForce 4-Go 460, Intel ICH3 Audio, P4 2Ghz, Kubuntu 8.04 (Updated from 4.02 which was working fine).
Comment 1 FiNeX 2008-06-08 18:32:25 UTC
Did you tried with a clean user account too?
Comment 2 Jim Spaloss 2008-06-10 04:56:49 UTC
~snip~
>
>
> Did you tried with a clean user account too?
>


First of all, thank you for taking the time to get back to me. I did some
looking through the list of existing bugs and did not find anything that
matched my particular issue.

I added a clean user account as per your suggestion. KWin crashes (and
causes signal 11 SIGSEGV) before KDE hangs. I think this may have something
to do with the way the I created my user, since I had to manually create the
home directory, and change ownership to the new user. I'm sure I m missing
additional steps here.

I tried starting X as root. I seem to get a little bit further the way. The
splash screen disappears and I can get a click in on the K menu button
before the GUI hangs. The K menu does not display, but the button "lights
up", then nothing. My pointer remains responsive, but I can not click on
anything. I am also unable to kill the X-Server w/ CTRL-ALT-BKSPC. Is there
a logfile that I can attach to shed some light on the subject?

My Issue may be related to the audio subsystem (I think the system hangs
when the startup sound is played):
Error message shows up as:

Phonon
> The audio playback device Intel 82801CA-ICH3 with YMF753 (Intel
> 82801CA-ICH3) does not...(goes off screen)
> Falling back to Intel 82801CA-ICH3 with YMF753 (Intel 82801CA-ICH3).
>


My system is a Toshiba 5205-S503 Notebook, and has no proper BIOS, so I can
not disable the sound. Is there a way to disable the sound by CLI?

I am also willing to accept that I have hosed my Kubuntu install somehow, so
if you think that this is an isolated incident and I need to wipe it and
reinstall, please let me know.

Thanks,
Jim
<br>~snip~<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Did you tried with a clean user account too?<br>
</blockquote></div><br>First of all, thank you for taking the time to get back to me. I did some looking through the list of existing bugs and did not find anything that matched my particular issue.<br><br>I added a clean user account as per your suggestion. KWin crashes (and causes signal 11 SIGSEGV) before KDE hangs. I think this may have something to do with the way the I created my user, since I had to manually create the home directory, and change ownership to the new user. I&#39;m sure I m missing additional steps here.<br>
<br>I tried starting X as root. I seem to get a little bit further the way. The splash screen disappears and I can get a click in on the K menu button before the GUI hangs. The K menu does not display, but the button &quot;lights up&quot;, then nothing. My pointer remains responsive, but I can not click on anything. I am also unable to kill the X-Server w/ CTRL-ALT-BKSPC. Is there a logfile that I can attach to shed some light on the subject?<br>
<br>My Issue may be related to the audio subsystem (I think the system hangs when the startup sound is played):<br>Error message shows up as:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Phonon<br>The audio playback device Intel 82801CA-ICH3 with YMF753 (Intel 82801CA-ICH3) does not...(goes off screen)<br>Falling back to Intel 82801CA-ICH3 with YMF753 (Intel 82801CA-ICH3).<br></blockquote><br>My system is a Toshiba 5205-S503 Notebook, and has no proper BIOS, so I can not disable the sound. Is there a way to disable the sound by CLI?<br>
<br>I am also willing to accept that I have hosed my Kubuntu install somehow, so if you think that this is an isolated incident and I need to wipe it and reinstall, please let me know.<br><br>Thanks,<br>Jim<br>
Comment 3 Jim Spaloss 2008-06-11 07:05:03 UTC
A New Development,

I booted by Kubuntu partition up under VMWare Server 1.4 (Windows XP Host if
that matters). Under the VM, KDE boots without issue (I did have to change
my video driver from nvidia to vesa in xorg.conf, but that's it.) I'm
convinced that the bug is related to my hardware, I tried disabling the
sound, but couldn't remove the device because the driver was not loaded
under the VM. I disabled sound notifications, and moved PulseAudio up in the
preferred sound devices list. When I booted back into Kubuntu natively, it
still froze.

Thanks,
Jim
A New Development,<br><br>I booted by Kubuntu partition up under VMWare Server 1.4 (Windows XP Host if that matters). Under the VM, KDE boots without issue (I did have to change my video driver from nvidia to vesa in xorg.conf, but that&#39;s it.) I&#39;m convinced that the bug is related to my hardware, I tried disabling the sound, but couldn&#39;t remove the device because the driver was not loaded under the VM. I disabled sound notifications, and moved PulseAudio up in the preferred sound devices list. When I booted back into Kubuntu natively, it still froze.<br>
<br>Thanks,<br>Jim<br>
Comment 4 George Goldberg 2008-06-15 05:40:09 UTC
Jim, could you try changing your video driver in xorg to vesa (for the main kubuntu install, not the VM). Nvidia drivers a responsible for lots of issues with KDE 4, and although the vesa driver will probably look horrible (low resolution etc), it will at least allow is to identify whether the nvidia drivers are causing the issue.
Comment 5 Jim Spaloss 2008-06-16 04:20:53 UTC
>
> Jim, could you try changing your video driver in xorg to vesa (for the main
> kubuntu install, not the VM). Nvidia drivers a responsible for lots of
> issues with KDE 4, and although the vesa driver will probably look horrible
> (low resolution etc), it will at least allow is to identify whether the
> nvidia drivers are causing the issue.
>



Thank you for your reply.

I tried the vesa driver and was able to get into the KDE4.1 desktop without
locking up. After seeing that the VESA driver worked, I also tried the open
source nv driver and that also worked (at full resolution). I tested my
sound system (which I thought was my problem initially) and that works also.
I guess this is just an incompatibility between the proprietary Nvidia
driver and KDE4.1?

For the sake of documentation, the proprietary Nvidia driver was
71.86.04.I'm not really missing much on this old Geforce 4 Go 460
anyway.

Thanks again for the help!!!
<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Jim, could you try changing your video driver in xorg to vesa (for the main kubuntu install, not the VM). Nvidia drivers a responsible for lots of issues with KDE 4, and although the vesa driver will probably look horrible (low resolution etc), it will at least allow is to identify whether the nvidia drivers are causing the issue.<br>

</blockquote></div><br><br>Thank you for your reply. <br><br>I tried the vesa driver and was able to get into the KDE4.1 desktop without locking up. After seeing that the VESA driver worked, I also tried the open source nv driver and that also worked (at full resolution). I tested my sound system (which I thought was my problem initially) and that works also. I guess this is just an incompatibility between the proprietary Nvidia driver and KDE4.1?<br>
<br>For the sake of documentation, the proprietary Nvidia driver was <a href="http://71.86.04.">71.86.04.</a> I&#39;m not really missing much on this old Geforce 4 Go 460 anyway.<br><br>Thanks again for the help!!!<br>
Comment 6 George Goldberg 2008-06-16 05:32:07 UTC
Great, we've tracked down this issue! However, there's not a lot we can do about the general state of nvidia drivers so I'm going to close this bug.
Comment 7 Jim Spaloss 2008-06-18 00:34:24 UTC
Thanks again for your help! KDE 4.1 is awesome!

On Sun, Jun 15, 2008 at 11:32 PM, George Goldberg <
grundleborg@googlemail.com> wrote:

[bugs.kde.org quoted mail]
Thanks again for your help! KDE 4.1 is awesome!<br><br><div class="gmail_quote">On Sun, Jun 15, 2008 at 11:32 PM, George Goldberg &lt;<a href="mailto:grundleborg@googlemail.com">grundleborg@googlemail.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------<br>
You reported the bug, or are watching the reporter.<br>
<br>
<a href="http://bugs.kde.org/show_bug.cgi?id=163505" target="_blank">http://bugs.kde.org/show_bug.cgi?id=163505</a><br>
</div><div class="Ih2E3d">grundleborg googlemail com changed:<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; What &nbsp; &nbsp;|Removed &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Added<br>
----------------------------------------------------------------------------<br>
</div> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Status|UNCONFIRMED &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |RESOLVED<br>
 &nbsp; &nbsp; &nbsp; &nbsp; Resolution| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|WORKSFORME<br>
<br>
<br>
<br>
------- Additional Comments From grundleborg googlemail com &nbsp;2008-06-16 05:32 -------<br>
Great, we&#39;ve tracked down this issue! However, there&#39;s not a lot we can do about the general state of nvidia drivers so I&#39;m going to close this bug.<br>
</blockquote></div><br>
Comment 8 FiNeX 2008-06-18 18:21:43 UTC
Not it seems works, with the same nvidia drivers ...