Bug 246121 - crashed while running startx from recovery mode
Summary: crashed while running startx from recovery mode
Status: RESOLVED DUPLICATE of bug 248348
Alias: None
Product: knetworkmanager
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-29 08:00 UTC by Liam FItzpatrick
Modified: 2011-01-23 18:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Liam FItzpatrick 2010-07-29 08:00:50 UTC 
Application: knetworkmanager (v0.9)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
with a normal startup I got to the X login prompt which accepted my username+password, progressed a little and then restarted X.

I rebooted in recovery mode and ran startx from the command line. X+KDE seemed to start fine but then this crash happened.

 -- Backtrace:
Application: KNetworkManager (knetworkmanager), signal: Segmentation fault
[KCrash Handler]
#6  QList (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qlist.h:114
#7  QDBusMessage::arguments (this=0x8) at qdbusmessage.cpp:664
#8  0x003149b4 in QDBusPendingReplyData::argumentAt (this=0xbff74b94, index=0) at qdbuspendingreply.cpp:268
#9  0x002752dd in NMDBusSettingsConnectionProvider::initConnections() () from /usr/lib/libknm_nm.so
#10 0x00275b79 in NMDBusSettingsConnectionProvider::NMDBusSettingsConnectionProvider(ConnectionList*, QString const&, QObject*) () from /usr/lib/libknm_nm.so
#11 0x080545fa in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-23 18:42:16 UTC 
[Comment from a bug triager]
This issue is being tracked at bug 248348. Merging. Thanks

*** This bug has been marked as a duplicate of bug 248348 ***