Bug 12289 - Pidgin doesn't start - it zombifies with 100% CPU - 4RC
Summary: Pidgin doesn't start - it zombifies with 100% CPU - 4RC
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Damien Lallement
QA Contact:
URL:
Whiteboard: 4RC
Keywords:
Depends on:
Blocks: 11704
  Show dependency treegraph
 
Reported: 2014-01-13 17:55 CET by claire robinson
Modified: 2014-02-21 00:04 CET (History)
7 users (show)

See Also:
Source RPM: pidgin
CVE:
Status comment:


Attachments

Description claire robinson 2014-01-13 17:55:07 CET
Classic 4RC DVD 32 with multi desktops installed

Pidgin doesn't produce a window. It zombifies and sits there taking 100% of one core.

There are similar others so may be theme related etc. 

See bug 12244 for kwrite, digikam & kdenlive, bug 11666 for claws-mail and I'm about to create a similar bug for cheese.


Reproducible: 

Steps to Reproduce:
claire robinson 2014-01-13 17:55:59 CET

CC: (none) => ennael1, hugo.pereira
Whiteboard: (none) => 4RC

Comment 1 claire robinson 2014-01-13 18:41:02 CET
As with the others, pidgin does start properly under gdb.
Comment 2 Hugo Pereira Da Costa 2014-01-13 19:24:40 CET
Same comment as with cheese:

There must be some multiple bug reports merged, since pidgin is a gtk application, while kwrite, digikam, and kdelive are Qt
They have zero code in common.

Also: cannot reproduce with latest cauldron.
Comment 3 Hugo Pereira Da Costa 2014-01-13 19:26:31 CET
Does the application start when selecting another widget style for gtk ? (e.g. Raleigh) ?
Thierry Vignaud 2014-01-13 19:27:17 CET

CC: (none) => fundawang, jani.valimaa, shlomif

claire robinson 2014-01-25 20:14:55 CET

Blocks: (none) => 11704

Comment 4 Charly Pammer 2014-02-07 17:37:50 CET
I can reproduce the problem on my installation (Mageia 4 upgradeed from Mageia 3). Pidgin uses 100% CPU when started from terminal. When started with strace or gdb it works.

I tried widget styles Raleigh, Adwaita and Aurora. Changing the style did not improve the situation.

As the other bug reports mentioned the Nvidia driver as a possible culprit: I am using dkms-nvidia-current-325.15-1.mga4.nonfree.
Pidgin version used is pidgin-2.10.9-1.mga4

CC: (none) => mageia.bugzilla

Comment 5 Charly Pammer 2014-02-07 17:43:47 CET
changed platform to "all" because I have the problem on a 64bit installation.

Hardware: i586 => All

Comment 6 Charly Pammer 2014-02-14 18:43:12 CET
I have two Mageia4 installions running, both using the proprietary NVIDIA driver (dkms-nvidia-current-325.15-1.mga4.nonfree) and Adwaita GTK theme.

One installation (Updated from Mageia3, NVIDIA GK107 [GeForce GT 640]) which shows the problem. Pidgin only runs via strace/gdb

On the second installation (newly installed, NVIDIA G96GL [Quadro FX 580], Pidgin works fine out of the box.

I tried to switch the from the proprietary NVIDIA driver to nouveau/nv on the first installation for testing purposes. Unfortunately, X will not start, with these drivers.
Comment 7 Charly Pammer 2014-02-20 17:26:54 CET
For me Pidgin works now on both installations.

With reference to the Errata (https://wiki.mageia.org/en/Mageia_4_Errata#nvidia_proprietary_drivers). Maybe the updates for the p11-kit* did the trick.
Comment 8 Shlomi Fish 2014-02-20 20:51:30 CET
Hi Charly!

(In reply to Charly Pammer from comment #7)
> For me Pidgin works now on both installations.
> 
> With reference to the Errata
> (https://wiki.mageia.org/en/Mageia_4_Errata#nvidia_proprietary_drivers).
> Maybe the updates for the p11-kit* did the trick.

thanks for the confirmation. Is this caused by the nvidia proprietary drivers, and can we close this bug?

Regards,

-- Shlomi Fish
Comment 9 Florian Hubold 2014-02-21 00:04:04 CET
pidgin starts fine here, confirming fixed.

This should be fixed since 5 days with the p11-kit updates:
https://wiki.mageia.org/en/Mageia_4_Errata#nvidia_proprietary_drivers

Please reopen if problem persists.

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


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