Comment 3 for bug 977110

On 13/04/2012 01:26, Johannes H. Jensen wrote:
> Unfortunately I don't have a 12.04 system readily available. Therefore a
> debug log would be very helpful. It puzzles me that there is no output
> at all when you start alarm-clock-applet from shell. There should be
> plenty of debug information.

Yeah, I was pretty surprised as well. What are you using to log? Perhaps
something in Glib changed?

> Can you please paste the output of the following five commands?
>
> file $(which alarm-clock-applet)

/usr/bin/alarm-clock-applet: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24,
BuildID[sha1]=0x268b9375cc10fa0ca672ad0fff4c5d1899fc68b5, stripped

> sha1sum $(which alarm-clock-applet)

db8f291ff34ebfaa89341f7c9ded005895ab9a77

> killall alarm-clock-applet

This doesn't work. I think there's a regression in killall that causes it to not
work with long commands.

> alarm-clock-applet --help

Usage:
  alarm-clock-applet [OPTION…]

Help Options:
  -h, --help Show help options
  --help-all Show all help options
  --help-gtk Show GTK+ Options

Application Options:
  --hidden Start hidden
  --display=DISPLAY X display to use

> alarm-clock-applet

Nothing.

I can confirm that this is definitely the alarm-clock-applet that came from the
package in 12.04. But I can't figure out why there's no output.

--
Kind regards,
Loong Jin