[Ubuntu-x-swat] [Bug 619403] Re: [KDE] no option for mouse wheel acceleration

2017-02-08 Thread Albert Zeyer
Well, there is some ongoing discussion here: https://bugs.freedesktop.org/show_bug.cgi?id=29905 -- 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/619403 Title: [KDE] no option for mouse whee

[Ubuntu-x-swat] [Bug 807968] Re: GLX module fails

2011-08-23 Thread Albert Zeyer
I tried reinstalling the nvidia driver but that didn't helped. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nv in Ubuntu. https://bugs.launchpad.net/bugs/807968 Title: GLX module fails To manage notifications about this

[Ubuntu-x-swat] [Bug 807968] Re: GLX module fails

2011-08-20 Thread Albert Zeyer
I tried to delete the xorg.conf and I was expecting that it autogenerates a correct one (or that it automatically uses the correct settings). I don't want to manually setup any xorg.conf. What am I supposed to do? -- You received this bug notification because you are a member of Ubuntu-X, which i

[Ubuntu-x-swat] [Bug 807972] Re: display stays black after standby

2011-08-20 Thread Albert Zeyer
How exactly? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/807972 Title: display stays black after standby To manage notifications about this bug go to: https://bugs.launchp

[Ubuntu-x-swat] [Bug 807972] Re: display stays black after standby

2011-07-09 Thread Albert Zeyer
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/807972 Title: display stays black after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/8

[Ubuntu-x-swat] [Bug 807972] [NEW] display stays black after standby

2011-07-09 Thread Albert Zeyer
Public bug reported: When recovering from Standby, the screen stays black. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16 Uname: Linux 2.6.32-32-generic x86_64 NonfreeKernelModules: nvidia Architecture

[Ubuntu-x-swat] [Bug 807968] Re: GLX module fails

2011-07-09 Thread Albert Zeyer
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/807968 Title: GLX module fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/807968/+subscripti

[Ubuntu-x-swat] [Bug 807968] [NEW] GLX module fails

2011-07-09 Thread Albert Zeyer
Public bug reported: root@hcompneu:~# DISPLAY=:0 glxinfo name of display: :0.0 Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "

[Ubuntu-x-swat] [Bug 441653] Re: radeon graphics mode and console does not start - xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

2010-12-24 Thread Albert Zeyer
@David: Read my comment #49. And also the linked Freedesktop bug. http://bugs.freedesktop.org/show_bug.cgi?id=29975 I read the relevant Xorg-server code and the same bug is still there and not fixed. There may be various possible reasons why VT_ACTIVATE succeeds but VT_WAITACTIVE will wait foreve

[Ubuntu-x-swat] [Bug 619403] Re: [KDE] no option for mouse wheel acceleration

2010-11-04 Thread Albert Zeyer
Note that this is not only KDE. The first place where this needs to be implemented is the Xorg server. I have done that already with my patch. Without that or another similar implementation in Xorg, this cannot (should not) be implemented. Also note that there was a discussion with Xorg developers

[Ubuntu-x-swat] [Bug 441653] Re: radeon graphics mode and console does not start - xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

2010-09-02 Thread Albert Zeyer
If I am right with my explanation, the title of this report should be changed. -- radeon graphics mode and console does not start - xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call https://bugs.launchpad.net/bugs/441653 You received this bug notification because you are a member of

[Ubuntu-x-swat] [Bug 441653] Re: radeon graphics mode and console does not start - xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

2010-09-02 Thread Albert Zeyer
I have had a similar behavior here. I am using the nvidia driver. I don't really like any of the suggested workarounds here. They are all hacks that don't really fix the bug itself. This is the relevant code: if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, xf86Info.vtno) < 0)

[Ubuntu-x-swat] [Bug 596943] Re: xorg uses too high resolution by default

2010-06-21 Thread Albert Zeyer
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/50691786/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/50691787/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/50691789/Dependencies.txt ** A

[Ubuntu-x-swat] [Bug 596943] [NEW] xorg uses too high resolution by default

2010-06-21 Thread Albert Zeyer
Public bug reported: Binary package hint: xorg After I installed the nvidia drivers, Xorg used 1600x1200 at the next reboot -- which was too high for my monitor. I'm not sure what package to blame here. Should it automatically detect what resolutions my monitor support? Also, why does it use th