GNOME Bugzilla – Bug 726095
Cheese not working
Last modified: 2014-10-25 11:28:02 UTC
When i click on the cheese application, it doesn't open at all. In side bar cheese menu will appear for a while and it also disappear. Please help me out. Thanks, Dhanabal
Bugzilla is not really a good support forum (you should instead file a bug or raise an issue in your distribution's support system), but you can try a few things to see what the problem might be. First, please run "cheese" in a terminal and paste any output into this bug report.
Dhanabal: See https://bugzilla.gnome.org/page.cgi?id=bug-writing.html
What the reporter means is that cheese cannot be launched from the application overview in gnome-shell. It simply won't launch. Running cheese by using ALT+F2/cheese or running it from terminal works fine. Some references: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765513 https://bugs.archlinux.org/task/42488 There seems to be an issue with dbus activation, disabling it in the .desktop file makes it work.
If that is the case, the DBusActivatable key is in the 1.1 desktop entry specification (and a valid key): http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html The Cheese desktop file is valid according to desktop-file-validate. The bug seems to be in the desktop shell implementation, and should be filed and fixed there.
Already found out what the problem is here: it's the service file that is shipped with Cheese: Exec=${exec_prefix}/bin/cheese --gapplication-service Other applications that work fine have the exec_prefix replaced, so I guess this is a bug in the build process. Cheese on Archlinux is built from a released tarball and as this bug is also present in Debian, I don't believe it's a packaging bug.
The bug seems to be in Makefile.am. Nautilus and Sushi have this additional line in Makefile.am (which is located in data subdir instead of project root btw): org.gnome.Sushi.service: org.gnome.Sushi.service.in Makefile $(AM_V_GEN) sed -e "s|\@bindir\@|$(bindir)|" $< > $@
Ah, then my apologies, and thanks for investigating further! I just fixed this in the master and gnome-3-14 branches, so the fix will be in 3.14.2 in a couple of weeks.