[Ubuntu-x-swat] [Bug 919478] Re: Running warzone from source by following the guide results in corruption fo graphics settings
Thank you for taking the time to report this bug and helping to make Ubuntu better. As you already mentioned, the logs are not that useful... Anyway, this seems to be more an issue of warzone messing up the xorg configuration and not an issue of xorg itself? Is there any specific reason that you compile warzone from source instead of just using the warzone2010 package in the repositories? Can you reproduce the issue with the warzone package from the repositories? ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- 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/919478 Title: Running warzone from source by following the guide results in corruption fo graphics settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/919478/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 627281] Re: package nvidia-current (not installed) failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error caused by a corrupted archive. Please execute the following commands, as it will clear your package cache, in a terminal ( Applications - Accessories - Terminal ) : sudo apt-get clean sudo apt-get update Then try performing the update again. This will likely resolve your issue. If so please set the bug's status to Invalid. Thanks in advance! ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New = Incomplete -- 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/627281 Title: package nvidia-current (not installed) failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 627095] Re: package fglrx-amdcccle (not installed) failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error caused by a corrupted archive. I'm closing this issue since it seems that the problem with the package installation disappeared -- feel free to file new bugs for any other issue you are still having. ** Changed in: fglrx-installer (Ubuntu) Status: New = Invalid -- 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/627095 Title: package fglrx-amdcccle (not installed) failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561734] Re: quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context
** Tags added: maverick ** Tags removed: lucid -- quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context https://bugs.launchpad.net/bugs/561734 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561734] Re: quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context
** Tags added: regression-potential -- quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context https://bugs.launchpad.net/bugs/561734 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561734] Re: quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context
** Tags removed: regression-potential -- quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context https://bugs.launchpad.net/bugs/561734 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 561734] Re: quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context
This bug reappears in Maverick, maybe the newer xserver package is missing the patch? This is using virtualbox: $ quadrapassel --clutter-debug=all ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:143: XOpenDisplay on ':0.0' ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:170: Getting the X screen Clutter-Message: [BACKEND] ./clutter-backend.c:173: Units per em: 11.96 ClutterX11-Message: [BACKEND] ./clutter-device-manager-x11.c:70: XInput support not enabled ClutterX11-Message: [BACKEND] ./clutter-device-manager-x11.c:167: Added core pointer device ClutterX11-Message: [BACKEND] ./clutter-device-manager-x11.c:176: Added core keyboard device ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:225: X Display ':0.0'[0x9604a0] opened (screen:0, root:258, dpi:95.849057) Clutter-Message: [MISC] ./clutter-feature.c:91: checking features Clutter-Message: [MISC] ./clutter-feature.c:95: allocating features data ClutterGLX-Message: [BACKEND] clutter-backend-glx.c:407: Retrieving GL fbconfig, dpy: 0x9604a0, xscreen; 0x8e2f10 (0) ClutterGLX-Message: [BACKEND] clutter-backend-glx.c:509: Creating GLX Context (display: 0x9604a0) ClutterGLX-Message: [GL] clutter-backend-glx.c:528: Setting direct context failed to create drawable ClutterGLX-Message: [BACKEND] clutter-backend-glx.c:587: Selecting dummy 0x3c4 for the GLX context Failed to initialise clutter: Unable to select the newly created GLX context $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.8.1.902-0ubuntu2 Candidate: 2:1.8.1.902-0ubuntu2 Version table: *** 2:1.8.1.902-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ maverick/main Packages 100 /var/lib/dpkg/status ** Tags added: regression-potential -- quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context https://bugs.launchpad.net/bugs/561734 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 229966] Re: ~ key does not appear directly after pressing AltGr-4 on Spanish Keyboard
Thanks for confirming. Yes fix released would be fine, as it was likely fixed by an update. Invalid might also be appropriate (because no one really confirmed the bug when you reported it). I set the status to Fix released. ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete = Fix Released -- ~ key does not appear directly after pressing AltGr-4 on Spanish Keyboard https://bugs.launchpad.net/bugs/229966 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 229966] Re: ~ key does not appear directly after pressing AltGr-4 on Spanish Keyboard
Hi. It's been a while since you reported this issue -- is this still a problem with Ubuntu Lucid (10.04)? Thanks. ** Changed in: xkeyboard-config (Ubuntu) Status: New = Incomplete -- ~ key does not appear directly after pressing AltGr-4 on Spanish Keyboard https://bugs.launchpad.net/bugs/229966 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 208899] Re: Xorg crashes drawing complex geometries
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Invalid -- Xorg crashes drawing complex geometries https://bugs.launchpad.net/bugs/208899 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 397617] Re: brightness no more working on karmic (KMS)
With BIOS and MICOM version 04CA, the brightness was not working on my Samsung NC 10 as well, a BIOS update indeed fixed the problem. That said, even without the BIOS update, the backlight (and modesetting) worked using nc10-backlight from this PPA: https://launchpad.net/~voria/+archive/ppa So, it is principally fixable for old BIOSes as well. -- brightness no more working on karmic (KMS) https://bugs.launchpad.net/bugs/397617 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 397617] Re: brightness no more working on karmic (KMS)
** Tags added: xorg-needs-kernel-fix -- brightness no more working on karmic (KMS) https://bugs.launchpad.net/bugs/397617 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 397617] Re: brightness no more working on karmic (KMS)
** Tags added: regression-potential -- brightness no more working on karmic (KMS) https://bugs.launchpad.net/bugs/397617 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
