[Ubuntu-x-swat] [Bug 1318570] Re: Disabled touchpad on again after wake

2016-09-05 Thread Ales
This is an old bugreport. It's already resolved. The problem disappeared with upgrade to 14.10. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1318570 Title: Disabled

[Ubuntu-x-swat] [Bug 1539046] [NEW] libGL error: failed to open drm device: Permission denied

2016-01-28 Thread Ales
Public bug reported: After some update (unfortunately I'm not sure what) if I try to play a videofile (e.g. mpv movie.mkv) I get this error: libGL error: failed to open drm device: Permission denied I think from this message is not very clear why is that. I figured out I was not in "video"

[Ubuntu-x-swat] [Bug 1525721] Re: Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed

2016-01-11 Thread Ales
Thank you for your replay. After BIOS update: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date says: M74 Ver. 01.16 11/26/2015 Unfortunately no improvement, it doesn't work anyway. The only change is, that mpv doesn't give "SIGABRT" but "Aborted". Whole message:

[Ubuntu-x-swat] [Bug 1525721] Re: Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed

2016-01-11 Thread Ales
Done. Thank you for your help. -- 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/1525721 Title: Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed To manage

[Ubuntu-x-swat] [Bug 1531439] [NEW] Freeze after kernel upgrade to 4.0.23

2016-01-06 Thread Ales
Public bug reported: After the recent kernel upgrade 2.4.0-23 the computer freezes (see the screenshot) and I'm not able to login neither into a graphic mode nor the text console. When I try previous kernel 4.2.0-22 the result is the same even if it worked before. When I go to the recovery mode

[Ubuntu-x-swat] [Bug 1525721] [NEW] Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed

2015-12-13 Thread Ales
Public bug reported: mpv --hwdec=auto movie.mkv gives this: libva info: VA-API version 0.38.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_38 libva info:

[Ubuntu-x-swat] [Bug 1479596] Re: Cannot Run AMD Catalyst Control Center

2015-10-31 Thread Ales
I have a similar issue after clean install of Kubuntu 15.10. No matter if I use fglrx or fglrx-updates when trying to launching amdcccle I get this: "There was a problem initilizing Catalyst Control Center Linux edition". I used the Driver manager to install these drivers. I have a HP ProBook 450

[Ubuntu-x-swat] [Bug 1318570] [NEW] Disabled touchpad on again after wake

2014-05-12 Thread Ales
Public bug reported: I have set Disable touchpad when mouse is plugged in in System Settings / Touchpad. Works fine until I suspend the laptop to RAM. When waked up, touchpad is ON again. If I plug out and plug in the USB dongle it is disabled as expected. So I guess during waking up KDE doesn't

[Ubuntu-x-swat] [Bug 1098561] Re: Unsupported hardware watermark appears when FGLRX is installed on 13.04

2013-05-10 Thread Ales
ATI Mobility Radeon HD 5400 Series, Kubuntu 13.04, 3.8.0-19-generic. Updating drivers (apt-get install fglrx-updates) worked for me. The watermark is gone. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu.

[Ubuntu-x-swat] [Bug 1063091] Re: Bamboo Connect (CTL-470k) not responding

2012-10-12 Thread Ales Katona
After some additional testing it seems that the tablet works in a random manner (some reboots it does, most it doesn't but it doesn't seem to be related to it being plugged in USB on boot). When it works I get this xinput list result: ⎡ Virtual core pointer id=2

[Ubuntu-x-swat] [Bug 1063091] [NEW] Bamboo Connect (CTL-470k) not responding

2012-10-06 Thread Ales Katona
Public bug reported: My Bamboo Connect CTL-470 tabled (cable version) doesn't work in the latest 12.10 beta2. The kernel recognized it and creates two new input devices. I can see it also in the Xorg input list but not in the ubuntu settings/wacom. I can also see the device in Inkscape,

[Ubuntu-x-swat] [Bug 1063091] Re: Bamboo Connect (CTL-470k) not responding

2012-10-06 Thread Ales Katona
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1063091 Title: Bamboo Connect (CTL-470k) not responding To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 877014] Re: Screen stays dim following unlock

2011-11-26 Thread Ales Novy
I have the same problem. Some workaround? -- 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/877014 Title: Screen stays dim following unlock To manage notifications about this