Bug 12244 - kwrite digikam and kdenlive don't start beyond bouncing cursor but max CPU - 4RC
Summary: kwrite digikam and kdenlive don't start beyond bouncing cursor but max CPU - 4RC
Status: RESOLVED DUPLICATE of bug 12079
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard: 4RC
Keywords:
Depends on:
Blocks: 11704 12079
  Show dependency treegraph
 
Reported: 2014-01-08 18:02 CET by claire robinson
Modified: 2014-02-03 13:39 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
snapshot1.png showing oxygen widget style selected. (83.59 KB, image/png)
2014-01-14 17:48 CET, claire robinson
Details
snapshot2.png showing gtk+ stlye widgets selected (85.50 KB, image/png)
2014-01-14 17:48 CET, claire robinson
Details

Description claire robinson 2014-01-08 18:02:20 CET
Classic 4RC DVD 32 with default kde installation

kwrite digikam & kdenlive don't produce a GUI but sit taking 100% cpu



Reproducible: 

Steps to Reproduce:
claire robinson 2014-01-08 18:24:35 CET

Whiteboard: (none) => 4RC

Comment 1 claire robinson 2014-01-08 18:47:48 CET
All 3 start ok when run under gdb, similar symptoms to claws-mail in bug 11666
Comment 2 Hugo Pereira Da Costa 2014-01-13 19:23:27 CET
Could it be related to using a NVidia card ? 
(can't start gwenview on nvidia here, and heard on the mailing list that it was related to latest nvidia non free kernel).
in any case this one is unrelated to oxygen-gtk.

CC: (none) => hugo.pereira

Comment 3 Hugo Pereira Da Costa 2014-01-13 19:29:10 CET
Does these applications starts when using nouveau as a driver (in case nvidia-non-free was used) ?
Comment 4 claire robinson 2014-01-13 20:23:45 CET
Some cross bug chat on bug 12290 so bringing the relevant info here.

After changing the widget style in kde to gtk kdenlive and kwrite do start but digikam still not.
Comment 5 claire robinson 2014-01-14 17:47:25 CET
Updating kde stuff in this bug rather than cheese bug and a more thorough test.

Clean kde install from classic 4RC dvd 32

$ rpm -qa | grep oxygen | sort
icewm-theme-oxygen-aya-0.1-6.mga4
liboxygen-gtk-1.4.2-0.rc1.1.mga4
liboxygen-gtk3-1.3.2-0.rc1.1.mga4
liboxygenstyle4-4.11.4-1.mga4
liboxygenstyleconfig4-4.11.4-1.mga4
oxygen-gtk-1.4.2-0.rc1.1.mga4
oxygen-gtk3-1.3.2-0.rc1.1.mga4
oxygen-icon-theme-4.11.4-1.mga4

Kwrite did start this time if started from the terminal but not from the menu.

Current widget theme in kde system settings is Oxygen. I took screenshots to show the difference.

kdenlive, digikam zombify & kwrite is as above.

Changed to "GTK+ Style" widgets and applied the change.

Digikam still zombifies and kwrite still zombifies if started from the menu, but kdenlive now does starts from either terminal or menu.

Changing back to Oxygen widget style again, kdenlive zombifies again.

$ kdenlive
No LADSPA plugins were found!

Check your LADSPA_PATH environment variable.
^C

So kdenlive is fixed by changing widget styles. The others remain the same.
Comment 6 claire robinson 2014-01-14 17:48:11 CET
Created attachment 4781 [details]
snapshot1.png showing oxygen widget style selected.
Comment 7 claire robinson 2014-01-14 17:48:52 CET
Created attachment 4782 [details]
snapshot2.png showing gtk+ stlye widgets selected
Comment 8 Hugo Pereira Da Costa 2014-01-14 18:12:24 CET
all clear, thanks. (not that I have any clue about what's going on though)
claire robinson 2014-01-23 19:57:12 CET

Blocks: (none) => 11704

William Kenney 2014-01-23 23:22:03 CET

CC: (none) => wilcal.int

claire robinson 2014-01-24 10:02:11 CET

Blocks: (none) => 12079

Comment 9 Florian Hubold 2014-02-03 13:39:52 CET
Can we close this bug as kwrite, digikam & kdenlive have their own bugs, all tracked from https://bugs.mageia.org/show_bug.cgi?id=12079

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

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


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