[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module
This was/is working in: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Codename: yakkety $ uname -a Linux acer07 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux With later kernels no longer works. -- 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.launchpad.net/bugs/1634802 Title: Could not insert module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+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 1618423] Re: Modesetting driver cannot handle different display resolutions for two monitors
[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/1618423 Title: Modesetting driver cannot handle different display resolutions for two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1618423/+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 1609520] Re: Cannot login after logout
[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/1609520 Title: Cannot login after logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1609520/+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 1619320] Re: problems after 16 install
[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/1619320 Title: problems after 16 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619320/+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 1638431] [NEW] Screen "crash" (diagonal screen gibberish)
Public bug reported: This is a recurrent problem. For the last few Lubuntu installs, eventually, something that I invoke (one install, it was AbiWord, at least one it was Firefox, this time it is Hugin. [You may wonder - If this happens, why not install the proprietary driver nvidia-xxx? I have done so before, but this time for some reason it never gets into the kernel, and the largest screen resolution I have is 1024x768, which is much too small, especially for photo-editing... So I have to use nouveau, but as I say, I cannot now use Hugin.] Everything seems fine, I do something, and there is a pause... then the screen goes all diagonal gibberish, and the only thing I can do is hard- shutdown. I paid more attention this time, and can reproduce it on demand (not that I WANT to, but I need Hugin to stitch together some panoramas that I took on my trip, and since installing Lubuntu 16.10, when I go to load in the photos, there is a pause... then the screen crashes and I must hard-shutdown.) I have tried to simplify the debugging, and I booted from a Live-USB, the same .iso from which I installed Lubuntu 16.10 64-bit. I did nothing but install the hugin package (that, however, pulls in umpty ump other packages...) and mount my /data partition so I could point Hugin at my photos. I told Hugin which Images to Load, pressed Open, there was a pause... and it loaded them...! However, the upper half of the third image (sky?) was all gibberish, and not the image data. The globe thingy at the left seemed to have the full picture, so I went ahead and made the panorama, which was just fine - only that which was displayed on the screen was messed up. The garbage on the picture replaced itself if I went to a different tab, and then came back (although I don't guarantee it was the exact same garbage...). Today, when I reproduced the crash (so I could report the bug), I went to Syslog after hard-shutdown/boot, and copied down the info for the time it crashed...: Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS dbus[680]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS systemd[1]: Started Network Manager Script Dispatcher Service. Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS nm-dispatcher: req:1 'dhcp4-change' [wlx001f1fd8314a]: new request (1 scripts) Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS nm-dispatcher: req:1 'dhcp4-change' [wlx001f1fd8314a]: start running ordered scripts... Nov 1 21:17:01 scott-ASUS-M2N68-AM-PLUS CRON[2818]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 1 21:22:34 scott-ASUS-M2N68-AM-PLUS kernel: [14975.927029] nouveau :00:0d.0: bus: MMIO write of 01620001 FAULT at 00b000 Nov 1 21:22:34 scott-ASUS-M2N68-AM-PLUS kernel: [14976.243884] nouveau :00:0d.0: bus: MMIO write of 01680001 FAULT at 00b020 Nov 1 21:22:42 scott-ASUS-M2N68-AM-PLUS kernel: [14983.698742] nouveau :00:0d.0: bus: MMIO write of 091f0001 FAULT at 00b030 Nov 1 21:22:42 scott-ASUS-M2N68-AM-PLUS kernel: [14983.704355] nouveau :00:0d.0: bus: MMIO write of 01730001 FAULT at 00b000 Nov 1 21:22:42 scott-ASUS-M2N68-AM-PLUS kernel: [14983.741432] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b020 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="720" x-info="http://www.rsyslog.com";] start Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd: rsyslogd's groupid changed to 108 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd: rsyslogd's userid changed to 104 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ] Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd-2007: action 'action 10' suspended, next retry is Tue Nov 1 21:27:05 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Linux version 4.8.0-26-generic (buildd@lgw01-58) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #28-Ubuntu SMP Tue Oct 18 14:39:52 UTC 2016 (Ubuntu 4.8.0-26.28-generic 4.8.0) Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=5a40c58b-cb06-4221-8625-ef04379be2be ro quiet splash vt.handoff=7 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] KERNEL supported cpus: Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Intel GenuineIntel Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] AMD AuthenticAMD Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Centaur CentaurHauls Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] x86/fpu: Legacy x87 FPU detected. Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] x86/fpu: Using 'eager' FPU context switches. Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] e820: BIOS-p
[Ubuntu-x-swat] [Bug 1637815] Re: compiz error
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1637815 Title: compiz error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637815/+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 1634802] Re: Could not insert module
I changed /usr/src/nvidia-304-304.132/nv-linux.h and added just before the #endif in the end of the file the line: #undef CONFIG_MTRR then I did sudo dpkg-reconfigure nvidia-304 rebooted and at least X now is at proper resolution, but cinnamon fails to load. running cinnamon --replace on the terminal I get libEGL warning: DRI2: failed to authenticate Segmentation fault (core dumped) Not sure if related with this bug or if it could be something else :( -- 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.launchpad.net/bugs/1634802 Title: Could not insert module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+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 1617583] Re: Ubuntu 16.04 system freeze xorg libglx.so
I have updated/upgraded my fresh XUbuntu install and no more trouble with new updated libglx.so With Ubuntu, freeze (media player totem) is not resolved, as Sebastien with last updated BIOS P1.70 -- 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/1617583 Title: Ubuntu 16.04 system freeze xorg libglx.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1617583/+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 1638283] Re: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/
I can't find an edit button; the command I quoted above is incorrect. The corrected one is: rrogers@rrogers-desktop:~/tmp$ apt-cache policy libgl1-mesa-dr1* libgl1-mesa-dri-lts-utopic-dbg: Installed: (none) Candidate: 10.3.2-0ubuntu1~trusty2 Version table: 10.3.2-0ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages libgl1-mesa-dri-lts-trusty-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-vivid: Installed: (none) Candidate: 10.5.9-2ubuntu1~trusty2 Version table: 10.5.9-2ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-quantal: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-utopic: Installed: (none) Candidate: 10.3.2-0ubuntu1~trusty2 Version table: 10.3.2-0ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages libgl1-mesa-dri: Installed: 10.1.3-0ubuntu0.6 Candidate: 10.1.3-0ubuntu0.6 Version table: *** 10.1.3-0ubuntu0.6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 10.1.0-4ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-experimental-dbg: Installed: (none) Candidate: (none) Version table: libgl1-mesa-dri-experimental: Installed: (none) Candidate: (none) Version table: libgl1-mesa-dri-lts-saucy-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-raring: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-saucy: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-wily: Installed: (none) Candidate: 11.0.2-1ubuntu4~trusty1 Version table: 11.0.2-1ubuntu4~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-dbg: Installed: (none) Candidate: 10.1.3-0ubuntu0.6 Version table: 10.1.3-0ubuntu0.6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 10.1.0-4ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-raring-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-quantal-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-dev: Installed: (none) Candidate: (none) Version table: libgl1-mesa-dri-lts-xenial: Installed: (none) Candidate: 11.2.0-1ubuntu2~trusty1 Version table: 11.2.0-1ubuntu2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-wily-dbg: Installed: (none) Candidate: 11.0.2-1ubuntu4~trusty1 Version table: 11.0.2-1ubuntu4~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-trusty: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-vivid-dbg: Installed: (none) Candidate: 10.5.9-2ubuntu1~trusty2 Version table: 10.5.9-2ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages rrogers@rrogers-desktop:~/tmp$ -- 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/1638283 Title: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1 -mesa-dri/changelog
[Ubuntu-x-swat] [Bug 1638283] [NEW] libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/do
Public bug reported: This resulted from trying to install libgli from http://packages.ubuntu.com/trusty/i386/libgl1-mesa-dri/download Presumably, it's the wrong package? Following the instructions below: ubuntu-bug mesa failed reporting that it wasn't installed. Well that was because the installation was what failed. rrogers@rrogers-desktop:~/tmp$ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 rrogers@rrogers-desktop:~/tmp$ apt-cache policy libgl1-mesa-dri* N: Unable to locate package libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb N: Couldn't find any package by regex 'libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb' Ray ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Oct 31 17:16:07 2016 DpkgTerminalLog: Preparing to unpack .../libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb ... Unpacking libgl1-mesa-dri:i386 (10.1.3-0ubuntu0.6) over (10.1.0-4ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 InstallationDate: Installed on 2016-10-19 (12 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict trusty -- 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/1638283 Title: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1 -mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa- dri:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1638283/+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 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled
Good news: I have a had a small eureka moment that results my computer fully booted with graphics hardware fully accelerated. Bad news: it is still a workaround -- I still can't push power button and boot up normally. Here is the workaround sequence -- it requires another computer that can ssh in: 1. Computer in OFF state, press power. 2. At boot select screen, press `e` and edit kernel line by appending `modprobe.blacklist=radeon` 3. Press `F10` to boot 4. At login screen, click gear icon in upper right and select `Suspend` 5. After computer is in suspended state, press any key to awaken. 6. The display does not "reawaken" and still appears off. 7. From another computer, ssh into the first. 8. Issue `sudo service lightdm stop` 9. Issue `sudo modprobe radeon`. This should succeed! \o/ 10. Issue `sudo service lightdm start` Now the computer should be using correct drm drivers and have full resolution display. Furthermore, Suspend and Wake work successfully. I discovered this using ubuntu mainline kernel 4.8.0-rc5 but have verified it works with mainline 4.8.6 and also with 4.4.0-45. Unfortunately, I am also using the oibaf/graphics-drivers PPA with more recent mesa and libdrm drivers. I plan to test again after removing the PPA but it may take a while. If anyone with this problem is still watching, I'd be curious to hear if my workaround steps work for you. -- 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/1568429 Title: 1002:68b8 Radeon won't work with KMS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+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 1617583] Re: Ubuntu 16.04 system freeze xorg libglx.so
As Sebastien, I had the same trouble with an ASRock Q1900-ITX (BIOS set to P1.70 03/31/2016) over XUbuntu 16.04 . No freezes any more after renaming /usr/lib/xorg/modules/extensions/libglx.so file. (fresh install, not updated) Hope an updated GLX package. Trouble (freeze PC) only with Parole media player (0.8.1-1ubuntu amd64) Best regards -- 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/1617583 Title: Ubuntu 16.04 system freeze xorg libglx.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1617583/+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 1636397] Re: Fix modesetting slave output names
** Description changed: - From a private bug: - "Currently, NVIDIA and modesetting drivers are using same output names, that creates confusion for xrandr clients like gnome-setting-daemon or xrandr utility. + [Impact] + Currently, NVIDIA and modesetting drivers are using same output names, that creates confusion for xrandr clients like gnome-setting-daemon or xrandr utility. When modesetting outputs act as slave for other x-screen (like NVIDIA X-screen here), modesetting driver uses different scheme of output names to avoid kind of confusion we are seeing here. There is a bug in modesetting X-driver gets shipped with X-server, which disables slave - output's name scheme." + output's name scheme. From a reviewed upstream patch: "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit 9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that." so we need to backport that to zesty/yakkety/xenial. + + [Test Case] + Enable dGPU, test that output to DP works. + + [Regression Potential] + There should be none, as this leftover was a simple mistake that shouldn't be there. -- 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/1636397 Title: Fix modesetting slave output names To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1636397/+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
