Bug 12099 - Kdevelop hangs on startup (nvidia)
Summary: Kdevelop hangs on startup (nvidia)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 12079
  Show dependency treegraph
 
Reported: 2013-12-23 21:56 CET by MichaÅ Walenciak
Modified: 2014-02-19 21:02 CET (History)
6 users (show)

See Also:
Source RPM: kdevelop4-4.6.0-1.mga4.src.rpm
CVE:
Status comment:


Attachments

Description MichaÅ Walenciak 2013-12-23 21:56:47 CET
Description of problem:
When I start KDevelop it hangs on a startup (at 63 or 78%).
What's interesting here - if I try to run it from gdb or strace it starts normally. When I attached with gdb to hanged instance it looks like it hanged on plugins load.

I'm using caludron, updated from mageia 3 about 3 days ago (20th December)


Version-Release number of selected component (if applicable):


How reproducible:
Every time I run kdevelop

Steps to Reproduce:
1. run kdevelop


Reproducible: 

Steps to Reproduce:
MichaÅ Walenciak 2013-12-23 21:57:05 CET

CC: (none) => Kicer86

Comment 1 Nicolas Lécureuil 2013-12-23 23:29:13 CET
i can't reproduce.

Please make sure your cauldron is completly udpdated.

CC: (none) => mageia

Comment 2 MichaÅ Walenciak 2013-12-24 11:46:46 CET
urpmi --auto-update says it's all updated.

Please take a look at my another, similar bug. There is a little more info:
https://bugs.mageia.org/show_bug.cgi?id=12106
Florian Hubold 2013-12-27 19:53:28 CET

Blocks: (none) => 12079

