[Ubuntu-x-swat] [Bug 1360218] Re: Dim screen until brightness key pressed

2014-09-13 Thread Ariszló
ore details in command line In addition to the brightness slider, the following command also reports maximum brightness while the screen is dim: cat /sys/class/backlight/acpi_video0/brightness Typing this command fixes brightness immediately: echo 50 | sudo tee

[Ubuntu-x-swat] [Bug 1365336] Re: Lightdm update=No desktop

2014-09-13 Thread Ben Cracknell
I think I'm experiencing the same problem now after updating Ubuntu. Same hardware and driver setup as the others. The tracker says these bugs were fixed, but does that mean 'apt-get update apt-get upgrade' should solve my issue? It doesn't seem to change anything. output from show-seat:

[Ubuntu-x-swat] [Bug 1041790]

2014-09-13 Thread Frank Stephan
Hi Chris, meanwhile my current kernel is 3.16.1-46.1.g90bc0f1 I'm wondering (after a reinstall) that the semaphore bug hasn't occured yet, which was the case before (after a fresh install). This leads me to 4 definable possible reasons: 1. the named kernel revision somehow contains a fix for

[Ubuntu-x-swat] [Bug 1041790]

2014-09-13 Thread Frank Stephan
2. of course I meant cgroup_disable=memory -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround

[Ubuntu-x-swat] [Bug 1322589] Re: Screen flickers when running game Sins of a Solar Empire

2014-09-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1322589 Title:

[Ubuntu-x-swat] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-13 Thread sohel
yes thats the most strange thing, i didnt find any issue in my logs but issue is same as described by others in this thread : i hear login sound but no login box, just purple screen and no way to login from UI, command line works... -- You received this bug notification because you are a member

[Ubuntu-x-swat] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-13 Thread sohel
is there anyway to change log level to debug or something like that to generate more logs? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer

[Ubuntu-x-swat] [Bug 1369103] [NEW] brightness heys don't work after resume from hibernate

2014-09-13 Thread Denis Prost
Public bug reported: This is an hibernate specific problem. After resume from suspend to ram, brightness keys do work. So I guess this is a different problem than issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778. (I tried the different solutions described in this bug comments,

[Ubuntu-x-swat] [Bug 1369103] Re: brightness keys don't work after resume from hibernate

2014-09-13 Thread Denis Prost
** Summary changed: - brightness heys don't work after resume from hibernate + brightness keys don't work after resume from hibernate -- 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/1369103

[Ubuntu-x-swat] [Bug 1327774] Re: asus x200la brightness hotkeys not working (rest of them do)

2014-09-13 Thread Jaime Pérez
sudo sed 's/GRUB_CMDLINE_LINUX_DEFAULT=quiet splash/GRUB_CMDLINE_LINUX_DEFAULT=quiet splash acpi_osi=/' -i /etc/default/grub update-grub -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.

[Ubuntu-x-swat] [Bug 1369113] [NEW] Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2014-09-13 Thread Adam Colligan
Public bug reported: I am cross-posting this issue, which I reported to Valve's Source GIT issue tracker, because it was suggested that the regression may be due to Ubuntu Xorg changes rather than changes on the Steam end. Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822

[Ubuntu-x-swat] [Bug 1360218] Re: Dim screen until brightness key pressed

2014-09-13 Thread Ariszló
** Attachment added: Xorg.0.log before brightness key pressed https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1360218/+attachment/4203065/+files/Xorg_0_log-1-before -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1360218] Re: Dim screen until brightness key pressed

2014-09-13 Thread Ariszló
** Attachment added: Xorg.0.log after touching a brightness key https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1360218/+attachment/4203074/+files/Xorg_0_log-2-after -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1041790]

2014-09-13 Thread Frank Stephan
Hi Chris, OK, nothing of the above was the reason. In my case it's simply this: /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option TearFreetrue EndSection I added it when the tearing scrolling through large webpages annoyed

