Bug 314171 - kget's gui always failed to display/show
Summary: kget's gui always failed to display/show
Status: RESOLVED WORKSFORME
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: 2.9.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-31 08:00 UTC by Danny Inna Diaspora
Modified: 2013-08-01 03:31 UTC (History)
0 users

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 Danny Inna Diaspora 2013-01-31 08:00:25 UTC
Application: kget (2.9.5)
KDE Platform Version: 4.9.5
Qt Version: 4.8.2
Operating System: Linux 3.2.0-32-generic-pae i686
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I lunch the kget application on normal circumstance
- Unusual behavior I noticed:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work.
"/usr/bin/kget(2909)" Soprano: "Could not connect to server at /tmp/ksocket-groundzero/nepomuk-socket (No such file or directory)"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

The crash can be reproduced every time.

-- Backtrace:
Application: KGet (kget), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xafd1b980 (LWP 2909))]

Thread 3 (Thread 0xad766b40 (LWP 2910)):
#0  0xb1c53c3a in _nv024tls () from /usr/lib/nvidia-current-updates/tls/libnvidia-tls.so.304.64
#1  0xad76603c in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 0xacdffb40 (LWP 2911)):
#0  0xb7780424 in __kernel_vsyscall ()
#1  0xb576a5f0 in __GI___poll (fds=0xac4022b8, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0xb4e82a7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4e750ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb4e7556b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xae4b11ba in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb4e986b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb1dfc0d1 in ?? () from /usr/lib/nvidia-current-updates/libGL.so.1
#8  0x5c8b0824 in ?? ()
#9  0xbab80424 in ?? ()
#10 0x65000000 in ?? ()
#11 0x001015ff in ?? ()
#12 0xd3890000 in ?? ()
#13 0xfff0013d in ?? ()
#14 0xc30173ff in ?? ()
#15 0x0fc3a2e8 in ?? ()
#16 0xafc18100 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xafd1b980 (LWP 2909)):
[KCrash Handler]
#7  0xb7780424 in __kernel_vsyscall ()
#8  0xb576a5f0 in __GI___poll (fds=0x8e4a118, nfds=9, timeout=999) at ../sysdeps/unix/sysv/linux/poll.c:87
#9  0xb4e82a7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb4e750ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb4e75201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#12 0xb65e6d57 in QEventDispatcherGlib::processEvents (this=0x8e148e8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#13 0xb5b57a1a in QGuiEventDispatcherGlib::processEvents (this=0x8e148e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0xb65b267d in QEventLoop::processEvents (this=0xbff7cd54, flags=...) at kernel/qeventloop.cpp:149
#15 0xb65b2919 in QEventLoop::exec (this=0xbff7cd54, flags=...) at kernel/qeventloop.cpp:204
#16 0xb65b831a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#17 0xb5a9c9c4 in QApplication::exec () at kernel/qapplication.cpp:3817
#18 0x08068921 in main (argc=<error reading variable: Cannot access memory at address 0x9>, argv=<error reading variable: Cannot access memory at address 0xd>) at ../../kget/main.cpp:149

Possible duplicates by query: bug 314085, bug 314048, bug 313804, bug 313361, bug 313220.

Reported using DrKonqi
Comment 1 Lukas Appelhans 2013-03-07 10:41:16 UTC
To my eye this looks rather like a crash in some nvidia code?

Lukas
Comment 2 Danny Inna Diaspora 2013-07-29 09:23:26 UTC
Hi there,
Thanks.m((
After staying off online, just came back yesterday.
I decided to start with system update, which updated quite lots of stuff on
the system.
Anyway, after updating to Version 2.10.5 on KDE Development Platform
4.10.5, the KGet gui seems to be back on KUbuntu KDE at least.
Am not really sure of this on the default Ubuntu Unity desktop but I will
still try it on Unity.
In the main time, another long standing major problem is wifi still unable
to work and not even detectable by latest system(kernel) update.
Any (community) help link on that will be appreciated so much.


On Thu, Mar 7, 2013 at 11:41 AM, Lukas Appelhans <l.appelhans@gmx.de> wrote:

> https://bugs.kde.org/show_bug.cgi?id=314171
>
> --- Comment #1 from Lukas Appelhans <l.appelhans@gmx.de> ---
> To my eye this looks rather like a crash in some nvidia code?
>
> Lukas
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 3 Jekyll Wu 2013-08-01 03:31:34 UTC
Thanks for the update. For your wifi problem, please use forum.kde.org or other channels which are more appropriate for user support.