Kubuntu Jaunty - plasma crashed with SIGSEGV, when laptop mounted on docking station

Bug #342438 reported by Musthafa Meeran
0
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
New
Undecided
Unassigned

Bug Description

Yesterday I updated from Intrepid to Jaunty, since I very much like KDE 4.2. It was working smoothly in Intrepid, but after upgrading to Jaunty, I encountered the following problems.

Reporting a new bug, since the bug raised by apport (plasma crashed with SIGSEGV https://bugs.launchpad.net/bugs/342223) was closed automatically !!

When my laptop is mounted in the docking station, the laptop screen resolution is wrongly detected as "1152x864" instead of the original "1440x900" (in kdm as well as after login). When not mounted in docking station, it is correctly identified.
This was working fine in Intrepid with KDE 4.2.

And KDE always starts with no plasma and black blank screen. When I try to start plasma using krunner or konsole, it crashes. But it starts without any problem, when not mounted in docking station.
Again, this was working fine in Intrepid with KDE 4.2.

So, it looks like a problem with the new kernel or the xorg video driver, which I am not sure.

HP/Compaq nc6400 laptop

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

$ uname -a
Linux <hostname> 2.6.28-9-generic #31-Ubuntu SMP Wed Mar 11 15:43:58 UTC 2009 i686 GNU/Linux

$ glxinfo | grep render
get fences failed: -1
param: 6, val: 0
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) 945GM GEM 20090114 x86/MMX/SSE2

Plasma crash report generated by apport for the old bug::
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb80d4430:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/plasma
Package: kdebase-workspace-bin 4:4.2.1a-0ubuntu3
ProcCmdline: /usr/bin/plasma
ProcEnviron:
 PATH=(custom, user)
 LANG=en_IN
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace: #0 0xb80d4430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: plasma crashed with SIGSEGV
Uname: Linux 2.6.28-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

http://launchpadlibrarian.net/23821617/CoreDump.gz
http://launchpadlibrarian.net/23821618/Dependencies.txt
http://launchpadlibrarian.net/23821619/ProcMaps.txt
http://launchpadlibrarian.net/23821620/ProcStatus.txt
http://launchpadlibrarian.net/23821621/Registers.txt

Could you please help me in fixing these issues?
Please let me know what are all the information that I need to provide and I ll attach them here.

Thanks a lot in advance....

Following are the attachments related to the above issues

Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :
Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :

The duplicate bug #338205 says that the plasma crash issue is resolved.

But the wrong screen resolution issue still remains.

Could you please have a look at this bug from this perspective and help me out with this?

Thanks in advance...

Revision history for this message
Jonathan Thomas (echidnaman) wrote : Re: Kubuntu Jaunty - laptop docking station problem - wrong screen resolution

It says fix committed, not fix released. (which would be resolved)

Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :

Hi, sorry, pardon me for using the wrong terminology.

Do I need to report a new bug for the screen resolution issue?

Thanks a lot....

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

You would want to report the resolution issue separately.

Revision history for this message
Musthafa Meeran (musthafameeran-deactivatedaccount) wrote :

Thanks a lot, will report separately.

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

Other bug subscribers

Remote bug watches

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