The debug flag is "--debug", that's 2 '-' characters. Attempting to
narrow this down to a specific plugin would be very helpful for us.
On Mon, Aug 31, 2009 at 10:30 AM, DorianDaumiller<email address hidden> wrote:
> How do i get to the debug log? I get this behaviour only at login, not
> when starting Do manually.
>
> I tried changing the Startup-programs entry for Do to:
> gnome-do -debug 2>&1 >> /home/dorian/Desktop/GNOME-DO.debug
>
> but that file stays empty when Do crashes on startup and fills with
> pleasant indifferencies when not.
>
> Since upgrade to Karmic on friday, the log is empty, as i don't get a
> single normal startup.
>
> I will now deselect all plugins and see if that helps.
>
> --
> Crashing too much
> https://bugs.launchpad.net/bugs/394337
> You received this bug notification because you are a member of GNOME Do
> Core Team, which is subscribed to GNOME Do.
>
The debug flag is "--debug", that's 2 '-' characters. Attempting to
narrow this down to a specific plugin would be very helpful for us.
On Mon, Aug 31, 2009 at 10:30 AM, DorianDaumiller <email address hidden> wrote: Desktop/ GNOME-DO. debug /bugs.launchpad .net/bugs/ 394337
> How do i get to the debug log? I get this behaviour only at login, not
> when starting Do manually.
>
> I tried changing the Startup-programs entry for Do to:
> gnome-do -debug 2>&1 >> /home/dorian/
>
> but that file stays empty when Do crashes on startup and fills with
> pleasant indifferencies when not.
>
> Since upgrade to Karmic on friday, the log is empty, as i don't get a
> single normal startup.
>
> I will now deselect all plugins and see if that helps.
>
> --
> Crashing too much
> https:/
> You received this bug notification because you are a member of GNOME Do
> Core Team, which is subscribed to GNOME Do.
>