[Ubuntu-x-swat] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

2018-05-10 Thread Ákos Maróy
should be this one: https://errors.ubuntu.com/oops/68c71690-5413-11e8-80d4-fa163ef911dc -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1769819 Title: Xorg crashes after system sleep /

[Ubuntu-x-swat] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

2018-05-09 Thread Ákos Maróy
done. the new bug is bug #1770322 this was created by running ubuntu-bug xserver-xorg-core I wasn't able to determine the big ID when running ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.0.crash . also the system seemed to automatically run ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.0.crash after

[Ubuntu-x-swat] [Bug 1770322] [NEW] Xorg crashes after system sleep / wakeup

2018-05-09 Thread Ákos Maróy
Public bug reported: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a

[Ubuntu-x-swat] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

2018-05-08 Thread Ákos Maróy
can you be more specific about the workaround. I read but 994921, but didn't find a clear reference as to what would need to be done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1769819

[Ubuntu-x-swat] [Bug 1769819] [NEW] Xorg crashes after system sleep / wakeup

2018-05-08 Thread Ákos Maróy
Public bug reported: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a

[Ubuntu-x-swat] [Bug 1085035] [NEW] fgrlx module does not build kernel driver

2012-11-30 Thread Ákos Maróy
Public bug reported: when installing the fglrx module, it doesn't build the kernel driver, because it doesn't install the kernel sources as a dependency. from the command line output to apt-get install fglrx: Loading new fglrx-9.000 DKMS files... Building only for 3.5.0-19-generic Building for

[Ubuntu-x-swat] [Bug 1085035] Re: fgrlx module does not build kernel driver

2012-11-30 Thread Ákos Maróy
after manually installing linux-sources-generic, the fglrx module also compiles / installs fine -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1085035 Title: fgrlx module does not

[Ubuntu-x-swat] [Bug 658636] Re: title in title bars sometimes refreshes only if the window is moved/resized

2011-06-03 Thread Ákos Maróy
is this really 'fix released'? I'm having the same issue, with the ATI binary driver... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/658636 Title: title in title bars

[Ubuntu-x-swat] [Bug 577858] [NEW] X server with intel 82852/855GM fails

2010-05-09 Thread Ákos Maróy
Public bug reported: Binary package hint: xserver-xorg the X server fails to star on a machine with an intel 82852/855GM video card. this is an older Fujitsu Siemens Agilo laptop, running 10.04 the X server used to work with 9.04 in 'failsafe mode' (using the vesa driver), it starts just fine.

[Ubuntu-x-swat] [Bug 521436] Re: ioctl EVIOCGNAME failed: Inappropriate ioctl for device on 10.04

2010-02-23 Thread Ákos Maróy
well, I was surprised as well, but this is what happens, as I described: gdm fails to start, while startx will start X fine, with the same errors in the X log file. when gdm fails to start, it displays a window complaining about these errors. I looked at the wiki page you sent, but did not find

[Ubuntu-x-swat] [Bug 521436] Re: ioctl EVIOCGNAME failed: Inappropriate ioctl for device on 10.04

2010-02-19 Thread Ákos Maróy
I wonder why you changed this to virtualbox-ose - virtualbox is not even installed on the system, and this happens an a raw hardware boot, not in a virtualbox VM... ** Package changed: virtualbox-ose (Ubuntu) = xorg (Ubuntu) -- ioctl EVIOCGNAME failed: Inappropriate ioctl for device on 10.04

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
I tried to run apport-collect, and it opens the browser window after asking for permissions, but then it hands at a page with saying 'Almost finished...' - and it never finishes :( -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification

[Ubuntu-x-swat] [Bug 521436] Re: ioctl EVIOCGNAME failed: Inappropriate ioctl for device on 10.04

2010-02-14 Thread Ákos Maróy
intersetingly, I get more and more similar messages, as I use different pointers, like an external USB mouse. after having plugged in the mouse, I get a similar ioctl error message related to the mouse as well - even if its not actually plugged in. interestingly, this issue is only coming up when

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
what information would you need - maybe I can collect it manually instead of apport-collect? -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/39194138/Xorg.0.log -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu.

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
** Attachment added: dmesg http://launchpadlibrarian.net/39194142/dmesg -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu.

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
** Attachment added: lspci-vvvnn http://launchpadlibrarian.net/39194226/lspci-vvvnn -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu.

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
added log files - how would I screen capture the corruption? -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu.

[Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2

2010-02-14 Thread Ákos Maróy
well, I don't see how I could respond to a pop-up on a totally corrupt screen, especially when the screen is locked, or its about a an error message of X failing to start - and the error message itself is on a corrupted screen :( -- screen corruption on 10.04 alpha2

[Ubuntu-x-swat] [Bug 440544] Re: screen corruption with Radeon 4770

2010-02-12 Thread Ákos Maróy
I also have a similar issue, with a Mobility Radeon HD 5830 card - but the above xorg.conf sample makes the whole X unable to start :( -- screen corruption with Radeon 4770 https://bugs.launchpad.net/bugs/440544 You received this bug notification because you are a member of Ubuntu-X, which is