[Ubuntu-x-swat] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13

2016-11-15 Thread Christopher M. Penalver
vak, after what package update precisely did this issue start happening again with? ** 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/158

[Ubuntu-x-swat] [Bug 1610666] Re: Mouse cursor moves choppy/doesn't update its position as it should

2016-11-15 Thread Christopher M. Penalver
** Description changed: Q. What I expected to happen? A. The mouse would run smoothly as it does run in windows. Q. What happened instead? A. The mouse lags moves choppy/doesn't update its position as it should Additional Information: Output of "xinput --list --short" ⎡ Virt

[Ubuntu-x-swat] [Bug 1599952] Re: Blurred images with kernels after 4.2.x

2016-11-15 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1599952

[Ubuntu-x-swat] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-11-15 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1623969

[Ubuntu-x-swat] [Bug 1577074] Re: AMDGPU driver problems on "Carrizo" APU

2016-11-15 Thread victor gaspar
Same (or similar) issue here with Ubuntu 16.04.1 LTS on my laptop HP Pavilion with graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0). Already filled a report using ubuntu-bug. Bug #1642078. -- You received this bug notification because you are a member of Ubuntu-X, which is subscr

[Ubuntu-x-swat] [Bug 1642078] [NEW] Black screen at startup

2016-11-15 Thread victor gaspar
Public bug reported: Problem description: The laptop starts up fine but the screen is black; even though the screen is black I can hear the drum sound prompting me to log in. After rebooting laptop all is well with the screen and I have a fully functional system. Sometimes, though, I have to re

[Ubuntu-x-swat] [Bug 1639663] Re: vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2

2016-11-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. http

[Ubuntu-x-swat] [Bug 1642045] [NEW] Please check about these issues

2016-11-15 Thread giorgio
Public bug reported: Please check about these issues ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic i686 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..03.00.0:

[Ubuntu-x-swat] [Bug 1607240] Re: Unity8 default mouse wheel increment seen by Mir clients is 7.0 (it should be 1.0)

2016-11-15 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-system-settings - 0.4+17.04.20161109.1-0ubuntu1 --- ubuntu-system-settings (0.4+17.04.20161109.1-0ubuntu1) zesty; urgency=medium [ Daniel van Vugt ] * Allow scroll speed multipliers up to 3.0; since the default speed in (LP: #1607240, #

[Ubuntu-x-swat] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-11-15 Thread Bengt Nilsson
I tried xfce4-settings 4.12.1-11 as mentioned in #133 and indeed it "works", X does not crash. However, the set screen resolution is lost. When I turn on the screen again, the desktop defaults to the highest possible screen resolution. In my case, it means that my desktop menu bar and docky are

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Oleksandr Pikozh
** Description changed: I'm unable to start plasma after nvidia nvidia-304 package upgrade (and reboot). The related KDE bug report is (at least, KDE crash handler (DrKonqi) considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229. However, I discovered that the c

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Alberto Salvia Novella
** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided => Critical ** Changed in: plasma-workspace (Ubuntu) Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ub

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread lothar4ever
Steps i did to solve this: 1. sudo apt-get install nvidia-304=304.131-0ubuntu3 (it will downgrade to 131) 2. sudo apt-mark hold nvidia-304 (it will prevent future automatic updates) I don't know if in the future it will be a problem not having it updated, but for now i can work like this. -- Yo

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plasma-workspace (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.la

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. http

[Ubuntu-x-swat] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-11-15 Thread Veress Krisztián
1. Fekete nvidia-304. sudo apt remove --purge nvidia-304 2. Download nvidia-304.131.0ubuntu3.deb 3. Install nvidia driver sudo dpkg -i nvidia-304.131.0ubuntu3 deb 4. Reboot -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-

[Ubuntu-x-swat] [Bug 1581560] Re: system crash when attaching external display

2016-11-15 Thread kay
Why did you close the issue? I still have to power off my laptop instead of suspending. -- 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/1581560 Title: system crash when attaching external display

[Ubuntu-x-swat] [Bug 1585884] Re: xrandr unable to activate displays after docking

2016-11-15 Thread visnae
I'm not on `autorandr` only plain `xrandr`. If I boot while in dock, everything works fine. I can even remove my laptop from dock and suspend/resume it outside of dock, dock it again, and everything still works as long as I didn't attach an external monitor during that time. However, if I attach