On 18/04/2012 02:36, Johannes H. Jensen wrote:
> Interesting... From the logs it appears you are creating a new alarm (#4)
> but there is no mention of the sound-repeat gconf key being set. On my
> system, this key is set to true for all new alarms.
>
> Can you try the following:
> 1. Create a new
Interesting... From the logs it appears you are creating a new alarm (#4)
but there is no mention of the sound-repeat gconf key being set. On my
system, this key is set to true for all new alarms.
Can you try the following:
1. Create a new alarm, name it "Bug 977110"
2. Paste here the output of th
On 14/04/2012 07:10, Johannes H. Jensen wrote:
> On Sat, Apr 14, 2012 at 00:54, Chow Loong Jin wrote:
>>
>> Here you go. The former command does not work as G_LOG_DOMAIN was not
>> defined
>> during the build, but the latter does.
>
>
> Thank you. Is that log output captured while you trigger th
On Sat, Apr 14, 2012 at 00:54, Chow Loong Jin wrote:
>
> Here you go. The former command does not work as G_LOG_DOMAIN was not
> defined
> during the build, but the latter does.
Thank you. Is that log output captured while you trigger the sound_repeat
bug?
--
You received this bug notification
On 14/04/2012 06:20, Johannes H. Jensen wrote:
> @hyperair Ah that seems to be different from Glib 2.30! There is no
> mention of G_MESSAGES_DEBUG in the 2.30 docs:
> http://developer.gnome.org/glib/stable/glib-Message-Logging.html#g-log-
> default-handler
>
> Can someone on a 12.04 system please
On 13/04/2012 02:58, Johannes H. Jensen wrote:
> Can you please try the attached program on your 12.04 system?
Based on Glib 2.32's documentation, g_log_default_handler() that only debug
messages for which G_MESSAGES_DEBUG[1] contains G_LOG_DOMAIN[2] are printed out.
In other words, something lik
On Thu, Apr 12, 2012 at 19:47, Chow Loong Jin wrote:
>
> Yeah, I was pretty surprised as well. What are you using to log? Perhaps
> something in Glib changed?
I'm using g_debug() and friends to log. I'll have a look in the changelogs
for Glib and check for relevant changes...
--
You received t
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.
Y
