[Ubuntu-x-swat] [Bug 1829327] Re: package libomp5-8 (not installed) failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-8/lib/libomp-8.so.5', which is different from other instances o

2019-05-15 Thread Apport retracing service
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-8 in Ubuntu. https://bugs.launchpad.net/bugs/1829327 Title: package libomp5-8 (not installed) failed to install/upgrade: trying to overwrite

[Ubuntu-x-swat] [Bug 1829327] [NEW] package libomp5-8 (not installed) failed to install/upgrade: trying to overwrite shared '/usr/lib/llvm-8/lib/libomp-8.so.5', which is different from other instances

2019-05-15 Thread dezi
Public bug reported: -tried to recover from mkl bug - ubuntu 19.04 amd ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libomp5-8 (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia

[Ubuntu-x-swat] [Bug 1829256] Re: [Dell Vostro 5568] Cannot find display brightness settings anywhere

2019-05-15 Thread Daniel van Vugt
Your screenshot seems to show an HP ZBook 17 G5. But this bug was reported from a Dell Vostro 5568. Please tell us which machine is affected. If it is the HP then we will need to close this bug and ask you to open a new bug from that machine instead. ** Summary changed: - Cannot find display bri

[Ubuntu-x-swat] [Bug 1829228] Re: boot time is too long and running HD videos starts flickering

2019-05-15 Thread Daniel van Vugt
Please be careful to only report one problem per bug. I will make this bug just about the long boot time. If you want to discuss the other issue then please open another bug. Your long boot time appears to be multiple problems in the kernel log (CurrentDmesg.txt). I can't quite put my finger on ju

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-15 Thread Daniel van Vugt
> modesetting doesn't have a VSync option like Intel did The modesetting driver shouldn't ever tear in the single monitor case. If it does then that's a bug like this one. Although modesetting may tear in the multi-monitor case and there is an effort underway by Intel to fix that: https://gitla

[Ubuntu-x-swat] [Bug 1828846] Re: ecra

2019-05-15 Thread Steve Beattie
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privile

[Ubuntu-x-swat] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-05-15 Thread Balint Reczey
** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial -- You received thi

[Ubuntu-x-swat] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-05-15 Thread Balint Reczey
Verified 1.15.5-1ubuntu5.16.04.0 on Xenial: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name

[Ubuntu-x-swat] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-05-15 Thread pekon
I also confirm that Paco Angulo (3rpako)'s suggestion (#42) worked for my laptop too. It's Asus with I7 core running Debian-10. Thanks Paco Angulo. -- 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.l

[Ubuntu-x-swat] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-05-15 Thread Balint Reczey
Verified 2.0.4-2ubuntu1.18.04.0 on Bionic: test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name

[Ubuntu-x-swat] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-05-15 Thread Balint Reczey
Verified 2.0.4-2ubuntu1.18.10.0 on Cosmic: test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-15 Thread Pedro Fleck
I know it is not, but I found this issue trying to fix the tearing since modesetting doesn't have a VSync option like Intel did and XFWM 4.12 VSync option didn't fix it. But I just tried the Eoan package and now XPresent works for XFWM 4.13 and my tearing problem is solved! Any chance that it will

[Ubuntu-x-swat] [Bug 1829256] [NEW] Cannot find display brightness settings anywhere

2019-05-15 Thread Daniel Martinek
Public bug reported: Ubuntu: Description:Ubuntu 19.04 Release:19.04 xorg: Instalovaná verze: 1:7.7+19ubuntu12 Kandidát: 1:7.7+19ubuntu12 Tabulka verzí: *** 1:7.7+19ubuntu12 500 500 http://cz.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/

[Ubuntu-x-swat] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-05-15 Thread Balint Reczey
Verified 2.0.4-4ubuntu1.19.04.0 on Disco: test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name

[Ubuntu-x-swat] [Bug 1829228] [NEW] boot time is too long and running HD videos starts flickering

2019-05-15 Thread pushpendra
Public bug reported: boot time is too long and running HD videos starts flickering ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvid

[Ubuntu-x-swat] [Bug 1829160] Re: Xorg and wayland crash

2019-05-15 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell

[Ubuntu-x-swat] [Bug 1829160] [NEW] Xorg and wayland crash

2019-05-15 Thread Obvi84-w
Public bug reported: On Ubuntu 19.10, on either Gnome or Ubuntu desktops whether you use wayland or xorg upon hitting the super key or by pointing the mouse on the upper left corner xorg / wayland crashes or gets stuck. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 U

[Ubuntu-x-swat] [Bug 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from WakeupHandler()

2019-05-15 Thread Daniel van Vugt
Tracking in https://errors.ubuntu.com/problem/a221de843241aab4d9728bcad808922b71c4a11c ** Description changed: + https://errors.ubuntu.com/problem/a221de843241aab4d9728bcad808922b71c4a11c + The error is reported on boot up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserv

[Ubuntu-x-swat] [Bug 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from WakeupHandler()

2019-05-15 Thread Daniel van Vugt
** Tags removed: vivid wily ** Tags added: bionic cosmic -- 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/1421808 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from Fat

[Ubuntu-x-swat] [Bug 1829127] Re: Xorg crash

2019-05-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1421808 *** https://bugs.launchpad.net/bugs/1421808 This looks like the main issue: [421325.901] (EE) modeset(0): failed to set mode: No such file or directory [421325.901] (EE) Fatal server error: [421325.901] (EE) EnterVT failed for screen 0 [421325.901]

[Ubuntu-x-swat] [Bug 1829127] Re: Xorg crash

2019-05-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1421808 *** https://bugs.launchpad.net/bugs/1421808 If you are interested in finding out exactly which of those bugs this is a duplicate of then please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.cras

[Ubuntu-x-swat] [Bug 1829127] Re: Xorg crash

2019-05-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1421808 *** https://bugs.launchpad.net/bugs/1421808 ... which makes this a duplicate of bug 1421808, or bug 1787332, or bug 1787338 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** This bug has been marked a duplicate of bug 1421808 Xorg cras

[Ubuntu-x-swat] [Bug 1787338] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from xf86VTSwitch()

2019-05-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1787