Comment 3 Florian Hubold 2013-12-27 19:53:48 CET
(In reply to Nicolas Lécureuil from comment #1)
> i can't reproduce.
> 
> Please make sure your cauldron is completly udpdated.

@neoclust: please have a look at https://bugs.mageia.org/show_bug.cgi?id=12079#c3
This is caused by more recent version of nvidia proprietary driver.
Manuel Hiebel 2013-12-27 19:55:56 CET

Summary: Kdevelop hangs on startup => Kdevelop hangs on startup (nvidia)

Comment 4 Anne Nicolas 2014-01-19 21:34:35 CET
Reporter can you please test again using RC isos or up-to-date cauldron?

CC: (none) => ennael1

Comment 5 MichaÅ Walenciak 2014-01-28 23:42:03 CET
Yes I still have this issue.
As far as I understand this is related to nvidia problems, but since I've reported this bug I didn't get any nvidia updates. My current versions of rpms I use are:

rpm -qa | grep nvidia
nvidia-current-doc-html-331.20-10.mga4.nonfree
nvidia-current-cuda-opencl-331.20-10.mga4.nonfree
x11-driver-video-nvidia-current-331.20-10.mga4.nonfree
nvidia-current-kernel-desktop-latest-331.20-15.mga4.nonfree
nvidia-current-kernel-3.12.6-desktop-2.mga4-331.20-15.mga4.nonfree
dkms-nvidia-current-331.20-10.mga4.nonfree

Are they fresh enougth?
Maybe I have some problems with repo servers.

I've updated rpms with urpmi --auto-update today
Comment 6 Sander Lepik 2014-01-29 08:55:51 CET
You should switch to nouveau (and reboot). Then remove all nvidia related packages and use MCC to switch to proprietary drivers again. We switched back to 325.

CC: (none) => mageia

Comment 7 MichaÅ Walenciak 2014-01-29 22:27:20 CET
unfortunately it still doesn't work.
KDevelop hangs and when I attach to it I get bt:


#0  0x00007f2d2ad320c9 in ?? () from /usr/lib64/nvidia-current/libGL.so.1
#1  0x00007f2d29d5b6ac in ?? () from /usr/lib64/nvidia-current/tls/libnvidia-tls.so.325.15
#2  0x00007f2c816f6361 in p11_mmap_close () from /lib64/libp11-kit.so.0
#3  0x00007f2c816ddc36 in _p11_conf_parse_file () from /lib64/libp11-kit.so.0
#4  0x00007f2c816de2f0 in _p11_conf_load_globals () from /lib64/libp11-kit.so.0
#5  0x00007f2c816ea3e6 in load_registered_modules_unlocked.part.7 () from /lib64/libp11-kit.so.0
#6  0x00007f2c816eb195 in p11_kit_initialize_registered () from /lib64/libp11-kit.so.0
#7  0x00007f2c81fa2308 in gnutls_pkcs11_init () from /lib64/libgnutls.so.28
#8  0x00007f2c81f8bf14 in gnutls_global_init () from /lib64/libgnutls.so.28
#9  0x00007f2c8271015a in inf_init () from /lib64/libinfinity-0.5.so.0
#10 0x00007f2c83b26288 in KteCollaborativePlugin::KteCollaborativePlugin(QObject*, QList<QVariant> const&) ()
   from /usr/lib64/kde4/ktexteditor_collaborative.so
#11 0x00007f2c83b28248 in QObject* KPluginFactory::createInstance<KteCollaborativePlugin, QObject>(QWidget*, QObject*, QList<QVariant> const&) () from /usr/lib64/kde4/ktexteditor_collaborative.so


/usr/lib64/nvidia-current/libGL.so.1 is from:
$ rpm -qf /usr/lib64/nvidia-current/libGL.so.1
x11-driver-video-nvidia-current-325.15-1.mga4.nonfree

my nvidia rpms:
$ rpm -qa | grep nvidia
x11-driver-video-nvidia-current-325.15-1.mga4.nonfree
nvidia-current-doc-html-325.15-1.mga4.nonfree
nvidia-current-kernel-desktop-latest-325.15-6.mga4.nonfree
dkms-nvidia-current-325.15-1.mga4.nonfree
nvidia-current-cuda-opencl-325.15-1.mga4.nonfree
nvidia-current-kernel-3.12.8-desktop-2.mga4-325.15-6.mga4.nonfree

I've rebooted pc after installing new drivers and nvidia-settings says 3.25 drivers are being used.
Comment 8 Florian Hubold 2014-02-03 13:33:54 CET
After upgrading to Mageia 4, with 325.15 kdevelop starts just fine here.

CC: (none) => doktor5000

Comment 9 MichaÅ Walenciak 2014-02-03 22:21:13 CET
Not here

Is it possible there are some corrupted settings, cache files etc around?
Also kwrite/kate still hangs (only in Kde4, not under Xfce4)
Comment 10 Florian Hubold 2014-02-03 23:16:59 CET
(In reply to MichaÅ Walenciak from comment #9)
> Not here
> 
> Is it possible there are some corrupted settings, cache files etc around?
Could be, you can easily test with a newly created user.

> Also kwrite/kate still hangs (only in Kde4, not under Xfce4)
This bug is about kdevelop. For kwrite and kate, see the other bugs linked from https://bugs.mageia.org/show_bug.cgi?id=12079
Comment 11 MichaÅ Walenciak 2014-02-04 19:45:49 CET
Still doesn't work (hangs) even on a brand new user
Comment 12 Piotr Mierzwinski 2014-02-15 01:49:27 CET
(In reply to MichaÅ Walenciak from comment #11)
> Still doesn't work (hangs) even on a brand new user

I don't know if found solution, but I found and I would like to share it.
Please check this thread: https://bugs.mageia.org/show_bug.cgi?id=11946 especially post from: Luc Menut  2014-02-08 21:49:33 CET

He has provided solution what works for me and others in this thread.

Briefly
The simplest way to fix it is:
mv /etc/pkcs11/pkcs11.conf /etc/pkcs11/pkcs11.conf.bak
or (because this file is the most likely empty):
echo " " >> /etc/pkcs11/pkcs11.conf

Unfortunately Mageia team didn't provide (for ver.4) this workaround for nVidia graphics card's users like some update . :/

--
regards

CC: (none) => piotr.mierzwinski
Hardware: x86_64 => i586
Version: Cauldron => 4

Comment 13 Sander Lepik 2014-02-15 12:49:44 CET
Update for p11-kit and related packages has been pushed. Please update and report back. I think we can close this bug.
Comment 14 Piotr Mierzwinski 2014-02-15 22:25:56 CET
Thanks. I can confirm for Mageia 4 32bit version that now all is fine.
Update comes with package: p11-kit-0.20.1-3.3.mga4
File /etc/pkcs11/pkcs11.conf is correctly updated.
From my side you can close this bug.
Comment 15 Piotr Mierzwinski 2014-02-15 22:28:34 CET
Mageia 4 32bit version:
Update comes with package: p11-kit-0.20.1-3.3.mga4
File /etc/pkcs11/pkcs11.conf is correctly updated.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 16 MichaÅ Walenciak 2014-02-19 21:02:48 CET
yeah I can confirm that too. Finaly works:)

Note You need to log in before you can comment on or make changes to this bug.