Bug 260363

Just tried to reproduce it and yes it consistently caused a reboot, go to Ledgers, select new transaction, then select the drop down for Pay to, the whole system reboots.  It happened for Deposit and Transfer transactions.

I also tried typing into the Pay to box, that worked fine.  I then tried the drop down again and that worked fine as well, so the problem seems to have been fixed.  This seems really weird!

If there is any debug I can run to try to get more info on this please let me know.

Thanks
Mick

By system reboot you actually mean that your computer is rebooted? If that's so there is no debug info you can obtain from the crash since the computer is being rebooted. Hard to believe that KMyMoney alone cause a computer reboot (isn't that the kernel's territory?).

Could it be that only the X server rebooted? You can check with uptime from a shell.

If so, it could also be a problem with the graphics driver

Yes I guess it could, is there any way that I can tell?  Are there any
system log files that would help?  Let me know and I will send them.

Thanks

Mick

On Fri, 2010-12-17 at 13:47 +0100, Wolfgang Rohdewald wrote:
> https://bugs.kde.org/show_bug.cgi?id=260363
> 
> 
> Wolfgang Rohdewald <wolfgang@rohdewald.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |wolfgang@rohdewald.de
> 
> 
> 
> 
> --- Comment #3 from Wolfgang Rohdewald <wolfgang rohdewald de>  2010-12-17 13:47:28 ---
> Could it be that only the X server rebooted? You can check with uptime from a
> shell.
> 
> If so, it could also be a problem with the graphics driver
>

- start a konsole window. This program might be called Konsole or Terminal.
- enter the letters "uptime"
- press RETURN

you will get something like
 15:50:39 up 8 days, 23:25,  7 users,  load average: 1.68, 1.52, 1.43

and you can check logs in /var/log like syslog, messages, kern.log depending on your distribution. Maybe you have error messages from the X server in
/var/log/Xorg.0.log (marked with (EE))

Here's another approach.  If only X restarts, the screen should go black and then you should almost immediately see your window manager (Gnome or KDE or whatever you use) starting.  If the whole system reboots, you would see the BIOS screen for at least a moment, and then the boot manager (grub or lilo).  Even if the boot manager is set to boot directly without having to choose the kernel, it should wait at least a second or more so you have a choice.

Another way to tell would be to go to another virtual terminal (usually Alt-Ctl-F2 for example) and log in.  Then switch back to X (usually Alt-Ctl-F7) start KMM and cause the crash.  When the system is ready, go back to the other terminal.  If the system rebooted, you will have to log in again there.  If only X restarted, that session will be unchanged.

Yes I think you are right, it was X term restarting not a full reboot


On Fri, 2010-12-17 at 16:26 +0100, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=260363
> 
> 
> 
> 
> 
> --- Comment #6 from Jack <ostroffjh users sourceforge net>  2010-12-17 16:26:42 ---
> Here's another approach.  If only X restarts, the screen should go black and
> then you should almost immediately see your window manager (Gnome or KDE or
> whatever you use) starting.  If the whole system reboots, you would see the
> BIOS screen for at least a moment, and then the boot manager (grub or lilo). 
> Even if the boot manager is set to boot directly without having to choose the
> kernel, it should wait at least a second or more so you have a choice.
> 
> Another way to tell would be to go to another virtual terminal (usually
> Alt-Ctl-F2 for example) and log in.  Then switch back to X (usually Alt-Ctl-F7)
> start KMM and cause the crash.  When the system is ready, go back to the other
> terminal.  If the system rebooted, you will have to log in again there.  If
> only X restarted, that session will be unchanged.
>

I have a couple of log files from around hte time of the problem.  I'm
not really sure what I am look at, so I have attached them both.

I have been using KMyMoney since the incident and it has not happened
again.

If there is anything else I can do to help please let me know

Thanks
Mick

On Fri, 2010-12-17 at 15:54 +0100, Wolfgang Rohdewald wrote:
> https://bugs.kde.org/show_bug.cgi?id=260363
> 
> 
> 
> 
> 
> --- Comment #5 from Wolfgang Rohdewald <wolfgang rohdewald de>  2010-12-17 15:54:18 ---
> - start a konsole window. This program might be called Konsole or Terminal.
> - enter the letters "uptime"
> - press RETURN
> 
> you will get something like
>  15:50:39 up 8 days, 23:25,  7 users,  load average: 1.68, 1.52, 1.43
> 
> and you can check logs in /var/log like syslog, messages, kern.log depending on
> your distribution. Maybe you have error messages from the X server in
> /var/log/Xorg.0.log (marked with (EE))
>

This is not a problem in KMyMoney, rather probably a graphic driver issue. You'll probably find the same happen with other applications.