[Desktop-packages] [Bug 1759644] [NEW] [18.04] Regression: wired network does not work upon resume from suspend
Public bug reported: After upgrade to 18.04 (bionic) I've encountered the following regression: wired network connection does not work, when system is resumed from suspend. Reloading the kernel driver module seems to help: sudo modprobe -r r8169 sudo modprobe r8169 Could this be fixed structurally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 20:08:20 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-01-06 (811 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 ethernet 1522260260 wo 28 mrt 2018 20:04:20 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/3 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- dzente a899e56b-4048-43a8-bc38-9212d0af383b wifi 1493769143 wo 03 mei 2017 01:52:23 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected/org/freedesktop/NetworkManager/Devices/4 Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1759644 Title: [18.04] Regression: wired network does not work upon resume from suspend Status in network-manager package in Ubuntu: New Bug description: After upgrade to 18.04 (bionic) I've encountered the following regression: wired network connection does not work, when system is resumed from suspend. Reloading the kernel driver module seems to help: sudo modprobe -r r8169 sudo modprobe r8169 Could this be fixed structurally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 20:08:20 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-01-06 (811 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago) nmcli-con:
[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect
- $ env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (38.5 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S - And that is it. -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (734 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect
@Daniel Even env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash does not provide needed link. Are there any system settings that can affect this behavior? -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (734 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1741886/+attachment/5034294/+files/ProcEnviron.txt -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (734 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1741886/+attachment/5034293/+files/ProcCpuinfoMinimal.txt -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (734 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1741886/+attachment/5034292/+files/JournalErrors.txt -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (734 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect
apport information ** Tags added: apport-collected ** Description changed: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + GsettingsChanges: + b'org.gnome.shell' b'app-picker-view' b'uint32 1' + b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.desktop.interface' b'cursor-blink' b'false' + b'org.gnome.desktop.interface' b'clock-show-date' b'true' + InstallationDate: Installed on 2016-01-06 (734 days ago) + InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: gnome-shell 3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 + Tags: artful + Uname: Linux 4.13.0-25-generic x86_64 + UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1741886/+attachment/5034291/+files/Dependencies.txt -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect
Well, I have done what you suggested. Invoking ubuntu-bug on a crash file creates corresponding upload* files but does not print any links. -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect
@Daniel The above commands do bring me to a web-page, but there are no uploaded relevant error reports, although I see them in /var/crash ** Attachment added: "/var/crash screenshot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+attachment/5033441/+files/20180108_ls_var_crash.png -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1741886] [NEW] GNOME shell crashes with sig 11 upon monitor disconnect
Public bug reported: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1741886 Title: GNOME shell crashes with sig 11 upon monitor disconnect Status in gnome-shell package in Ubuntu: New Bug description: Upon physical disconnect/connect of a monitor (connected via HDMI) shell crashes with signal 11. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.2-0ubuntu0.1 Expected is that physical disconnect/connect of a monitor will not influence the desktop environment. Note that the crash file was generated and according to /var/crash content was uploaded, when ubuntu-bug triggered by existence of crash file started up and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me to Launchpad (yet another bug???) for providing details, therefore I've used "ubuntu-bug gnome-shell" instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 13:12:14 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-blink' b'false' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-01-06 (732 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10
Another possible duplicate: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262 -- 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/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 Status in network-manager package in Ubuntu: In Progress Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: In Progress Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed before rebooting you should have a network connection after you reboot. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install netplan, configure to set up static network on an ethernet device using netplan. 4) Upgrade to yakkety 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1675934] [NEW] Screen corruption after resuming system from suspend
Public bug reported: Upon resuming system from suspend I observe graphical artefacts. This is a regression, since I've noticed this behaviour only after latest updates. Rebooting system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 22:20:38 2017 DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4] InstallationDate: Installed on 2016-01-06 (442 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 23 19:44:08 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial -- 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/1675934 Title: Screen corruption after resuming system from suspend Status in xorg package in Ubuntu: New Bug description: Upon resuming system from suspend I observe graphical artefacts. This is a regression, since I've noticed this behaviour only after latest updates. Rebooting system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0'
[Desktop-packages] [Bug 1675934] Re: Screen corruption after resuming system from suspend
** Attachment added: "bug_2017-03-24_22-22-32.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+attachment/4845050/+files/bug_2017-03-24_22-22-32.png -- 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/1675934 Title: Screen corruption after resuming system from suspend Status in xorg package in Ubuntu: New Bug description: Upon resuming system from suspend I observe graphical artefacts. This is a regression, since I've noticed this behaviour only after latest updates. Rebooting system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 22:20:38 2017 DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4] InstallationDate: Installed on 2016-01-06 (442 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 23 19:44:08 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+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 1551976] Re: Headphones not activated after unplugging/plugging-in
Puzzled... Was this instruction for me to do something??? On Wed, Mar 2, 2016 at 12:51 AM, Raymond <1551...@bugs.launchpad.net> wrote: > ports: analog-input-front-mic: Front Microphone (priority 8500, latency > offset 0 usec, available: no) properties: device.icon_name = "audio- > input-microphone" analog-input-rear-mic: Rear Microphone (priority 8200, > latency offset 0 usec, available: no) properties: device.icon_name = > "audio-input-microphone" analog-input-linein: Line In (priority 8100, > latency offset 0 usec, available: no) properties: analog-output-lineout: > Line Out (priority 9900, latency offset 0 usec, available: no) > properties: analog-output-headphones: Headphones (priority 9000, latency > offset 0 usec, available: yes) properties: device.icon_name = "audio- > headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0, > latency offset 0 usec, available: unknown) properties: > > Seem no line out plugged, do pulseaudio switch to digial after headphone > is unplugged > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1551976 > > Title: > Headphones not activated after unplugging/plugging-in > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1551976 Title: Headphones not activated after unplugging/plugging-in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+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 1551976] [NEW] Headphones not activated after unplugging/plugging-in
Public bug reported: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1551976 Title: Headphones not activated after unplugging/plugging-in Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Expected behavior: Sound is played-back via headphones, when they are plugged-in. Observed behavior: Unplugging/plugging-in headphones disables headphones sound. To restore sound, user needs to go to sound settings, and switch "Output" to "Headphones" This is a regression from 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1692 F pulseaudio /dev/snd/controlC0: alexei 1692 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 1 22:43:40 2016 InstallationDate: Installed on 2016-01-06 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
The same as in comment #101 for nvidia-331-updates on 14.10 (utopic) nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Bug description: Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+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 1336537] [NEW] LaTeX: Russian names of some months in \today command are incorrect.
Public bug reported: \todayrussian command returns date string in ancient Russian instead of plain Russian, which is visible in certain names. For example, for the 1st of June 2014 one expects to see 1 июня 2014 г. whereas 1 iюня 2014 г. is printed. The bug is in russianb.ldf of CTAN babel-russian package v1.3a shipped in the Package: texlive-lang-cyrillic Version: 2013.20140215-1 According to changelog in [1] this bug was fixed in v1.3c of the package. Please update texlive-lang-cyrillic to include newer version of babel-russian to fix this issue. [1] http://archive.cs.uu.nl/mirror/CTAN/macros/latex/contrib/babel-contrib/russian/README ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: texlive-lang-cyrillic 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 1 22:30:54 2014 InstallationDate: Installed on 2012-06-28 (733 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: texlive-lang UpgradeStatus: Upgraded to trusty on 2014-03-07 (116 days ago) ** Affects: texlive-lang (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1336537 Title: LaTeX: Russian names of some months in \today command are incorrect. Status in “texlive-lang” package in Ubuntu: New Bug description: \todayrussian command returns date string in ancient Russian instead of plain Russian, which is visible in certain names. For example, for the 1st of June 2014 one expects to see 1 июня 2014 г. whereas 1 iюня 2014 г. is printed. The bug is in russianb.ldf of CTAN babel-russian package v1.3a shipped in the Package: texlive-lang-cyrillic Version: 2013.20140215-1 According to changelog in [1] this bug was fixed in v1.3c of the package. Please update texlive-lang-cyrillic to include newer version of babel-russian to fix this issue. [1] http://archive.cs.uu.nl/mirror/CTAN/macros/latex/contrib/babel-contrib/russian/README ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: texlive-lang-cyrillic 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 1 22:30:54 2014 InstallationDate: Installed on 2012-06-28 (733 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: texlive-lang UpgradeStatus: Upgraded to trusty on 2014-03-07 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1336537/+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 1120584] Re: DPI settings do not influence scan result on Epson Stylus Photo PX710W
Hi Michael, Thank you for looking into this. Yes, I think it is a duplicate of Bug #891586 After reading it through, I do not get why resolution list is not computed correctly: on my unit it should be intersection of x/y-resolution lists, there are no other units attached, i.e. there should be no other possible resolution lists to intersect with. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1120584 Title: DPI settings do not influence scan result on Epson Stylus Photo PX710W Status in “simple-scan” package in Ubuntu: Incomplete Bug description: Scanner ID: Bus 001 Device 004: ID 04b8:0852 Seiko Epson Corp. I have a good faith belief that this is a bug in Simple Scan and not in sane-backends because I actually tried with xsane and it worked there. Essence of problem: I do not see difference in files saved after change of setting between 300dpi vs. 600dpi for images or 150dpi vs 300/600dpi for text Here I make my point based on the file sizes. The following files were generated by Simple Scan in various Text/Image 300/600 dpi settings. ~/tmp/ocr_try$ ls -lh ss* -rw-rw-r-- 1 user1 user1 2,2M feb 9 19:43 ss_image_300dpi.png -rw-rw-r-- 1 user1 user1 2,2M feb 9 19:53 ss_image_600dpi.png -rw-rw-r-- 1 user1 user1 77K feb 9 19:44 ss_text_300dpi.png -rw-rw-r-- 1 user1 user1 79K feb 9 19:52 ss_text_600dpi.png For comparison, files obtained by scan with various settings in Image Scan! for Linux from Epson: ~/tmp/ocr_try$ ls -lh is* -rw-rw-r-- 1 user1 user1 96K feb 9 20:31 is_150dpi_text_bw.png -rw-rw-r-- 1 user1 user1 702K feb 9 20:26 is_300dpi_image_bw.png -rw-rw-r-- 1 user1 user1 2,2M feb 9 20:18 is_300dpi_image.png -rw-rw-r-- 1 user1 user1 261K feb 9 20:24 is_300dpi_text_bw.png -rw-rw-r-- 1 user1 user1 789K feb 9 20:21 is_300dpi_text.png -rw-rw-r-- 1 user1 user1 2,6M feb 9 20:25 is_600dpi_image_bw.png -rw-rw-r-- 1 user1 user1 7,9M feb 9 20:20 is_600dpi_image.png -rw-rw-r-- 1 user1 user1 851K feb 9 20:25 is_600dpi_text_bw.png -rw-rw-r-- 1 user1 user1 2,5M feb 9 20:20 is_600dpi_text.png Note that Simple Scan Text file size for 300/600dpi settings roughly corresponds to Image Scan 150dpi for BW Document (150dpi is default for Text in Simple Scan), while Simple Scan 300/600dpi Image corresponds to Image Scan 300dpi Color Photo settings. Another couple of scans acquired with XSane: ~/tmp/ocr_try$ ls -lh xsane* -rw-r- 1 user1 user1 772K feb 9 21:18 xsane_300dpi_gray.png -rw-r- 1 user1 user1 2,9M feb 9 21:17 xsane_600dpi_gray.png Note that sizes of XSane generated files roughly match to Image Scan 300dpi BW Image and 600dpi BW image. I think that it is very important to have ability to make scans with 300dpi BW settings since those are recommended settings for better OCR performance. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: simple-scan 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4 Uname: Linux 3.5.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Feb 9 21:03:53 2013 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.12.6-3ubuntu4 hpoj N/A InstallationDate: Installed on 2012-06-28 (226 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-24-generic root=UUID=44ee0b94-7db6-4348-a0ab-a3889128485f ro quiet splash SourcePackage: simple-scan UpgradeStatus: Upgraded to quantal on 2012-12-21 (49 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1120584/+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 1120584] [NEW] DPI settings do not influence scan result on Epson Stylus Photo PX710W
Public bug reported: Scanner ID: Bus 001 Device 004: ID 04b8:0852 Seiko Epson Corp. I have a good faith belief that this is a bug in Simple Scan and not in sane-backends because I actually tried with xsane and it worked there. Essence of problem: I do not see difference in files saved after change of setting between 300dpi vs. 600dpi for images or 150dpi vs 300/600dpi for text Here I make my point based on the file sizes. The following files were generated by Simple Scan in various Text/Image 300/600 dpi settings. ~/tmp/ocr_try$ ls -lh ss* -rw-rw-r-- 1 user1 user1 2,2M feb 9 19:43 ss_image_300dpi.png -rw-rw-r-- 1 user1 user1 2,2M feb 9 19:53 ss_image_600dpi.png -rw-rw-r-- 1 user1 user1 77K feb 9 19:44 ss_text_300dpi.png -rw-rw-r-- 1 user1 user1 79K feb 9 19:52 ss_text_600dpi.png For comparison, files obtained by scan with various settings in Image Scan! for Linux from Epson: ~/tmp/ocr_try$ ls -lh is* -rw-rw-r-- 1 user1 user1 96K feb 9 20:31 is_150dpi_text_bw.png -rw-rw-r-- 1 user1 user1 702K feb 9 20:26 is_300dpi_image_bw.png -rw-rw-r-- 1 user1 user1 2,2M feb 9 20:18 is_300dpi_image.png -rw-rw-r-- 1 user1 user1 261K feb 9 20:24 is_300dpi_text_bw.png -rw-rw-r-- 1 user1 user1 789K feb 9 20:21 is_300dpi_text.png -rw-rw-r-- 1 user1 user1 2,6M feb 9 20:25 is_600dpi_image_bw.png -rw-rw-r-- 1 user1 user1 7,9M feb 9 20:20 is_600dpi_image.png -rw-rw-r-- 1 user1 user1 851K feb 9 20:25 is_600dpi_text_bw.png -rw-rw-r-- 1 user1 user1 2,5M feb 9 20:20 is_600dpi_text.png Note that Simple Scan Text file size for 300/600dpi settings roughly corresponds to Image Scan 150dpi for BW Document (150dpi is default for Text in Simple Scan), while Simple Scan 300/600dpi Image corresponds to Image Scan 300dpi Color Photo settings. Another couple of scans acquired with XSane: ~/tmp/ocr_try$ ls -lh xsane* -rw-r- 1 user1 user1 772K feb 9 21:18 xsane_300dpi_gray.png -rw-r- 1 user1 user1 2,9M feb 9 21:17 xsane_600dpi_gray.png Note that sizes of XSane generated files roughly match to Image Scan 300dpi BW Image and 600dpi BW image. I think that it is very important to have ability to make scans with 300dpi BW settings since those are recommended settings for better OCR performance. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: simple-scan 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4 Uname: Linux 3.5.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Feb 9 21:03:53 2013 DriverPackageVersions: libsane 1.0.23-0ubuntu1 libsane-extras N/A hplip 3.12.6-3ubuntu4 hpoj N/A InstallationDate: Installed on 2012-06-28 (226 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-24-generic root=UUID=44ee0b94-7db6-4348-a0ab-a3889128485f ro quiet splash SourcePackage: simple-scan UpgradeStatus: Upgraded to quantal on 2012-12-21 (49 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ** Attachment added: Debug logs collected for 300dpi and 600dpi settings via simple-scan --debug simple-scan_x00dpi_text.log 21 https://bugs.launchpad.net/bugs/1120584/+attachment/3522442/+files/simple-scan-debug-logs_300dpi_vs_600_dpi.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1120584 Title: DPI settings do not influence scan result on Epson Stylus Photo PX710W Status in “simple-scan” package in Ubuntu: New Bug description: Scanner ID: Bus 001 Device 004: ID 04b8:0852 Seiko Epson Corp. I have a good faith belief that this is a bug in Simple Scan and not in sane-backends because I actually tried with xsane and it worked there. Essence of problem: I do not see difference in files saved after change of setting between 300dpi vs. 600dpi for images or 150dpi vs 300/600dpi for text Here I make my point based on the file sizes. The following files were generated by Simple Scan in various Text/Image 300/600 dpi settings. ~/tmp/ocr_try$ ls -lh ss* -rw-rw-r-- 1 user1 user1 2,2M feb 9 19:43 ss_image_300dpi.png
