On 05/03/11 14:57, jean Monnat wrote:
Le Tue, 01 Mar 2011 19:30:02 +0100,
AG a écrit :
Two questions, then:
(1) how do I capture all of the debugging output from amarok --debug?
(2) any initial thoughts on why Amarok might start to crash today?
Le Tue, 01 Mar 2011 19:30:02 +0100,
AG a écrit :
> Two questions, then:
>
> (1) how do I capture all of the debugging output from amarok --debug?
>
> (2) any initial thoughts on why Amarok might start to crash today? I
> updated today and rebooted yesterday, and Amarok was working f
Dne, 03. 03. 2011 21:06:07 je AG napisal(a):
On 01/03/11 23:26, Klistvud wrote:
The first thing to check is, does it crash in another user account?
I accept that setting up another user account would be a valid test,
so my question is due to my own lack of understanding: - I would have
tho
On 03/03/11 21:33, Christopher Judd wrote:
On Thursday 03 March 2011 15:08:55 AG wrote:
...
I've double checked removing amarok completely from my system and
reinstalling it and its associated packages (common, dbg, etc.) and it
still crashes. I've submitted the crash handler report and a
On Thursday 03 March 2011 15:08:55 AG wrote:
> ...
>
> I've double checked removing amarok completely from my system and
> reinstalling it and its associated packages (common, dbg, etc.) and it
> still crashes. I've submitted the crash handler report and asked for
> assistance on the amarok list
On 01/03/11 20:47, Jeffrin Jose wrote:
On Tue, Mar 01, 2011 at 06:07:35PM +, AG wrote:
(1) how do I capture all of the debugging output from amarok --debug?
I think You may start gnome terminal and run "amarok --debug 2> debug.txt".
(2) any initial thoughts on why Amarok
On 01/03/11 23:26, Klistvud wrote:
Dne, 01. 03. 2011 19:07:35 je AG napisal(a):
(2) any initial thoughts on why Amarok might start to crash today? I
updated today and rebooted yesterday, and Amarok was working fine for
me yesterday after I booted up. So, it may have been something in
today'
On 01/03/11 21:57, Hugo Vanwoerkom wrote:
Simon Brandmair wrote:
On Tue, 01 Mar 2011 19:30:02 +0100 AG wrote:
However, attempting to capture this output via amarok --debug >
amarok.txt (or | amarok.txt) doesn't capture anything at all in a text
format that I can copy and paste as part of this
Dne, 01. 03. 2011 19:07:35 je AG napisal(a):
(2) any initial thoughts on why Amarok might start to crash today? I
updated today and rebooted yesterday, and Amarok was working fine for
me yesterday after I booted up. So, it may have been something in
today's updates (I only had 7 packages
Simon Brandmair wrote:
On Tue, 01 Mar 2011 19:30:02 +0100 AG wrote:
However, attempting to capture this output via amarok --debug >
amarok.txt (or | amarok.txt) doesn't capture anything at all in a text
format that I can copy and paste as part of this request for help.
Two questions, then:
(
On Tue, Mar 01, 2011 at 06:07:35PM +, AG wrote:
> (1) how do I capture all of the debugging output from amarok --debug?
I think You may start gnome terminal and run "amarok --debug 2> debug.txt".
> (2) any initial thoughts on why Amarok might start to crash today?
> I updated today and rebo
On Tue, 01 Mar 2011 19:30:02 +0100 AG wrote:
> However, attempting to capture this output via amarok --debug >
> amarok.txt (or | amarok.txt) doesn't capture anything at all in a text
> format that I can copy and paste as part of this request for help.
>
> Two questions, then:
>
> (1) how do I
Hi
Amarok is crashing almost immediately that I launch it on an up-to-date
testing/ wheezy machine using Gnome as the DE. Yesterday, Amarok worked
fine, today it doesn't. I've run amarok --debug at the command line and
get literally streams of output, with multi-colored code tags (I
think).
13 matches
Mail list logo
