Hello Sir
Executing:===$ osmo/home/myuser/.osmo/config.xml:1: parser error : Document is
empty
^/home/myuser/.osmo/config.xml:1: parser error : Start tag expected, '<' not
found
^
** (osmo:4142): CRITICAL **: gui_calendar_set_frame_cursor_thickness: assertion
`thickness > 0 && thickness < 6' failed===
The processor goes to 100% and osmo doesnt starts.
I re-installed it and still the problem persists.
The problem might have come due to light failure or some recent 4/5-days back
update. Not confirmed.
DE-BUG:===$ gdb osmo
Reading symbols from /usr/bin/osmo...Reading symbols from
/usr/lib/debug/usr/bin/osmo...done.done.(gdb) set pagination 0(gdb) runStarting
program: /usr/bin/osmo [Thread debugging using libthread_db enabled]Using host
libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1"./home/myuser/.osmo/config.xml:1:
parser error : Document is empty
^/home/myuser/.osmo/config.xml:1: parser error : Start tag expected, '<' not
found
^[New Thread 0xae573b70 (LWP 5049)][New Thread 0xadc4ab70 (LWP 5050)][New
Thread 0xad430b70 (LWP 5051)][New Thread 0xacc2fb70 (LWP 5052)]
** (osmo:5046): CRITICAL **: gui_calendar_set_frame_cursor_thickness: assertion
`thickness > 0 && thickness < 6' failed^CProgram received signal SIGINT,
Interrupt.gui_create_tasks (appGUI=0x8132648) at tasks.c:18241824 tasks.c:
No such file or directory.(gdb) bt#0 gui_create_tasks (appGUI=0x8132648) at
tasks.c:1824#1 0x080a7fc0 in gui_create_window (appGUI=0x8132648) at
gui.c:1573#2 0x080564a0 in main (argc=1, argv=0xbffff784) at main.c:275===
Thank you and oblige.
Kind Regards,
Khurram
> Date: Thu, 18 Apr 2013 18:44:35 +0200
> From: a...@gambaru.de
> To: makh...@hotmail.com; 705...@bugs.debian.org
> CC: cont...@bugs.debian.org
> Subject: Re: Bug#705689: osmo: Osmo crashed and doesnt starts now.
>
> tags 705689 unreproducible moreinfo
> severity 705689 normal
> thanks
>
> Dear Debian user,
>
> unfortunately your problem is not reproducible and more information is
> needed to solve it. Please answer the following questions
>
> * What led up to the situation?
> * What exactly did you do (or not do)
> * What was the outcome of this action?
> * What happens if you launch osmo from the command line?
>
> You can also try to install the latest version of osmo from
> experimental. If this does not solve your issue please install the
> osmo-dbg package, try to reproduce the error and get a backtrace with
> gdb.
>
> The following tutorial explains the steps in more detail.
>
> http://wiki.debian.org/HowToGetABacktrace
>
>