[Ubuntu-x-swat] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2014-09-13 Thread Adam Colligan
** Also affects: steam (Ubuntu) Importance: Undecided Status: New -- 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/1369113 Title: Steam game began crashing 2014-09-12 (cross-post Source

[Ubuntu-x-swat] [Bug 1041790]

2014-09-13 Thread Chris Wilson
(In reply to comment #189) Hi Chris, OK, nothing of the above was the reason. In my case it's simply this: /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option TearFreetrue EndSection I added it when the tearing

[Ubuntu-x-swat] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0

2014-09-13 Thread Bug Watch Updater
** Bug watch added: freedesktop.org Bugzilla #70764 https://bugs.freedesktop.org/show_bug.cgi?id=70764 -- 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/1041790 Title: [snb]

[Ubuntu-x-swat] [Bug 1369131] [NEW] package xserver-xorg-dev 2:1.15.1-0ubuntu9 failed to update on shell, found xserver-xorg-dev_2%3a1.16.0-1ubuntu1_amd64.deb on /var/cache/apt/archives/ exit 1 with m

2014-09-13 Thread LAHLOU Benoit
Public bug reported: En mode console, avec sudo apt-get dist-upgrade, le paquetage xserver- xorg-dev n'est pas trouvé et ressort avec une erreur de relais brisé car il y a un remplacement de certains caractère par un code de substitution qui serait généré lors du téléchargement. ProblemType:

[Ubuntu-x-swat] [Bug 1313459] Re: Screen corruption with Radeon 6670

2014-09-13 Thread Alexander Gitter
Just did a dist-upgrade (and rebooted the computer). Unfortunately, yes, this still occurs which makes Ubuntu unusable on this machine. -- 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 1363430] Re: ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp

2014-09-13 Thread Andreas Weller
** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- 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/1363430 Title: ABORT: Aborting

[Ubuntu-x-swat] [Bug 1363430] Re: ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp

2014-09-13 Thread Andreas Weller
I found a website which crashes Firefox repeatable: http://www.rtl-sdr.com/ But this bug seems to be related to xserver-xorg-video-intel Switching AccelMethod to uxa in /etc/X11/xorg.conf seems to prevent Firefox from crashing with this error message... FYI: My system uses an Intel Mobile 4 GPU

[Ubuntu-x-swat] [Bug 1363430] Re: ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp

2014-09-13 Thread Andreas Weller
Installing upstream Kernel 3.17 (RC4) also fixes this issue. -- 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/1363430 Title: ABORT: Aborting on channel error.: file

[Ubuntu-x-swat] [Bug 1338812] Re: [hsw mesa] False GPU lockup IPEHR: 0x780c0000 IPEHR: 0x0b140001

2014-09-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.

[Ubuntu-x-swat] [Bug 1338812] Re: [hsw mesa] False GPU lockup IPEHR: 0x780c0000 IPEHR: 0x0b140001

2014-09-13 Thread Nicholas Skaggs
This error start occurring for me after the upgrade to xserver-xorg- video-intel (2:2.99.914-1~exp1ubuntu2), but given the earlier occurence this might just have been random. Seems to occur randomly while using the desktop under load. -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 1275416] Re: touchscreen do not work after suspend/resume

2014-09-13 Thread Shane Sanders
The fix may be a little more complicated. I had to add an 'apmd' script. (1.) Blacklist usbtouchscreen in the file: /etc/modprobe.d/blacklist.conf ie. add an entry to the end of the file blacklist usbtouchscreen ie. sudo gedit /etc/modprobe.d/blacklist.conf (2.) Create a file in

[Ubuntu-x-swat] [Bug 1275416] Re: touchscreen do not work after suspend/resume

2014-09-13 Thread Shane Sanders
*** UPDATED// SLEEPY * The fix may be a little more complicated. I had to add an 'apmd' script. (1.) Blacklist usbtouchscreen in the file: /etc/modprobe.d/blacklist.conf ie. add an entry to the end of the file blacklist usbtouchscreen ie. sudo gedit

[Ubuntu-x-swat] [Bug 1275416] Re: touchscreen do not work after suspend/resume

2014-09-13 Thread Shane Sanders
UPDDATE #2 for the apm script just use #!/bin/sh rmmod hid_multitouch modprobe hid_multitouch The conditional isn't necessary! Appologies for the confusion -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xinput in Ubuntu.