kcmshell4 crashed with SIGSEGV in QDataStream::operator>>()

Bug #407446 reported by FFab
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Base
Invalid
High
kdebase-workspace (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kdebase-runtime

Message after Calling "Anmeldungsmanager"

ProblemType: Crash
Architecture: i386
Date: Fri Jul 31 19:49:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kcmshell4
Package: kdebase-runtime 4:4.2.98-0ubuntu3
ProcCmdline: /usr/bin/kcmshell4 kdm --lang de
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0xb3fa50 <_ZN11QDataStreamrsERi+32>: mov 0x8(%esi),%eax
 PC (0x00b3fa50) ok
 source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdebase-runtime
StacktraceTop:
 QDataStream::operator>>(int&) ()
 KServiceFactory::KServiceFactory() ()
 KServiceFactory::self() () from /usr/lib/libkdecore.so.5
 KService::serviceByMenuId(QString const&) ()
 KService::serviceByStorageId(QString const&) ()
Title: kcmshell4 crashed with SIGSEGV in QDataStream::operator>>()
Uname: Linux 2.6.31-4-generic i686
UserGroups:

Revision history for this message
FFab (ffab) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QDataStream::operator>> (this=0x0, i=@0xbfff0bfc)
KServiceFactory (this=0x909fd88)
KServiceFactory::self ()
KService::serviceByMenuId (_name=@0xbfff0d2c)
KService::serviceByStorageId (_storageId=@0xbfff0d2c)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdebase-runtime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Your bug has been reported to the developers of the software. You can track its progress and make further comments at: http://bugs.kde.org/show_bug.cgi?id=202145

affects: kdebase-runtime (Ubuntu) → kdebase-workspace (Ubuntu)
Changed in kdebase-workspace (Ubuntu):
importance: Medium → Low
status: New → Triaged
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi,
KDE would like to know a few things:
-Does only the Anmeldungsmanager (login manager) section do this?
-Does it ask you for your password before you can access the section?
-Does this always happen when you try to access the login manager section?

Thanks in advance.

visibility: private → public
Changed in kdebase-workspace (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
FFab (ffab) wrote : RE: [Bug 407446] Re: kcmshell4 crashed with SIGSEGV inQDataStream::operator>>()

Hi,
I can't reproduce the bug.
I only remember the following:
in order to get a solution for bug #407141 I was looking whether changes of systemsettings could help - after Energieverwaltung (?energy administration?) and restart I tried to change settings in the Anmeldungsmanager (login manager) - and got the error message.
I don't know whether I have been asked for a password - when I now call login manager, I'm asked for the password.
Meanwhile I have updated the system.
Sorry I can't give more information.
FFab

>Hi,
>KDE would like to know a few things:
>-Does only the Anmeldungsmanager (login manager) section do this?
>-Does it ask you for your password before you can access the section?
>-Does this always happen when you try to access the login manager section?
>
>Thanks in advance.
>
>** Also affects: kdebase via
> http://bugs.kde.org/show_bug.cgi?id=202145
> Importance: Unknown
> Status: Unknown
>
>** Visibility changed to: Public
>
>** Changed in: kdebase-workspace (Ubuntu)
> Status: Triaged => Incomplete
>
>--
>kcmshell4 crashed with SIGSEGV in QDataStream::operator>>()
>https://bugs.launchpad.net/bugs/407446
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in KDE Base Components: Unknown
>Status in “kdebase-workspace” package in Ubuntu: Incomplete
>
>Bug description:
>Binary package hint: kdebase-runtime
>
>Message after Calling "Anmeldungsmanager"
>
>ProblemType: Crash
>Architecture: i386
>Date: Fri Jul 31 19:49:42 2009
>DistroRelease: Ubuntu 9.10
>ExecutablePath: /usr/bin/kcmshell4
>Package: kdebase-runtime 4:4.2.98-0ubuntu3
>ProcCmdline: /usr/bin/kcmshell4 kdm --lang de
>ProcEnviron:
> LANGUAGE=
> PATH=(custom, no user)
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
>ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
>SegvAnalysis:
> Segfault happened at: 0xb3fa50 <_ZN11QDataStreamrsERi+32>: mov
>0x8(%esi),%eax
> PC (0x00b3fa50) ok
> source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed
>readable region)!
> destination "%eax" ok
>SegvReason: reading NULL VMA
>Signal: 11
>SourcePackage: kdebase-runtime
>StacktraceTop:
> QDataStream::operator>>(int&) ()
> KServiceFactory::KServiceFactory() ()
> KServiceFactory::self() () from /usr/lib/libkdecore.so.5
> KService::serviceByMenuId(QString const&) ()
> KService::serviceByStorageId(QString const&) ()
>Title: kcmshell4 crashed with SIGSEGV in QDataStream::operator>>()
>Uname: Linux 2.6.31-4-generic i686
>UserGroups:

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

Another thing that they want to know is if you have updated your packages since you first experienced this crash. (They think it could possibly be an installation problem)

Changed in kdebase:
status: Unknown → Confirmed
Revision history for this message
FFab (ffab) wrote :

I have updated the packages - and couldn't reproduce the bug. (see my last mail).

>Another thing that they want to know is if you have updated your
>packages since you first experienced this crash. (They think it could
>possibly be an installation problem)
>
>--
>kcmshell4 crashed with SIGSEGV in QDataStream::operator>>()
>https://bugs.launchpad.net/bugs/407446
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in KDE Base Components: Unknown
>Status in “kdebase-workspace” package in Ubuntu: Incomplete
>
>Bug description:
>Binary package hint: kdebase-runtime
>
>Message after Calling "Anmeldungsmanager"
>
>ProblemType: Crash
>Architecture: i386
>Date: Fri Jul 31 19:49:42 2009
>DistroRelease: Ubuntu 9.10
>ExecutablePath: /usr/bin/kcmshell4
>Package: kdebase-runtime 4:4.2.98-0ubuntu3
>ProcCmdline: /usr/bin/kcmshell4 kdm --lang de
>ProcEnviron:
> LANGUAGE=
> PATH=(custom, no user)
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
>ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
>SegvAnalysis:
> Segfault happened at: 0xb3fa50 <_ZN11QDataStreamrsERi+32>: mov
>0x8(%esi),%eax
> PC (0x00b3fa50) ok
> source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed
>readable region)!
> destination "%eax" ok
>SegvReason: reading NULL VMA
>Signal: 11
>SourcePackage: kdebase-runtime
>StacktraceTop:
> QDataStream::operator>>(int&) ()
> KServiceFactory::KServiceFactory() ()
> KServiceFactory::self() () from /usr/lib/libkdecore.so.5
> KService::serviceByMenuId(QString const&) ()
> KService::serviceByStorageId(QString const&) ()
>Title: kcmshell4 crashed with SIGSEGV in QDataStream::operator>>()
>Uname: Linux 2.6.31-4-generic i686
>UserGroups:

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

Ok, thanks. This was probably just an installation/configuration issue. Please reopen the bug if the crash happens again.

Changed in kdebase-workspace (Ubuntu):
status: Incomplete → Invalid
Changed in kdebase:
status: Confirmed → Invalid
Changed in kdebase:
importance: Unknown → High
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.