http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c1 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Severity|Critical |Minor --- Comment #1 from Egbert Eich --- Just a warning. Minor -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nixbugz@outlook.com Flags| |needinfo?(nixbugz@outlook.c | |om) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c4 --- Comment #4 from NIk Zbugz --- (In reply to Egbert Eich from comment #1)

Just a warning. Minor

It may be minor to you but I lose work when it happens. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c6 --- Comment #6 from NIk Zbugz --- Created attachment 676026 --> http://bugzilla.opensuse.org/attachment.cgi?id=676026&action=edit (EE) qxl(0): error doing QXL_ALLOC The crashes happen mostly when I have 2 desktops open via Switch User and mostly on the second desktop, as here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c7 --- Comment #7 from NIk Zbugz --- Created attachment 676027 --> http://bugzilla.opensuse.org/attachment.cgi?id=676027&action=edit Xorg.0.log.old: (EE) Couldn't init device "ImExPS/2 Generic Explorer Mouse" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c9 --- Comment #9 from Egbert Eich --- (In reply to NIk Zbugz from comment #5)

No, I could set one up but don't have the time for the hours of use necessary to provoke it into falling over.

To me this is not really a strong argument. There is no such thing like a free lunch. I do this in my spare time as well. If you think since I've got a SUSE email address, this is my work and obligation then I'd have a 12 to 14 h work day ;) Regardless, (In reply to NIk Zbugz from comment #6)

Created attachment 676026 [details] Xorg.1.log.old: (EE) qxl(0): error doing QXL_ALLOC

This looks like a memory leak issue. Several of those have been fixed in the patches I've backported now. (In reply to NIk Zbugz from comment #8)

...

I've backported a bunch of crash fixes to 13.2 now. You need to add: http://download.opensuse.org/repositories/home:/eeich:/branches:/ OBS_Maintained:/xf86-video-qxl/openSUSE_13.2_Update/ As repo and update the xf86-video-qxl.

Thank you, I'll try that.

Ok, thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c11 --- Comment #11 from NIk Zbugz --- Yes Egbert there is news but not good news. I installed xf86-video-qxl 0.1.2-2.5.1 on openSUSE 13.2 but it still falls over: opensuse:~ # journalctl -b|grep qxl_ttm.c May 14 11:01:10 opensuse kernel: WARNING: CPU: 3 PID: 3474 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 15 07:13:59 opensuse kernel: WARNING: CPU: 0 PID: 20212 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:04:18 opensuse kernel: WARNING: CPU: 3 PID: 31395 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:04:41 opensuse kernel: WARNING: CPU: 1 PID: 27309 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:04:51 opensuse kernel: WARNING: CPU: 2 PID: 27524 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:12:29 opensuse kernel: WARNING: CPU: 2 PID: 27847 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:13:39 opensuse kernel: WARNING: CPU: 1 PID: 28431 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() May 17 04:15:16 opensuse kernel: WARNING: CPU: 2 PID: 28770 at ../drivers/gpu/drm/qxl/qxl_ttm.c:414 qxl_sync_obj_wait+0x172/0x1f0 [qxl]() opensuse:~ # I will attach the Xorg logs and systemd journal. The last few entries are where it doesn't quite get to the desktop after logging in before reverting to the login screen. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c13 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #13 from Egbert Eich --- Ok, then I'm sorry - I can't help you. Investigating this will simply cost too much time which I'm not able to invest. Sorry again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978785 http://bugzilla.opensuse.org/show_bug.cgi?id=978785#c16 --- Comment #16 from NIk Zbugz --- Well that's disappointing but thanks for the work you have done on this. I'm not sure about no. 1: are you saying it's fixed in vmmouse but it will still fail elsewhere until 4 is fixed (and if it is fixed, where can I find the new code)? How do I get the other bugs fixed? Should I add 2, 3 and 4 as new bugs and if so, here or somewhere else? I've disabled Plymouth so I'll see how that goes. I expect no. 4 will be present in any distribution but I could try another desktop to try to avoid 2 & 3. Is there an alternative to vmmouse? I'm surprised to be the only one apparently suffering these crashes: does no-one else use more than one login session with spice or is it something else? -- You are receiving this mail because: You are on the CC list for the bug.