Unlike the others, cheese doesn't start properly under gdb.

It can be seen as a square where cheese should be when gnome menu is opened but an empty square.


One error when starting cheese, not none as I remembered it ..

(cheese:23405): Glib-GObject-WARNING ***: value "5.000000" of type 'gdouble' is invalid or out of range for property 'delaytime' of type 'gdouble'

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.
Does the application start when selecting another widget style for gtk ? (e.g. Raleigh) ?

Note that Hugo doesn't received messages when it's cc:ed on bugs

CC: (none) => olav
Source RPM: (none) => cheese

@Thierry
well, I did recieve the one from Claire (at comment #1; not #0).
Same for bug #12289

Not the others (but they are unrelated to oxygen-gtk anyway)

... and it is not clear (at least to me, sorry), that these one are either, actually ...

Thanks for the quick response Hugo, as always :)

Excuse the cross bug chat, it could be nvidia related, at least I do have nvidia here. The current nvidia driver is supposedly clear of the issues affecting later releases (3.25).

I was just trying to think what joins them all together, some qt, some gtk and all except this one start when run under gdb.

I'll try changing the widget style in gnome, not all that familiar with Gnome though so may be some time /o\

@Claire
Thanks for the extra info.
So: nvidia is off the hook. Good :)

Also, I will try running with a gnome session (maybe issue can occur there: I only tested with KDE).

For changing the widget style: gnome-tweak-tool should do the trick (I think) for gtk3 applications. For gtk2, I know only the kde way (system settings), or manually editting $HOME/.gtkrc-2.0 (or similar)

Also: question:
for KDE applications, running under gnome, is the widget style you use "oxygen" (Qt version), or gtk+ Qt widget style (that is a wrapper that would use the gtk style, wrapped to Qt). 

the second is really buggy and will assurely cause problem if the "wrapped" gtk style is oxygen-gtk. 

We actually do _not_ support oxygen-gtk wrapped to Qt via gtk+ style, since there is a "native" oxygen for Qt.

Which leads to the next question: does the same issues occur under a KDE session ?

update:
can't make neither pidgin nor cheese hand under gnome session either.
also: cheese appear to be a gtk3 application, so gnome-tweak-tool can be use to change its style (to Adwaita)

cheese and pidgin tested under gnome after switching to adwaita and logging out/in again don't seem any different.

After changing kde to use gtk widget style kwrite and kdenlive do now start but digikam still not so.

Hi Claire,
sorry for the delay.

"cheese and pidgin tested under gnome after switching to adwaita and logging out/in again don't seem any different."
"don't seem any different" means: the still do not start ? Or they have the oxygen-gtk visual appearance ? 


"After changing kde to use gtk widget style"
Not sure I understand this. What was the old style ? What is the new one ? (for which they start) ?

(In reply to Hugo Pereira Da Costa from comment #11)
> Hi Claire,
> sorry for the delay.
> 
> "cheese and pidgin tested under gnome after switching to adwaita and logging
> out/in again don't seem any different."
> "don't seem any different" means: the still do not start ? Or they have the
> oxygen-gtk visual appearance ? 

Both actually Hugo, to my eyes anyway. I'm maybe just not accustomed to noticing stuff like this though or not looking at the right bits :\ They definitely still didn't start though.

> "After changing kde to use gtk widget style"
> Not sure I understand this. What was the old style ? What is the new one ?
> (for which they start) ?

It was previously oxygen, changed to gtk in kde system settings. I noticed the widgets change instantly but logged out/in and even rebooted to check the applications. I thought it may be coincidence, or they had somehow deposited some user settings when run under gdb which allowed them to be started normally so changed widget style back to oxygen and they ceased to work again.

ok. One step back and more testing :)
It appears that gnome-tweak-tool only works in gnome session (not KDE) to change gtk widget style, and only for gtk3 applications

Under KDE, you need to install package kde-gtk-config
Then "System settings"->"Application Appearance"->"Gtk"

From here you can change the gtk style of both gtk2 (pidgin) and gtk3 (cheese) applications. Can you do that (under KDE), make sure non-hanging applications do change style (e.g. nautilus, gedit, and even firefox) and see if pidgin/cheese still hang ?
(that could put me off the hook ... or not ...)

For the other *KDE* applications. You changed the widget style from
"System Settings"->"Application Appearance"->"Style". Correct ? 
And then it
- works with "Gtk+ Style" (that should somehow mimic oxygen-gtk, but poorly)
- does not work with "Oxygen Style". 

Did I get it right ? 

If yes, that's new; related to Oxygen-Qt (and not oxygen-gtk).

oh and still, all these applications start well here (with latest cauldron) :(

Keep me posted,

Hugo

Would this be easier to debug if you could access the ISO Hugo?

I've installed over the top of this installation and just doing an icewm install now followed shortly by new live isos landing. I can email you the access details to the pre-release RC isos.

kde install under way, that should allow me to test the kde stuff and icewm at the same time.

Hi Claire,
using RC1 KDE4-CD iso, then installing cheese (as well as digikam, kwrite, and some more) from mirrors (that is: from cauldron), in a virtual box, I still cannot reproduce any of the hanging you report :(
(well: on the one hand it is a good news, but on the other, I can't really help figuring what's wrong on your side).

Now: I did not get cheese (nor others) from RC1 directly. Do I need the DVD iso for this ?

Cannot reproduce with cheese, runs fine both from menu launcher or in terminal. Does this still persist with Mageia 4?

CC: (none) => doktor5000

(In reply to Florian Hubold from comment #17)
> Cannot reproduce with cheese, runs fine both from menu launcher or in
> terminal. Does this still persist with Mageia 4?

I confirm this issue in Mageia 4 for digikam, kate, kwrite.
I have update from MGA3 64-bit.

Kate and kwrite not runnig from menu launcher, but open when clicked to associated file (for example text file). Not at digikam.

I tried to find some error by using strace (command "strace digikam" in quick lunch). But with strace, digikam open and runnig well. Same for kate and kwrite. I found nothing.

CC: (none) => vit.brezina

(In reply to Vit Brezina from comment #18)
> (In reply to Florian Hubold from comment #17)
> > Cannot reproduce with cheese, runs fine both from menu launcher or in
> > terminal. Does this still persist with Mageia 4?
> 
> I confirm this issue in Mageia 4 for digikam, kate, kwrite.
This bug is about cheese, not digikam, kate nor kwrite.

> I tried to find some error by using strace (command "strace digikam" in
> quick lunch). But with strace, digikam open and runnig well. Same for kate
> and kwrite. I found nothing.

No need to find anything, strace is only used as a workaround to start the programs.

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
Resolution: (none) => FIXED