crash if i press F12

Bug #118574 reported by David Heidelberg
6
Affects Status Importance Assigned to Milestone
yakuake
Invalid
Unknown
yakuake (Ubuntu)
Confirmed
Low
Rich Johnson

Bug Description

Binary package hint: yakuake

KDE start, yakuake too. I press F12, start in first shell "wget ftp://...", add "shell no. 2". If i now press F12, Xorg crash(back to kdm).

I using amd64 kubuntu 7.04, with nvidia drivers(lastest from official rep.), KDE 3.5.7
-------------------
cat /var/log/Xorg.0.log.old

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48282d]
1: /lib/libc.so.6 [0x2ab3269fdd40]
2: /usr/bin/X [0x517e8c]
3: /usr/bin/X [0x5181f3]
4: /usr/bin/X [0x51434c]
5: /usr/bin/X [0x509f8b]
6: /usr/bin/X(Dispatch+0x1cb) [0x44df4b]
7: /usr/bin/X(main+0x45d) [0x43703d]
8: /lib/libc.so.6(__libc_start_main+0xf4) [0x2ab3269ea8e4]
9: /usr/bin/X(FontFileCompleteXLFD+0x241) [0x436339]

Fatal server error:
Caught signal 11. Server aborting

-------------------

David Heidelberg (okias)
Changed in yakuake:
status: Unconfirmed → Confirmed
Revision history for this message
Rich Johnson (nixternal) wrote :

I just tested this on Feisty and Gutsy and cannot reproduce. I am using the FGLRX drivers on my amd64 box which is Feisty using yakuake 2.7.5-4ubuntu2. On my Gutsy box I am using an Intel driver with yakuake 2.8~beta1-1ubuntu1.

Can anyone else reproduce utilizing the "nvidia" driver and not the "nv" driver?

Changed in yakuake:
status: Confirmed → Needs Info
Revision history for this message
plosco (plosco+linux) wrote :

Hi,

I have exactly the same pb than the logger.
Yet, I can't reproduce it systemaically!

My conf is the following:
 * intel core duo
 * kubuntu feisty 7.0.4
 * nvidia 7600 Go with new glx driver
 * yakuake 2.7.5 (installed via adept)

regards

Phil

Revision history for this message
David Heidelberg (okias) wrote :

same problem, crashing xorg-server on Gentoo testing, with:
* kernel 2.6.21
* xorg-server 1.3
* yakuake 2.8

i dont must press F12, yakuake with xserver crash... :-(

Revision history for this message
Rich Johnson (nixternal) wrote :

Confirming due to responses. I will speak with the Yakuake dev on this and see if we can figure this out. Thanks everyone for the responses!

Changed in yakuake:
importance: Undecided → Low
status: Incomplete → Confirmed
Revision history for this message
Rich Johnson (nixternal) wrote :

http://bugs.kde.org/show_bug.cgi?id=136496

There was a report of this in the KDE bug tracker. I will report this in the KDE bug tracker as well.

Revision history for this message
Friedemann Schorer (friedemann-schorer) wrote :

I'd like to confirm this bug to be existing in Kubuntu Gutsy, too. Running on an IBM Z61m with Intel 945GM graphics chipset, using KDE 3.5.8 and Compiz 0.6.2 (earlier version of compiz had the same problem).

Changed in yakuake:
status: Unknown → Invalid
Revision history for this message
Shashank Chintalagiri (shashank-chintalagiri) wrote :

I can confirm that this happens on Ubuntu Gutsy with the nvidia drivers. I'm abe to reproduce it with more or less 100% accuracy. Open two tabs, with the second one active. Run some X-application from it (I'm not sure if its all or just a few - I've seen it happen with mplayer and deluge) and X crashes. The time taken to get back to the kdm/gdm varies from time to time.

Revision history for this message
Rich Johnson (nixternal) wrote :

Does this happen if you use a different shortcut than F12? I use ctrl~ and I can't reproduce this with either yakuake 2.8.1-1ubuntu2 (KDE 3) or yakuake 2.9.1-0ubuntu1 (KDE 4). Can anyone confirm this in Hardy at all while not using Compiz?

Changed in yakuake:
assignee: nobody → nixternal
Revision history for this message
Rich Johnson (nixternal) wrote :

Marking as duplicate of bug #126732. This is also been confirmed by X developers to not be a Yakuake issue but an issue with X as every distro is having this same exact problem. The problem only occurs when using compositing and seems that it doesn't matter which video driver you use. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.