[Desktop-packages] [Bug 1992688] Re: firefox deb not installed
FYI, if a user has a 22.04 install where they have explicitly removed snapd/firefox this will add them back. Not sure if this was a consideration in the fix/testing. Also, the apt resolver is pulling in snapd while holding ubuntu-desktop back during staging which made finding the cause of the snapd/firefox installation a bit hard to track down since no packages upgraded in the same unattended-upgrades operation had dependencies on them. (thread: https://hachyderm.io/@rcj4747/110667685702206834) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
@3v1n0 (Marco Trevisan) has pointed out https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a possible fix ** Description changed: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: - Installed: 3.38.3-3ubuntu1 - Candidate: 3.38.3-3ubuntu1 - Version table: - *** 3.38.3-3ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.38.3-3ubuntu1 + Candidate: 3.38.3-3ubuntu1 + Version table: + *** 3.38.3-3ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages + 100 /var/lib/dpkg/status + + $ dpkg-query -W|grep mutter + gir1.2-mutter-7:amd64 3.38.3-3ubuntu1 + libmutter-7-0:amd64 3.38.3-3ubuntu1 + mutter3.38.3-3ubuntu1 + mutter-common 3.38.3-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.3-3ubuntu1 Candidate: 3.38.3-3ubuntu1 Version table: *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ dpkg-query -W|grep mutter gir1.2-mutter-7:amd64 3.38.3-3ubuntu1 libmutter-7-0:amd64 3.38.3-3ubuntu1 mutter3.38.3-3ubuntu1 mutter-common 3.38.3-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connecte
[Desktop-packages] [Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
As a workaround for anyone, you can use nmcli to bring up a VPN connection. Run `nmcli c` to get a list of connections, once you have the name you can enable it with `nmcli c up $name` or disable it with `nmcli c down $name`. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.3-3ubuntu1 Candidate: 3.38.3-3ubuntu1 Version table: *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
This looks to be around the time of the issue where I disabled a VPN connection (from syslog): Mar 8 14:11:54 splat gnome-shell[677801]: ** Mar 8 14:11:54 splat gnome-shell[677801]: Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) Mar 8 14:11:54 splat gnome-shell[677801]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) Mar 8 14:11:54 splat gnome-shell[677801]: GNOME Shell crashed with signal 6 Mar 8 14:11:54 splat gnome-shell[677801]: == Stack trace for context 0x556edc56f150 == Mar 8 14:11:54 splat gnome-shell[677801]: #0 556edea1ffc0 i resource:///org/gnome/shell/ui/popupMenu.js:390 (1162dc8fad80 @ 138) Mar 8 14:11:54 splat gnome-shell[677801]: #1 556edea1ff18 i resource:///org/gnome/shell/ui/status/network.js:1429 (2ab06bf803d0 @ 171) Mar 8 14:11:54 splat gnome-shell[677801]: #2 556edea1fe80 i resource:///org/gnome/shell/ui/status/network.js:171 (2ab06bf82560 @ 111) Mar 8 14:11:54 splat gnome-shell[677801]: #3 7ffef0da2770 b self-hosted:850 (b5d5c736d80 @ 454) Mar 8 14:11:54 splat gnome-shell[677801]: #4 556edea1fde0 i resource:///org/gnome/shell/ui/popupMenu.js:411 (1162dc8face0 @ 56) Mar 8 14:11:54 splat gnome-shell[677801]: #5 556edea1fd48 i resource:///org/gnome/shell/ui/popupMenu.js:398 (1162dc8fad30 @ 41) Mar 8 14:11:54 splat gnome-shell[677801]: #6 556edea1fca8 i resource:///org/gnome/shell/ui/popupMenu.js:138 (1162dc8fb4c0 @ 88) Mar 8 14:11:54 splat systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 8 14:11:54 splat dbus-daemon[1286]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+attachment/5474636/+files/journal ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: - Installed: 1.30.0-1ubuntu1 - Candidate: 1.30.0-1ubuntu1 + Installed: 1.30.0-1ubuntu1 + Candidate: 1.30.0-1ubuntu1 + Version table: + *** 1.30.0-1ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages + 100 /var/lib/dpkg/status + + $ apt-cache policy gnome-shell + gnome-shell: + Installed: 3.38.3-3ubuntu1 + Candidate: 3.38.3-3ubuntu1 Version table: - *** 1.30.0-1ubuntu1 500 + *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: - libssl1.1 - libssl1.1 + libssl1.1 + libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.30.0 connected started full enabled enabled disabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.30.0 connected started full enabled enabled disabled enabled enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubu
[Desktop-packages] [Bug 1918190] [NEW] Enabling/Disabling VPN crashes window manager
Public bug reported: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1918190 Title: Enabling/Disabling VPN crashes window manager Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1
I'm using xorg because wayland has bug #1918189 (can't share terminals in Google Meet) blocking me from using wayland as a daily driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1917926 Title: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918189] [NEW] Can not share gnome-terminal in Google Meet under xwayland
Public bug reported: When running xwayland in Hirsute I am unable to share gnome-terminal windows from Google Meet. In Google Meet running in Chrome v89.0.4389.82 when I select the share a window I do not see my gnome- terminal windows listed as an option to share. Here is what I am running with, I can provide additional package info $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ apt-cache policy xwayland xwayland: Installed: 2:1.20.10-3ubuntu3 Candidate: 2:1.20.10-3ubuntu3 Version table: *** 2:1.20.10-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status I'd be nice to be able to use wayland and have features on par with xorg and right now I have to do this because of bug #1917926 making xorg unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xwayland 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:03:30 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.10.0-14-generic, x86_64: installed v4l2loopback, 0.12.5, 5.8.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.3.4-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute reproducible single-occurrence ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1918189 Title: Can not share gnome-terminal in Google Meet under xwayland Status in xorg-server package in Ubuntu: New Bug description: When running xwayland in Hirsute I am unable to share gnome-terminal windows from Google Meet. In Google Meet running in Chrome v89.0.4389.82 when I select the share a window I do not see my gnome- terminal windows listed as an option to share. Here is what I am running with, I can provide additional package info $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ apt-cache policy xwayland xwayland: Installed: 2:1.20.10-3ubuntu3 Candidate: 2:1.20.10-3ubuntu3 Version table: ***
[Desktop-packages] [Bug 1866616] Re: 2nd display stopped working
Attaching the 2nd display via DisplayPort rather than DVI allows me to use it again, so I happen to have a solution, but not everyone may be so lucky. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866616] [NEW] 2nd display stopped working
Public bug reported: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal regression reproducible ubuntu ** Description changed: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. - I've notices that Xorg.0.log shows fbdev rather than amdgpu in use (as - it had in the past). + I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd + monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) -Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) + Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1866616] Re: 2nd display stopped working
The log shows "open /dev/dri/card0: No such file or directory" but it does exist: $ ls -l /dev/dri/card0 crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0 Unplugging the display from DVI-D-0 and plugging it back in does not result in showing up in xrandr output. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788231] Re: Silently discards tar contents after a file with xattrs is encountered
libarchive 3.3.0 appears to add xattr support for gnu tar archives, this needs to be tested still but likely this is a key part of our issue. https://github.com/libarchive/libarchive/releases/tag/v3.3.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1788231 Title: Silently discards tar contents after a file with xattrs is encountered Status in file-roller package in Ubuntu: New Bug description: Steps to reproduce: 1) Create a tar file containing /usr/bin/mtr-packet (which has xattrs) (and a file before and after to confirm the behaviour): $ tar -C / --xattrs --xattrs-include=\* etc/adduser.conf usr/bin/mtr-packet etc/aliases -cf reproducer.tar 2) Confirm that tar reads the file correctly: $ tar tf reproducer.tar etc/adduser.conf usr/bin/mtr-packet etc/aliases 3) Open the file with file-roller (`file-roller reproducer.tar`) Expected behaviour: All three files are displayed in the UI Actual behaviour: Only etc/adduser.conf appears in the UI ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: file-roller 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 21 11:41:05 2018 InstallationDate: Installed on 2017-10-23 (301 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: file-roller UpgradeStatus: Upgraded to bionic on 2018-01-23 (210 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1788231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788231] Re: Silently discards tar contents after a file with xattrs is encountered
@daniel-thewatkins, this is still failing on cosmic with 3.30.0-1 but it's likely a library, like libarchive, and not file-roller. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1788231 Title: Silently discards tar contents after a file with xattrs is encountered Status in file-roller package in Ubuntu: New Bug description: Steps to reproduce: 1) Create a tar file containing /usr/bin/mtr-packet (which has xattrs) (and a file before and after to confirm the behaviour): $ tar -C / --xattrs --xattrs-include=\* etc/adduser.conf usr/bin/mtr-packet etc/aliases -cf reproducer.tar 2) Confirm that tar reads the file correctly: $ tar tf reproducer.tar etc/adduser.conf usr/bin/mtr-packet etc/aliases 3) Open the file with file-roller (`file-roller reproducer.tar`) Expected behaviour: All three files are displayed in the UI Actual behaviour: Only etc/adduser.conf appears in the UI ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: file-roller 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 21 11:41:05 2018 InstallationDate: Installed on 2017-10-23 (301 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: file-roller UpgradeStatus: Upgraded to bionic on 2018-01-23 (210 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1788231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724597] Re: Regression: Text selection not places in PRIMARY clipboard
Restarted the desktop and I can't recreate, closing. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1724597 Title: Regression: Text selection not places in PRIMARY clipboard Status in gnome-terminal package in Ubuntu: Invalid Bug description: On artful this morning my text selections in gnome-terminal (and not in other desktop applications) are not places in the PRIMARY clipboard (or whatever you call the middle mouse button). I don't find a user preference to change this. I would like to be able to highlight text with the mouse in the terminal and then paste with middle mouse button. Middle mouse paste does work in the terminal for text selected in other applications. Only the placement of text into the paste buffer is failing in gnome-terminal. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-terminal-data gnome-terminal-data: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1724597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724597] [NEW] Regression: Text selection not places in PRIMARY clipboard
Public bug reported: On artful this morning my text selections in gnome-terminal (and not in other desktop applications) are not places in the PRIMARY clipboard (or whatever you call the middle mouse button). I don't find a user preference to change this. I would like to be able to highlight text with the mouse in the terminal and then paste with middle mouse button. Middle mouse paste does work in the terminal for text selected in other applications. Only the placement of text into the paste buffer is failing in gnome-terminal. $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-terminal-data gnome-terminal-data: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1724597 Title: Regression: Text selection not places in PRIMARY clipboard Status in gnome-terminal package in Ubuntu: New Bug description: On artful this morning my text selections in gnome-terminal (and not in other desktop applications) are not places in the PRIMARY clipboard (or whatever you call the middle mouse button). I don't find a user preference to change this. I would like to be able to highlight text with the mouse in the terminal and then paste with middle mouse button. Middle mouse paste does work in the terminal for text selected in other applications. Only the placement of text into the paste buffer is failing in gnome-terminal. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-terminal-data gnome-terminal-data: Installed: 3.24.2-0ubuntu4 Candidate: 3.24.2-0ubuntu4 Version table: *** 3.24.2-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1724597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
These are working with 16.04 perfectly, I updated to 16.10 and had to restore from backups to get back to 16.10. Then I booted from the live- cd to capture this bug. Scenarios: 1. mDP to HDMI cable connected to a 1080p monitor (Dell E248Wfp); that is the simple example and they all fail with the same result. 2. same Dell via DP2 on the doc using a DP to single-link DVI adapter (like http://www.monoprice.com/product?c_id=104&cp_id=10428&cs_id=1042801&p_id=4827) 3. DP2 on the doc connected to a Shimian LCD running at 2560x1440 connected via a Dell (BizLink) DisplayPort to DVI Dual Link Adapter (like https://www.amazon.com/Dell-BIZLINK-DisplayPort-Adapter-Powered/dp/B003XYBA72). But I didn't want to confuse the issue with that more niche bit of hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Incomplete Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
Also, the bug was opened with the system running BIOS version 2.57: dmi.bios.version: G2ET97WW (2.57 ) I have upgraded to the latest version and recreated there as well: Version: G2ETA7WW (2.67 ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Incomplete Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
I have tried two monitors of different brands and a random television. The resolution selected is 1920x1080. On Mon, Oct 10, 2016 at 7:19 PM, Mathieu Trudel-Lapierre < mathieu...@gmail.com> wrote: > Could you please try with a different monitor or share more of the > details of how you are using this, such as which resolution is picked? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1631519 > > Title: > No X on boot with external monitor connected > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > When booting from today's (201610907) daily yakkety livecd with an > external display attached X does not start. > > If the external monitor is attached after X has started I can boot to > the desktop using only using the laptop's LCD (ThinkPad x230, intel > graphics). The attaching a 1920x1080 LCD via miniDP extends the > desktop but windows moved around produce a trail of windows that > persist even after the window is closed. > > This is a regression from Xenial. > > $ lsb_release -rd > Description: Ubuntu Yakkety Yak (development branch) > Release: 16.10 > > $ apt-cache policy xorg > xorg: > Installed: 1:7.7+13ubuntu4 > Candidate: 1:7.7+13ubuntu4 > Version table: >*** 1:7.7+13ubuntu4 500 > 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: xorg 1:7.7+13ubuntu4 > ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 > Uname: Linux 4.8.0-19-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.3-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.379 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Fri Oct 7 20:23:46 2016 > DistUpgraded: Fresh install > DistroCodename: yakkety > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Lenovo 3rd Gen Core processor Graphics Controller > [17aa:21fa] > LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) > MachineType: LENOVO 2306CTO > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi > file=/cdrom/preseed/username.seed boot=casper quiet splash --- > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/25/2013 > dmi.bios.vendor: LENOVO > dmi.bios.version: G2ET97WW (2.57 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 2306CTO > dmi.board.vendor: LENOVO > dmi.board.version: Not Defined > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO: > pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO: > rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.name: 2306CTO > dmi.product.version: ThinkPad X230 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.70-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.2-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160706-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-2 > xserver.bootTime: Fri Oct 7 20:18:12 2016 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-1ubuntu6 > xserver.video_driver: modeset > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Incomplete Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external moni
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
Still failing with http://cdimage.ubuntu.com/daily-live/20161008 /yakkety-desktop-amd64.iso (Yakkety Final) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: Confirmed Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
The attached gif tries to show the effect of moving a window across the screen. Not captured in the low-framerate gif is that the trails of the window are flickering and moving (compiz cpu usage is high when this happens). Hitting WIN+w to display windows and then drop back to the desktop clears the current trail. But that is not a reasonable workaround and does not address the basic issue that the livecd (or a fully installed desktop) does not boot to X with an external monitor attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
A monitor attached to the Thinkpad x230 via the docking station DVI port is fine (boots to X and no crazy window trails). This is seen when attaching a monitor via DP on the dock or mDP from the laptop. I was using an mDP to HDMI cable or a DP to DualLink-DVI adapter to connect monitors when I found this issue. Multiple monitors were tried and all experienced the issue when connect to the monitor's HDMI port from the laptop's mDP port. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
** Attachment added: "moving a window across the display" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+attachment/4757009/+files/ezgif.com-video-to-gif%20%282%29.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
** Summary changed: - xorg hall-of-mirrors on external display + No X on boot with external monitor connected ** Description changed: - Running from today's (201610907) daily yakkety livecd I can boot to the - desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). - Attaching a 1920x1080 LCD via miniDP extends the desktop but windows - moved around produce a trail of windows that persist even after the - window is closed. + When booting from today's (201610907) daily yakkety livecd with an + external display attached X does not start. - Also, when booting from the livecd with the external display attached X - does not start. + If the external monitor is attached after X has started I can boot to + the desktop using only using the laptop's LCD (ThinkPad x230, intel + graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop + but windows moved around produce a trail of windows that persist even + after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: - Installed: 1:7.7+13ubuntu4 - Candidate: 1:7.7+13ubuntu4 - Version table: - *** 1:7.7+13ubuntu4 500 - 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+13ubuntu4 + Candidate: 1:7.7+13ubuntu4 + Version table: + *** 1:7.7+13ubuntu4 500 + 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Changed in: xorg (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monit
[Desktop-packages] [Bug 1631519] [NEW] No X on boot with external monitor connected
Public bug reported: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No value set for