[Desktop-packages] [Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Expired Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 1801494] Re: dock missing
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 Version table: *** 0.9.1ubuntu18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 4) dock is there 5) dock is not there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+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 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily Status in gnome-shell package in Ubuntu: Expired Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04. I then upgraded it to 18.10 for a short while, before wiping it and installing 19.04 from a fresh ISO download after that was released. This is the non-touch non-4K version (13-inch 1080p). I have the i7 model with 16GB of RAM and an NVMe SSD (so the performance should be pretty good). Sometimes when typing in Gnome Terminal, the screen just freezes for around 1 second. The cursor doesn't move, additional keypresses don't appear, and any moving content doesn't update. After the freeze stops, all the keypresses that occurred during the freeze do appear (they're not lost). Immediately after the freeze, I don't see anything in dmesg output that gives a clue. It almost feels how some old desktops did around 10-15 years ago when everything would lock up while waiting for slow HDD I/O, and then suddenly keypresses etc. would catch-up. If there is something specific I should look for immediately after a freeze in order to debug further, please let me know. Note that this happens both on battery power but also when plugged into the charger. Someone else on AskUbuntu asked this question for the same model (9380), which sounds very similar to what I'm seeing on mine (the freezing part): https://askubuntu.com/questions/1133191/ubuntu-18-04 -on-dell-xps-9380-small-freezes-and-jumping-touchpad Note that I filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790 for what I think is a separate issue related to screen flashing (as opposed to freezing). The two events do not seem to happen at the same time which is why I've filed them separately. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 16:16:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-04-28 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64
[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
Can confirm #43 The latest I experienced of this bug, all I have to do is click on **show applications** ( 9 dots ) icon to get rid of the freeze. Looks like not necessary to click on the search box or type a letter in 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/1807056 Title: Occasional Keyboard freeze Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/907 --- I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807056/+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 1837266] Re: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1837266 Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137 Status in pygobject package in Ubuntu: New Bug description: I'm running Ubuntu 114.04 on a 32-bit Lenovo T61. When I try to launch alacarte from the menus or from the command line I get $ alacarte Traceback (most recent call last): File "/usr/bin/alacarte", line 23, in from Alacarte.MainWindow import main File "/usr/share/alacarte/Alacarte/MainWindow.py", line 20, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 36, in from ._gi import _gobject ModuleNotFoundError: No module named 'gi._gi' Web pages I've looked at suggest reinstalling python3-gi, but apt-get and Synaptic won't do that for me - instead apt-get locks up in a tight 100% processor usage loop. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-gi 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: python-gi: Install python3-gi: Install python-gi: Configure python3-gi: Configure Architecture: i386 Date: Fri Jul 19 16:08:12 2019 DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess new pre-removal script returned error exit status 137 ErrorMessage: subprocess new pre-removal script returned error exit status 137 InstallationDate: Installed on 2016-05-13 (1162 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: pygobject Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1837266/+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 1837266] [NEW] package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137
Public bug reported: I'm running Ubuntu 114.04 on a 32-bit Lenovo T61. When I try to launch alacarte from the menus or from the command line I get $ alacarte Traceback (most recent call last): File "/usr/bin/alacarte", line 23, in from Alacarte.MainWindow import main File "/usr/share/alacarte/Alacarte/MainWindow.py", line 20, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 36, in from ._gi import _gobject ModuleNotFoundError: No module named 'gi._gi' Web pages I've looked at suggest reinstalling python3-gi, but apt-get and Synaptic won't do that for me - instead apt-get locks up in a tight 100% processor usage loop. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-gi 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: python-gi: Install python3-gi: Install python-gi: Configure python3-gi: Configure Architecture: i386 Date: Fri Jul 19 16:08:12 2019 DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess new pre-removal script returned error exit status 137 ErrorMessage: subprocess new pre-removal script returned error exit status 137 InstallationDate: Installed on 2016-05-13 (1162 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: pygobject Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1837266 Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137 Status in pygobject package in Ubuntu: New Bug description: I'm running Ubuntu 114.04 on a 32-bit Lenovo T61. When I try to launch alacarte from the menus or from the command line I get $ alacarte Traceback (most recent call last): File "/usr/bin/alacarte", line 23, in from Alacarte.MainWindow import main File "/usr/share/alacarte/Alacarte/MainWindow.py", line 20, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 36, in from ._gi import _gobject ModuleNotFoundError: No module named 'gi._gi' Web pages I've looked at suggest reinstalling python3-gi, but apt-get and Synaptic won't do that for me - instead apt-get locks up in a tight 100% processor usage loop. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-gi 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: python-gi: Install python3-gi: Install python-gi: Configure python3-gi: Configure Architecture: i386 Date: Fri Jul 19 16:08:12 2019 DuplicateSignature: package:python-gi:3.12.0-1ubuntu1:subprocess new pre-removal script returned error exit status 137 ErrorMessage: subprocess new pre-removal script returned error exit status 137 InstallationDate: Installed on 2016-05-13 (1162 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: pygobject Title: package python-gi 3.12.0-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1837266/+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 1835625] Re: Shows old snap edge version of thunderbird
As I wrote on the snapcraft forums, that's a problem then as long as the snap continues to be out of date/unstable, as the snap replaces the deb version for users that don't have Thunderbird installed. I don't mind if non-stable snaps appear in the store, but they should not be default if a deb version is also available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1835625 Title: Shows old snap edge version of thunderbird Status in gnome-software package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Fix Released Bug description: Test case: Open ubuntu-software, search thunderbird Version returned is an old edge version of thunderbird not meant to be used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 14:57:47 2019 InstallationDate: Installed on 2019-07-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190703) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu8 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835625/+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 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications
Any opinions? https://bugzilla.redhat.com/show_bug.cgi?id=1670504#c102 :-) ** Bug watch added: Red Hat Bugzilla #1670504 https://bugzilla.redhat.com/show_bug.cgi?id=1670504 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/1836462 Title: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications Status in xdg-user-dirs package in Ubuntu: New Status in xdg-user-dirs package in Fedora: Unknown Bug description: Renaming "Templates" to "# Templates" fixes a lot of speed issues in a range of desktop applications, e.g. file managers, text editors, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I have also been trying to see what are the packages difference between the OEM version and 19.04 since I suspect that Dell might have addressed this issue in their version. I have a list of all packages that were on the OEM but that might be tedious. If we contacted Dell directly, would they be able to help narrow it down / provide packages that they set up on the OEM? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+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 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Hello all, I believe that I have this same bug, also after a 19.04 fresh install. I initially posted on that bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125 but they kindly directed me here. Of note, I am glad you tried wayland as I wanted to try if that made any difference. I have tried passing different kernel parameters (though not all combinations) namely: First try: i915.edp_vswing=2 Second try: i915.fastboot=1 i915.edp_vswing=1 i915.preliminary_hw_support=1 intel_idle.max_cstate=1 acpi_backlight=vendor acpi.osi=Linux (see https://www.reddit.com/r/linuxquestions/comments/ayi4n6/flickering_on_laptops_with_a_4k_screen_and_intel/) but that did not seem to make any difference apart from disabling the backlight controls It somewhat feels good to have that identified as a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+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 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
This is still an issue!
It is also more important than "low".
We need to have a way to secure desktops when users forget to log out
when stepping away.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open.
No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using
other mechanisms to prevent the idle timeout. Any ideas on what to
look for?
Julian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+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 1836881] Re: gnome-shell freeze
oh okay. I actually updated from ubuntu 18.04 to 19.04 in the expectation that the bug disappears. I do not have enough time now for trying to figure out this issue due to some academic deadline. But I will follow the steps as soon as the bug happens again in version 19.04 though. Thank you very much! On Fri, 19 Jul 2019 at 04:50, Daniel van Vugt wrote: > OK I missed some steps there sorry... > > The command: > > apport-cli --hanging -P PID > > will give you a link to help you complete creation of a new bug. You > then need to follow that link, on any machine. Don't send us that link. > > After you have created a new bug, please tell us its ID. > > If that didn't work then please look at > https://errors.ubuntu.com/user/ID where ID is the content of file > /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to > recent problems on that page? If so then please send the links to us. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1836881 > > Title: > gnome-shell freeze > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > My gnome session freezes, mouse works fine but cannot start > applications. I am able to enter one of the tty terminals and kill the > session. This happens a few times a day and started a week ago > probably. > > Douglas > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 > Uname: Linux 4.15.0-54-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Jul 17 12:29:38 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: >nvidia, 418.56, 4.15.0-52-generic, x86_64: installed >nvidia, 418.56, 4.15.0-54-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GpuHangFrequency: Several times a week > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Within the last few days > GraphicsCard: >Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: Acer Incorporated [ALI] Device [1025:1208] >NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev > a1) (prog-if 00 [VGA controller]) > Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti > Mobile] [1025:1207] > InstallationDate: Installed on 2018-01-13 (550 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 > (20171018) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. >Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. >Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Acer Predator PH317-51 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic > root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2017 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V1.05 > dmi.board.asset.tag: Type2 - Board Serial Number > dmi.board.name: Sienna_KLS > dmi.board.vendor: KBL > dmi.board.version: V1.05 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.05 > dmi.modalias: > dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: > dmi.product.family: Predator Helios 300 > dmi.product.name: Predator PH317-51 > dmi.product.version: V1.05 > dmi.sys.vendor: Acer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836881/+subscriptions > -- 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/1836881 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu:
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
So finally this has been fixed also in 18.04. I want to thank Steven Santos who called my attention to the problem as well as the solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Bionic: Fix Released Status in sane-backends package in Debian: Fix Released Bug description: To the sponsor: Please upload to bionic using the attached sane- backends_lp1728012_bionic.debdiff. [Impact] * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane dll looks for third party drivers. This configuration effectively broke backward compatibility for all existing third-party drivers. * A large swath of these third party drivers (most of them) are no longer supported by the OEM, so maintaining compatibility is important. * No open source replacement drivers are currently available, nor does the community have the resources to easily replace them. * This bug represents a substantial portion of the scanners in use. Scanners known to be affected include, but are not limited to: - Brother Scanners (all Brother scanners before brscan4) - DCP-145C - DCP-163C - DCP-165C - DCP-167C - DCP-185C - DCP-195C - DCP-197C - DCP-365CN - DCP-373CW - DCP-375CW - DCP-377CW - DCP-383C - DCP-385C - DCP-387C - DCP-395CN - DCP-585CW - DCP-6690CW - DCP-7030 - DCP-7040 - DCP-7045N - DCP-8070D - DCP-8080DN - DCP-8085DN - DCP-9010CN - DCP-9040CN - DCP-9042CDN - DCP-9045CDN - DCP-J125 - DCP-J315W - DCP-J515W - DCP-J715W - MFC-250C - MFC-255CW - MFC-257CW - MFC-290C - MFC-295CN - MFC-297C - MFC-490CW - MFC-495CW - MFC-5490CN - MFC-5890CN - MFC-5895CW - MFC-6490CW - MFC-6890CDW - MFC-7320 - MFC-7340 - MFC-7345N - MFC-7440N - MFC-7450 - MFC-7840N - MFC-7840W - MFC-790CW - MFC-795CW - MFC-8370DN - MFC-8380DN - MFC-8480DN - MFC-8510DN - MFC-8680DN - MFC-8880DN - MFC-8890DW - MFC-9010CN - MFC-9120CN - MFC-9320CW - MFC-9440CN - MFC-9450CDN - MFC-9840CDW - MFC-990CW - MFC-J220 - MFC-J265W - MFC-J270W - MFC-J410 - MFC-J410W - MFC-J415W - MFC-J615W - MFC-J630W - Dell MFP Laser Printer 1135n - Epson Scanners - All scanners supported by the libsane-epk driver - All scanners supported by the iscan driver - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Epson Perfection V33 - Samsung M2070 - Xerox Workcentre 3225 * This was working in the 17.04 release. 18.04 is an LTS release, so backporting is warranted for the 18.04 release. [Test Case] * Following the standard installation procedures for any of the affected scanner drivers results in the driver files being installed to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux- gnu/sane. When xsane is run, the scanner is not found. * Install the libsane1, libsane-common and sane-utils packages from bionic-proposed and confirm that it now finds drivers in /usr/lib/sane. [Regression Potential] * The proposed change is based on an upstream commit, and the patch is functional and stable in both 19.04 and 19.10. Low regression risk. [Other Info] * Third party sane drivers in previous version of sane were located under /usr/lib/sane/, however, the current version of sane on Ubuntu only looks for 64 bit drivers under the /usr/lib/x86_64-linux-gnu/sane directory. /usr/lib64 and /usr/lib64/sane are other directories old drivers are known to install files to. * The addition of symlinks alone does not appear to fix this issue, though it may make the scanner detectable. Changes to udev rules are also needed to allow proper communications to the scanners. A selection of workarounds, including working (though not ideal) udev rules for a number of scanners has been posted to the sane troubleshooting guide: help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1835647] Re: Saned does not start: service is masked
That's good news. :) sane-backends was updated yesterday for 18.04 (bug #1728012). I didn't realize that that change applies to your problem description, but apparently it does (somehow). Closing this bug then. ** No longer affects: systemd (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1835647 Title: Saned does not start: service is masked Status in sane-backends package in Ubuntu: Fix Released Bug description: I have been running saned for a couple of years on both 16 and 18. Recently it has stopped working with the message that it is masked. I don't use the scanner all that often so I cannot say exactly when it stopped working, certainly in the last few weeks. root@T550:~# systemctl status saned.socket ● saned.socket - saned incoming socket Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: ena Active: active (listening) since Fri 2019-07-05 00:03:10 BST; 1min 46s ago Listen: 0.0.0.0:6566 (Stream) Accepted: 0; Connected: 0 Tasks: 0 (limit: 4915) CGroup: /system.slice/saned.socket Jul 05 00:03:10 T550 systemd[1]: Listening on saned incoming socket. root@T550:~# systemctl start saned Failed to start saned.service: Unit saned.service is masked. root@T550:~# service saned start Failed to start saned.service: Unit saned.service is masked. root@T550:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sane-utils 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 4 23:45:57 2019 InstallationDate: Installed on 2018-02-09 (510 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: sane-backends UpgradeStatus: Upgraded to bionic on 2018-09-12 (294 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835647/+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 1835647] Re: Saned does not start: service is masked
I have just ried this again and it is now working. No changes other than the normal updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1835647 Title: Saned does not start: service is masked Status in sane-backends package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have been running saned for a couple of years on both 16 and 18. Recently it has stopped working with the message that it is masked. I don't use the scanner all that often so I cannot say exactly when it stopped working, certainly in the last few weeks. root@T550:~# systemctl status saned.socket ● saned.socket - saned incoming socket Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: ena Active: active (listening) since Fri 2019-07-05 00:03:10 BST; 1min 46s ago Listen: 0.0.0.0:6566 (Stream) Accepted: 0; Connected: 0 Tasks: 0 (limit: 4915) CGroup: /system.slice/saned.socket Jul 05 00:03:10 T550 systemd[1]: Listening on saned incoming socket. root@T550:~# systemctl start saned Failed to start saned.service: Unit saned.service is masked. root@T550:~# service saned start Failed to start saned.service: Unit saned.service is masked. root@T550:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sane-utils 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 4 23:45:57 2019 InstallationDate: Installed on 2018-02-09 (510 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: sane-backends UpgradeStatus: Upgraded to bionic on 2018-09-12 (294 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835647/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.2 --- mesa (19.0.2-1ubuntu1.1~18.04.2) bionic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1836721) -- Timo Aaltonen Thu, 18 Jul 2019 18:44:14 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Released Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1836721] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Released Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1837233] Re: [bionic] Manual IPv6 routes are not set
Nevermind then, this is working well enough for a stable release.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Won't Fix
--
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/1837233
Title:
[bionic] Manual IPv6 routes are not set
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Won't Fix
Bug description:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
# ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
Restarting NetworkManager does not help, nor does rebooting.
DistroRelease: Ubuntu 18.04
Package: 1.10.6-2ubuntu1.1
Architecture: amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1837233/+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 1837233] Re: [bionic] Manual IPv6 routes are not set
I confirm that using a valid IP works better:
In the config:
route1=fe80:2::/60,fe80::99,42
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
fe80:2::/60 via fe80::99 proto static metric 42 pref medium
It's still missing the route to fe80:2:: itself, though.
--
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/1837233
Title:
[bionic] Manual IPv6 routes are not set
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Won't Fix
Bug description:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
# ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
Restarting NetworkManager does not help, nor does rebooting.
DistroRelease: Ubuntu 18.04
Package: 1.10.6-2ubuntu1.1
Architecture: amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1837233/+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 1837233] Re: [bionic] Manual IPv6 routes are not set
The journal says why:
NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure
to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No
route to host (113)
NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply
manual IPv6 configuration
Apparently later versions ignore non-reachable hosts and set the route
anyway?
** Description changed:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
# ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
Restarting NetworkManager does not help, nor does rebooting.
+
+ DistroRelease: Ubuntu 18.04
+ Package: 1.10.6-2ubuntu1.1
+ Architecture: amd64
--
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/1837233
Title:
[bionic] Manual IPv6 routes are not set
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Won't Fix
Bug description:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
# ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
[Desktop-packages] [Bug 1837233] [NEW] [bionic] Manual IPv6 routes are not set
Public bug reported:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42 }
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
# ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42 }
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
Restarting NetworkManager does not help, nor does rebooting.
DistroRelease: Ubuntu 18.04
Package: 1.10.6-2ubuntu1.1
Architecture: amd64
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
** Description changed:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
- ip -6 route show dev eth2
+ # ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
Restarting NetworkManager does not help, nor does rebooting.
--
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/1837233
Title:
[bionic] Manual IPv6 routes are not set
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
New
Bug description:
I have a system
[Desktop-packages] [Bug 1824507] Re: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE
Thanks for the report. Can you please run the following command in a terminal to attach additional information to the bug report? apport-collect 1824507 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1824507 Title: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE Status in firefox package in Ubuntu: New Bug description: Without unity-menubar.patch, aka. an official binary build of firefox wouldn't export its traditional menu to global menu plasmoid, nor the unity menu addon. The applied patch works fine on its purpose: to export the menu to a global retriever, whether the DE is. However, it fails to stay the browser consist when Mozilla introduced native client-side decoration (CSD) support on KDE. When we don't use global menu plasmoid but disable titlebar (enable CSD), the window stays slim, and the tab bar stay tightly on top of the window left to the window control icons, but when we add the global menu plasmoid, the window gives a blank area where there is the window control icons on top right, then the opened tab bar. IMHO, it should stay on top like there is no the menu holder plasmoid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+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 1818812] Re: glib: Fix named destinations
I wrote a comment on the upstream fixing commit asking if there are
other commits that are required to apply the fix on Poppler 0.62.0, no
answer yet, and I don't think upstream is interested in 0.62.0 any more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+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 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
I'm attaching a screenshot demonstrating my claim above, showing gnome- calculator as a snap on the left, and from the deb on the right. This is in a clean and up-to-date disco VM, with Adwaita as the default theme. Colours clearly aren't right with the snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+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 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
(and both are focused, of course) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+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 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
** Attachment added: "left: snap / right: deb" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+attachment/5278047/+files/gnome-calculator-left-snap-right-nonsnap-adwaita.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+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 1837160] Re: Syslog filled with millions of entries per hour with stack trace ending in clutter_actor_get_child_at_index and clutter_actor_get_n_children, called from anima
* Uninstalled all extensions * restarted * ran apport-collect. For some reason, the extensions show as enabled in the bug report. This is not the case. - K On 2019-07-18 10:27 p.m., Daniel van Vugt wrote: > Please run this command to send us more information about the machine: > > apport-collect 1837160 > > Please also be sure to uninstall all extensions, not just disable them. > > ** Summary changed: > > - Syslog Filled with Millions of Entries per Hour with Stack Trace Ending in > /org/gnome/shell/ui/animation.js and /org/gnome/gjs/modules/_legacy.js > + Syslog filled with millions of entries per hour with stack trace ending in > clutter_actor_get_child_at_index and clutter_actor_get_n_children, called > from animation.js:53/57/59 > > ** Changed in: gnome-shell (Ubuntu) >Importance: Undecided => High > > ** Tags added: bionic > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > -- 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/1837160 Title: Syslog filled with millions of entries per hour with stack trace ending in clutter_actor_get_child_at_index and clutter_actor_get_n_children, called from animation.js:53/57/59 Status in gnome-shell package in Ubuntu: Incomplete Bug description: [Sys Info] Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 [Description] I'm seeing several GB/day of syslog entries by org.gnome.Shell.desktop /gnome-shell, causing the / partition to eventually run out of space (which is how I found out about this). It is a repetition of the following block over and over again. [Reproduciblity] So far as I can tell, simply logging in to the GNOME desktop starts the logging sequence. Disabling shell extensions via Tweaks has no effect. [From /var/log/syslog -- N.B. disregard "trusty", I'm running bionic] Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR
[Desktop-packages] [Bug 1755232] Re: Xorg crashes when tapping Unity system tray icons
** Changed in: xorg-server (Ubuntu) Assignee: fallo7...@gmail.com (fallo78) => Timo Aaltonen (tjaalton) -- 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/1755232 Title: Xorg crashes when tapping Unity system tray icons Status in xorg-server package in Ubuntu: In Progress Bug description: This bug requires some prerequisites to reproduce: 0. Make sure you've got multitouch-enable display 1. Start Unity+xorg session 2. Verify that four-finger tap gesture works (shows unity app search tool) 3. Wait some time for this gesture to stop working - this is another bug, not necessarily xorg one, already known and thought to be connected with Google Chrome running. 4. Once it stops working, quickly tap all icons in the Unity system tray like you would be pretending to play a piano (tapping them individually or slowly does not cause any problems). 5. Xorg crashes immediately. This scenario is 100% reproducible on my setup. I recompiled xorg with debug info enabled and got this nice trace: [ 22705.385] (EE) [ 22705.385] (EE) Backtrace: [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f] [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) [0x7f382f64414f] [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f382f2880bb] [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) [0x7f382f289f5d] [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) [0x7f382f2d22bd] [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) [0x7f382f2d9f7a] [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) [0x7f382f2de0fe] [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) [0x7f382f2e044e] [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32] [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) [0x562a3698428f] [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) [0x562a3698ea8b] [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) [0x562a369bc371] [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) [0x562a3696e488] [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9] [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3] [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f382f2721c1] [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a] [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] Looks like FreeGrab tries to free pGrab for the second time (some multithreading issue?) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 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:Unity7:ubuntu Date: Mon Mar 12 17:03:34 2018 DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2017-09-01 (192 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HES2130Q ProcEnviron: LANGUAGE=pl_PL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 i915.enable_guc_submission=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to artful on 2018-02-11 (29 days ago) dmi.bios.date: 05/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET55W (1.30 ) dmi.board.asset.tag: Not Available
[Desktop-packages] [Bug 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
This doesn't appear to be chromium-specific, nor Yaru-specific. I initially thought that only Yaru was exhibiting an incorrect background color for the focused headerbar, but I am now seeing an incorrect color with the gnome-calculator snap when using Adwaita. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+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 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
Thanks Dmitry. I'm tentatively closing the bug for firefox. To anyone affected, feel free to re-open if you're not using the GNOME Flashback session. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in GNOME Flashback: Unknown Status in firefox package in Ubuntu: Invalid Status in gnome-flashback package in Ubuntu: New Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1836659/+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 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
$ echo $GTK_IM_MODULE ibus I don't know which session I use, I set this up a loong time ago and I have no idea how to find out. But yes, it looks like it's flashback: $ ps -ef|grep -i flash hajma 1742 1503 0 čec16 ? 00:00:00 /bin/sh /usr/lib/gnome-session/run-systemd-session gnome-session-flashback.target hajma 1910 1742 0 čec16 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch /usr/lib/gnome-session/run-systemd-session gnome-session-flashback.target hajma 2017 1742 0 čec16 ? 00:00:00 systemctl --user start --wait gnome-session-flashback.target hajma 2052 1721 0 čec16 ? 00:00:00 /usr/lib/gnome-session/gnome-session-binary --session=gnome-flashback-metacity --disable-acceleration-check hajma 2309 2052 0 čec16 ? 00:00:41 gnome-flashback hajma 3343 3228 0 16:59 pts/000:00:00 grep --color=auto -i flash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in GNOME Flashback: Unknown Status in firefox package in Ubuntu: Invalid Status in gnome-flashback package in Ubuntu: New Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1836659/+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 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
Closing then. Thanks. ** Changed in: network-manager (Ubuntu) Status: New => Won't Fix -- 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/1824425 Title: network-manager dies in package postinst on cosmic->disco upgrade Status in network-manager package in Ubuntu: Won't Fix Bug description: I just did a cosmic->disco upgrade and as soon as the network-manager package was configured, my network dropped. Setting up network-manager (1.12.4-1ubuntu1) ... As soon as this package was configured, the NetworkManager service died, the NM applet disappeared from my desktop, and my network dropped. The NetworkManager service eventually succeeded in restarting, but it took 12 minutes. journalctl output looks like: Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager... Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2262] caught SIGTERM, shutting down normally. Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2277] device (wlan2): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2392] device (wlan2): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3055] dhcp4 (wlan2): canceled DHCP transaction, DHCP client pid 2596 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3056] dhcp4 (wlan2): state changed bound -> done Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4210] device (virbr0-nic): released from master device virbr0 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4430] exiting (success) Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded. Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager. Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager... Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager. Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager... Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2. Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager. Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager... Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3. Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager. Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager... Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4. Apr 11 13:38:29 virgil systemd[1]: Stopped Network Manager. Apr 11 13:38:29 virgil systemd[1]: Starting Network Manager... Apr 11 13:40:00 virgil systemd[1]:
[Desktop-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
excellent, thanks for confirming! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Committed Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
If mine is the only report of this problem, then yes, it should probably be closed wontfix. ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- 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/1824425 Title: network-manager dies in package postinst on cosmic->disco upgrade Status in network-manager package in Ubuntu: New Bug description: I just did a cosmic->disco upgrade and as soon as the network-manager package was configured, my network dropped. Setting up network-manager (1.12.4-1ubuntu1) ... As soon as this package was configured, the NetworkManager service died, the NM applet disappeared from my desktop, and my network dropped. The NetworkManager service eventually succeeded in restarting, but it took 12 minutes. journalctl output looks like: Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager... Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2262] caught SIGTERM, shutting down normally. Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2277] device (wlan2): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2392] device (wlan2): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3055] dhcp4 (wlan2): canceled DHCP transaction, DHCP client pid 2596 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3056] dhcp4 (wlan2): state changed bound -> done Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4210] device (virbr0-nic): released from master device virbr0 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4430] exiting (success) Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded. Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager. Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager... Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager. Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager... Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2. Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager. Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager... Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3. Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager. Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager... Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4. Apr 11 13:38:29 virgil systemd[1]: Stopped Network Manager. Apr 11 13:38:29 virgil systemd[1]: Starting
[Desktop-packages] [Bug 1828102] Re: Regression in ModemManager
Hello yparitcher, or anyone else affected, Accepted modemmanager into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.10.0-1ubuntu0.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: Fix Committed Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
This is a bug in gnome-flashback, not in Firefox. I am working on a fix. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-flashback/issues #16 https://gitlab.gnome.org/GNOME/gnome-flashback/issues/16 ** Also affects: gnome-flashback via https://gitlab.gnome.org/GNOME/gnome-flashback/issues/16 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in GNOME Flashback: Unknown Status in firefox package in Ubuntu: Incomplete Status in gnome-flashback package in Ubuntu: New Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1836659/+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 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
I tested in an XFCE/XUbuntu session, and the focused headerbar color was correct, so there's something specific to the Ubuntu/GNOME session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+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 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
vorlon, as it only happens during the Cosmic -> Disco upgrade and Cosmic is EOL, should we close this then? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1824425 Title: network-manager dies in package postinst on cosmic->disco upgrade Status in network-manager package in Ubuntu: Incomplete Bug description: I just did a cosmic->disco upgrade and as soon as the network-manager package was configured, my network dropped. Setting up network-manager (1.12.4-1ubuntu1) ... As soon as this package was configured, the NetworkManager service died, the NM applet disappeared from my desktop, and my network dropped. The NetworkManager service eventually succeeded in restarting, but it took 12 minutes. journalctl output looks like: Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager... Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2262] caught SIGTERM, shutting down normally. Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2277] device (wlan2): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2392] device (wlan2): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3055] dhcp4 (wlan2): canceled DHCP transaction, DHCP client pid 2596 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3056] dhcp4 (wlan2): state changed bound -> done Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4210] device (virbr0-nic): released from master device virbr0 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4430] exiting (success) Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded. Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager. Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager... Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager. Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager... Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2. Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager. Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager... Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3. Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager. Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager... Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4. Apr 11 13:38:29 virgil systemd[1]: Stopped Network Manager. Apr 11 13:38:29 virgil
[Desktop-packages] [Bug 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
I tested a few more things, unsuccessfully:
- I modified the Yaru theme css in gtk-common-themes to remove the
".titlebar:not(headerbar)," selector, keeping only the "headerbar"
selector for header bars, but no difference
- I modified the custom selector in gtk_ui.cc to be just "#headerbar"
instead of "#headerbar.header-bar.titlebar", but no difference
- I instrumented AppendCssNodeToStyleContext() in gtk_util.cc to print
out the actual selectors being queried at the end of the function, just
before the return statement, and they looked correct ("window⤶headerbar"
and "window⤶headerbar:backdrop")
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1800260
Title:
[snap] with CSD and Yaru, background color of the header bar is
incorrect
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Channel:Stable
Version:70.0.3538.67
Updated:10/19/2018
License:Free
Developer: Canonical
Source: Snap Store
Installed Size: 148.2 MB
Settings -> Appearance: "Use system title bar and borders" was turned
off. Close, minimize, maximize buttons became oval (more of stretched
down) instead of circle. Turned back it on, buttons went back to
normal shape (circle). It's a repeatable action.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+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 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
No. This only happened the one time during the cosmic to disco upgrade. ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- 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/1824425 Title: network-manager dies in package postinst on cosmic->disco upgrade Status in network-manager package in Ubuntu: New Bug description: I just did a cosmic->disco upgrade and as soon as the network-manager package was configured, my network dropped. Setting up network-manager (1.12.4-1ubuntu1) ... As soon as this package was configured, the NetworkManager service died, the NM applet disappeared from my desktop, and my network dropped. The NetworkManager service eventually succeeded in restarting, but it took 12 minutes. journalctl output looks like: Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager... Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2262] caught SIGTERM, shutting down normally. Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2277] device (wlan2): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2392] device (wlan2): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3055] dhcp4 (wlan2): canceled DHCP transaction, DHCP client pid 2596 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3056] dhcp4 (wlan2): state changed bound -> done Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4210] device (virbr0-nic): released from master device virbr0 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4430] exiting (success) Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded. Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager. Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager... Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager. Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager... Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2. Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager. Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager... Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3. Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager. Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager... Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4. Apr 11 13:38:29 virgil systemd[1]: Stopped Network Manager. Apr 11 13:38:29 virgil systemd[1]: Starting Network Manager... Apr
[Desktop-packages] [Bug 1800968] Re: nm-applet only show current wifi connection
Please provide a log of network-manager in debug mode, following the instructions on https://wiki.ubuntu.com/DebuggingNetworkManager ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1800968 Title: nm-applet only show current wifi connection Status in network-manager package in Ubuntu: Incomplete Bug description: This doesn't happen all the time, but it happens quite frequently, that I'm connected to one wifi connection and there are others in the area, but when I click on nm-applet, it only displays the wifi that I'm connected to, but not the other available networks. I'm currently running Ubuntu 18.04.1 LTS, network-manager-gnome version 1.8.10-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800968/+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 1793763] Re: NetworkManager interaction with dhclient triggers IP conflict detection at dhcp server, causes ip address changing every day
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
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/1793763
Title:
NetworkManager interaction with dhclient triggers IP conflict
detection at dhcp server, causes ip address changing every day
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
After installing my laptop with Ubuntu and using the wired network
cable with default NetworkManager service to handle the connection, I
ran into the issue that my local ipv4 address changes every day, while
this never happens for other devices in the network. This is
undesirable to me, because it exhausts the local networks IP address
pool and the change of IP is inconvenient when working with services
like SSH, samba, etc. Added to this, I sometimes experience random
network outages especially when waking up from suspend.
After some investigation, I found the following to happen:
- The exact time the DHCP server provides with a new IP address that
different from previous one, is when I wake up my laptop after about 12 hours
of being suspended, typicaly at the start of the new working day.
- When I lookup the logs of the DHCP server at the time of the laptop getting
its new IP address, I find the following:
Sep 21 14:36 router dhcpd: DHCPDISCOVER from 68:f7:28:3f:a0:11 via eth2
Sep 21 14:36 router dhcpd: Abandoning IP address 192.168.1.137: pinged before
offer
Sep 21 14:36 router dhcpd: DHCPDISCOVER from 68:f7:28:3f:a0:11 via eth2
Sep 21 14:36 router dhcpd: DHCPOFFER on 192.168.1.139 to 68:f7:28:3f:a0:11
(kubuntu1804) via eth2
It looks like the DHCP server is detecting a possible IP conflict
because it can ping .137 while a DHCPDISCOVER for the hardware address
matches the lease with the same IP address it is about to offer. To
prevent problems, the DHCP server finds a new free IP address .139 and
offers this one instead.
Why is this triggered by the ubuntu client? When I look at the client
logs at the same time, I see following to happen:
Sep 21 00:27 kubuntu1804 systemd-sleep[21703]: Suspending system...
Sep 21 14:36 kubuntu1804 kernel: [14934.160293] Restarting tasks ... done.
Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.1923]
device (enp0s25): carrier: link connected
Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.1925]
device (enp0s25): DHCPv4 lease renewal requested
Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2246]
dhcp4 (enp0s25): canceled DHCP transaction, DHCP client pid 18900
Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2247]
dhcp4 (enp0s25): state changed bound -> done
Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2257]
dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2292]
dhcp4 (enp0s25): dhclient started with pid 21860
Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPDISCOVER on enp0s25 to
255.255.255.255 port 67 interval 3 (xid=0x71ed8c51)
Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPDISCOVER on enp0s25 to
255.255.255.255 port 67 interval 5 (xid=0x71ed8c51)
Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPREQUEST of 192.168.1.139 on
enp0s25 to 255.255.255.255 port 67 (xid=0x518ced71)
Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPOFFER of 192.168.1.139 from
192.168.1.1
Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPACK of 192.168.1.139 from
192.168.1.1
So if I understand it well, the summary of what happens here is:
1) Client wakes up after being suspended for about 14h
2) Existing running dhclient fired from NetworkManager discovers the lease
has expired and requesting a renewal
3) Shortly after that this dhclient is killed by NetworkManager, probably
because NetworkManager has detected a "link connected" event, caused by the
suspend (the cable has not been removed physicaly). The old dhclient is killed
during the lease renewal and probably long before the renewal procedure could
be proparly handled
4) A new dhclient is fired by NetworkManager, performing a whole new DHCP
request, getting a new IP address from the server
I expect the events 2 and 3 happening simultaneously are causing
trouble. Probably the old IP .137 is already set to the interface
while handling the lease renewal and then a new dhclient is started
performing again a new DHCPREQUEST, confusing the dhcp server.
When I look at the ISC dhclient, it is running the hook script "/sbin
/dhclient-script" when a lease is expired or the dhclient is
terminated. See line 347 of this file:
EXPIRE|FAIL|RELEASE|STOP)
if [ -n "$old_ip_address" ]; then
# flush leased IP
ip -4 addr flush dev ${interface} label ${interface}
fi
I see when dhclient is
[Desktop-packages] [Bug 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
Pavel and Ross, can you confirm that you are seeing this with the GNOME Flashback session, not the default Ubuntu session? ** Also affects: gnome-flashback (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in firefox package in Ubuntu: Incomplete Status in gnome-flashback package in Ubuntu: New Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836659/+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 1803236] Re: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS
Please follow the instructions of Thomas Haller in your upstream bug report. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1803236 Title: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS Status in network-manager package in Ubuntu: Incomplete Bug description: During the do-release-upgrade from 16.04 to 18.04, if the user chooses to preserve the old NetworkManager.conf having "dns=dnsmasq", it does not preserve dnsmasq as the local resolver. It results in a broken DNS configuration, with /etc/resolv.conf set to 127.0.0.53 but NetworkManager set to dnsmasq. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1803236/+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 1814473] Re: latest systemd, network-manager, kernel updates killed networking
As manual setup of networking also does not work it looks more like a kernel problem, moving ... ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1814473 Title: latest systemd, network-manager, kernel updates killed networking Status in linux package in Ubuntu: New Bug description: Latest network-manager, systemd, kernel-updates killed ethernet networking. It is impossible to have an address assigned. I can make sure hardware is ok, by booting into SystemRescueCD. Ethernet immediately is up and working. As soon as I boot into Ubuntu 18.10 networking with ethernet stops working at all. Even trying to set it up manually using "ip" or "ifconfig" does not help. Modules seem loaded, but not functional. Unsure if it is kernel, systemd, or network-manager related. From network-manager I can activate WLAN. Thus in my humble opinion the driver or firmware was killed by installing the latest updates. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 3 21:52:57 2019 IfupdownConfig: # Local loopback auto lo iface lo inet loopback InstallationDate: Installed on 2011-10-19 (2664 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to cosmic on 2018-11-03 (92 days ago) mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814473/+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 1818666] Re: no network(with cable)
Please report this bug to Trisquel. Thanks. ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/1818666 Title: no network(with cable) Status in network-manager package in Ubuntu: Invalid Bug description: Description: Trisquel GNU/Linux 8.0, Flidas Release: 8.0 --- network-manager: Installiert: 1.2.6-0ubuntu0.16.04.3 Installationskandidat: 1.2.6-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.6-0ubuntu0.16.04.3 500 500 https://archive.trisquel.info/trisquel flidas-security/main amd64 Packages 500 https://archive.trisquel.info/trisquel flidas-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 https://archive.trisquel.info/trisquel flidas/main amd64 Packages --- after starting the system there is no eth(0?) network available, after gdm-login it take some time, starting the network-managager leads to a freeze of the network-manager while rebooting the system it take a lot more time and there are also some error messages. i think they are included in the "Extra debug information". sorry i'm not sure, this is my first bug-report. a have this problem since i use trisquel, this problem doesnt exist with ubuntu, i think sometimes everything works fine. :) if this bug-report is not written correct, please contact me if possible. thanks ProblemType: Bug DistroRelease: Trisquel 8.0 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168+8.0trisquel2-generic 4.4.167-gnu Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 5 14:38:31 2019 InstallationDate: Installed on 2018-12-27 (68 days ago) InstallationMedia: Trisquel 8.0 "flidas" - Release amd64 (20180417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818666/+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 1832124] Re: Right-click file on desktop > Move to Trash frequently crashes gnome-shell
I can reliably reproduce the crash about half of the time with the following steps: - create a symlink to a folder on the desktop - right-click on that symlink and choose the option to send to trash Corresponding crash report: https://errors.ubuntu.com/oops/437cbc68-aa03-11e9-a2e9-fa163e6cac46 Relevant logs from journalctl: juil. 19 10:51:36 bribon gnome-shell[4142]: Object St.Bin (0x55e5ba9becd0), has been already deallocated — impossible to get any property from it. This might be c juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: == Stack trace for context 0x55e5b25cd280 == juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #0 7ffcea594890 b resource:///org/gnome/shell/ui/boxpointer.js:264 (7fc1cd112940 @ 611) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: == Stack trace for context 0x55e5b25cd280 == juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #0 7ffcea594600 b resource:///org/gnome/shell/ui/layout.js:946 (7fc1cd100040 @ 34) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #1 7ffcea5947c0 b resource:///org/gnome/shell/ui/boxpointer.js:476 (7fc1cd112b80 @ 193) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #2 7ffcea594890 b resource:///org/gnome/shell/ui/boxpointer.js:265 (7fc1cd112940 @ 634) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: == Stack trace for context 0x55e5b25cd280 == juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #0 7ffcea594600 b resource:///org/gnome/shell/ui/layout.js:947 (7fc1cd100040 @ 243) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #1 7ffcea5947c0 b resource:///org/gnome/shell/ui/boxpointer.js:476 (7fc1cd112b80 @ 193) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #2 7ffcea594890 b resource:///org/gnome/shell/ui/boxpointer.js:265 (7fc1cd112940 @ 634) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: == Stack trace for context 0x55e5b25cd280 == juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #0 7ffcea5947c0 b resource:///org/gnome/shell/ui/boxpointer.js:478 (7fc1cd112b80 @ 221) juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: #1 7ffcea594890 b resource:///org/gnome/shell/ui/boxpointer.js:265 (7fc1cd112940 @ 634) juil. 19 10:51:36 bribon audit[4142]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=5 pid=4142 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=5 res=1 juil. 19 10:51:36 bribon gnome-shell[4142]: Object St.Bin (0x55e5ba9becd0), has been already deallocated — impossible to access it. This might be caused by the ob juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: GNOME Shell crashed with signal 5 juil. 19 10:51:36 bribon org.gnome.Shell.desktop[4142]: == Stack trace for context 0x55e5b25cd280 == juil. 19 10:51:36 bribon gnome-shell[4142]: _clutter_actor_fully_transform_vertices: assertion 'CLUTTER_IS_ACTOR (self)' failed juil. 19 10:51:36 bribon gnome-shell[4142]: Object St.Bin (0x55e5ba9becd0), has been already deallocated — impossible to access it. This might be caused by the ob juil. 19 10:51:36 bribon gnome-shell[4142]: clutter_actor_get_transformed_size: assertion 'CLUTTER_IS_ACTOR (self)' failed juil. 19 10:51:36 bribon gnome-shell[4142]: Object St.Bin (0x55e5ba9becd0), has been already deallocated — impossible to access it. This might be caused by the ob juil. 19 10:51:36 bribon gnome-shell[4142]: Function allocate terminated with uncatchable exception ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic
[Desktop-packages] [Bug 1832124] Re: Right-click file on desktop > Move to Trash frequently crashes gnome-shell
I have managed to reproduce in a clean and fully up-to-date disco VM, but not in an eoan VM, which suggests the problem was fixed in eoan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed
*** This bug is a duplicate of bug 1422004 *** https://bugs.launchpad.net/bugs/1422004 BUG still existing also for model HP Color LaserJet Pro MFP M281fdw Printing works but scanning is not possible because of failure when installing plugin! No solution actually seems to be available! Developers please help! SystemInfo: System:Host: papi-mint Kernel: 4.15.0-54-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.0.10 wm: muffin dm: LightDM Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic TerminalLog: papi@papi-mint:~/Downloads$ hp-plugin HP Linux Imaging and Printing System (ver. 3.19.6) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.19.6) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir /home/papi/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.19.6 Plugin Self Extracting Archive.. HP Linux Imaging and Printing System (ver. 3.19.6) Plugin Installer ver. 3.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Plug-in version: 3.19.6 Installed HPLIP version: 3.19.6 Number of files to install: 64 Plugin installation failed error: Python gobject/dbus may be not installed error: Plug-in install failed. Cheers /Martin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1430561 Title: hp-plugin crashes with error: Python gobject/dbus may be not installed Status in HPLIP: Confirmed Status in One Hundred Papercuts: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: When trying to configure an HP LaserJet P1102w, when running hp-plugin I get errors and can not proceed: nessita@miro:~$ hp-plugin error: Unable to locate models.dat file HP Linux Imaging and Printing System (ver. 3.15.2) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for network connection... Downloading plug-in from: Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9 Creating directory plugin_tmp Verifying archive integrity... All good. Uncompressing HPLIP 3.15.2 Plugin Self Extracting Archive... Error importing HPLIP modules. Is HPLIP installed? error: Python gobject/dbus may be not installed error: Plug-in install failed. Done. nessita@miro:~$ ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hplip 3.15.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 19:23:41 2015 InstallationDate: Installed on 2014-11-30 (100 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet MachineType: LENOVO 3249CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET61WW (1.31 ) dmi.board.name: 3249CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To
[Desktop-packages] [Bug 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
Does this happen repeatedly since your update, for example at every boot? If so, could you provide a log of network-manager in debugging mode, as described on https://wiki.ubuntu.com/DebuggingNetworkManager ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1824425 Title: network-manager dies in package postinst on cosmic->disco upgrade Status in network-manager package in Ubuntu: Incomplete Bug description: I just did a cosmic->disco upgrade and as soon as the network-manager package was configured, my network dropped. Setting up network-manager (1.12.4-1ubuntu1) ... As soon as this package was configured, the NetworkManager service died, the NM applet disappeared from my desktop, and my network dropped. The NetworkManager service eventually succeeded in restarting, but it took 12 minutes. journalctl output looks like: Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager... Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2262] caught SIGTERM, shutting down normally. Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2277] device (wlan2): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2392] device (wlan2): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3055] dhcp4 (wlan2): canceled DHCP transaction, DHCP client pid 2596 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3056] dhcp4 (wlan2): state changed bound -> done Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4210] device (virbr0-nic): released from master device virbr0 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4430] exiting (success) Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded. Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager. Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager... Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager. Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager... Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2. Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager. Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager... Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3. Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager. Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager... Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart
[Desktop-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
I have just updated mesa from bionic-proposed and now everything is fine on i386 Ubuntu 18.04: ~# apt-cache policy libgl1-mesa-glx libgl1-mesa-glx: Встановлено: 19.0.2-1ubuntu1.1~18.04.2 Кандидат:19.0.2-1ubuntu1.1~18.04.2 Таблиця версій: *** 19.0.2-1ubuntu1.1~18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages 100 /var/lib/dpkg/status I have also tried different kernels with bad mesa 19.0.2-1ubuntu1.1~18.04.1 from bionic-updates: linux-generic (4.15.0-54-generic) - problem exists linux-generic-hwe-18.04 (4.18.0-25-generic) - problem exists linux-generic-hwe-18.04-edge (5.0.0-20-generic) - everything is fine With mesa 19.0.2-1ubuntu1.1~18.04.1 from bionic-proposed everything is fine on all these kernels ** Tags removed: verification-needed ** Tags added: verification-done-bionic ** Tags removed: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Committed Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1021375] Re: Nautilus says the USB stick is read only when it is not
Ubuntu 19.04 (disco) will switch to read-only when a automatically mounted VFAT filesystem with errors is detected. You have to umount the filesystem and then run "sudo fsck.vfat /dev/sd" multiple times, until fsck.vfat do no more ask to correct the new errors detected in the filesystem. Maybe fsck.vfat should be modified so that after the question "Perform changes ? (y/n) y" it asks for "Re-check filesystem ? (y/n)" because its behaviour is confusing... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1021375 Title: Nautilus says the USB stick is read only when it is not Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in thunar package in Ubuntu: Confirmed Bug description: First time I use an USB drive since I updated to 12.04 and I found a really annoying bug on Nautilus. Nautilus claims that the destination drive is read-only when in fact it is not. How to reproduce: 1. Connect a USB stick drive to your competer. 2. The USB will appear in the desktop. 3. Open two Nautilus windows one in your home folder, other in the USB stick drive. 4. Select any file from your home folder (small enough to fit the free space in the USB drive) 5. Drag the file and drop it in the USB drive window. -- Nautilus will say that it cannot copy the file because the destination is read ony -- If you try the copy the same file with the terminal you will see that the file is copied without problem, other programs like gedit or LibreOffice can write in the usb stick drive just fine. It is not a problem with the USB stick, as shown here: [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd [ 6232.426378] scsi8 : usb-storage 2-1:1.0 [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP PQ: 0 ANSI: 0 CCS [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 GB/1.86 GiB) [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.210138] sdb: sdb1 [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk The permisions on the removable drive are set correctly: sergio@shana:/media$ ls -lah total 12K drwxr-xr-x 3 root root 4,0K jul 5 10:20 . drwxr-xr-x 23 root root 4,0K jul 3 11:01 .. drwx-- 5 sergio sergio 4,0K dic 31 1969 DESIGNPLUS There is enough free space in the drive: sergio@shana:/media/DESIGNPLUS$ df -h S.ficheros Tamaño Usado Disp Uso% Montado en /dev/sda2 50G 5,5G 42G 12% / udev 1,5G 4,0K 1,5G 1% /dev tmpfs579M 872K 579M 1% /run none 5,0M 0 5,0M 0% /run/lock none 1,5G 1,1M 1,5G 1% /run/shm /dev/sda1497M 113M 360M 24% /boot /dev/sda5245G 111G 122G 48% /home /dev/sdb11,9G 681M 1,2G 36% /media/DESIGNPLUS A file can be copied to the USB stick using the cp command for example. sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS sergio@shana:~/Trash$ cd /media/DESIGNPLUS sergio@shana:/media/DESIGNPLUS$ ls -lah total 204K drwx-- 5 sergio sergio 4,0K jul 5 10:38 . drwxr-xr-x 3 root root 4,0K jul 5 10:20 .. -rw-r--r-- 1 sergio sergio 117K jul 5 10:14 ._Screen Shot 2012-06-30 at 8.50.37 AM.png -rw-r--r-- 1 sergio sergio 55K jun 30 08:51 Screen Shot 2012-06-30 at 8.50.37 AM.png drwx-- 4 sergio sergio 4,0K jul 5 10:05 .Spotlight-V100 drwx-- 2 sergio sergio 4,0K jul 5 10:05 .Trashes -rw-r--r-- 1 sergio sergio 4,0K jul 5 10:05 ._.Trashes -rw-r--r-- 1 sergio sergio 73 jul 5 10:38 wireless.txt But nautilus just dennies to copy the file claming that the destination is read only, when it is not. I tested it with two different USB sticks in two different computers running Ubuntu 12.04 and the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+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 1817537] Please test proposed package
Hello Lars, or anyone else affected, Accepted libsoup2.4 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libsoup2.4/2.62.1-1ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop
Did I miss something? -- 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/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Won't Fix Bug description: [ Description ] Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. [ Test case ] Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour (how it worked in cosmic & before): Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. [ Regression potential ] World clocks are not shown for some places To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827953/+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 1755232] Re: Xorg crashes when tapping Unity system tray icons
** Changed in: xorg-server (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => fallo7...@gmail.com (fallo78) -- 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/1755232 Title: Xorg crashes when tapping Unity system tray icons Status in xorg-server package in Ubuntu: In Progress Bug description: This bug requires some prerequisites to reproduce: 0. Make sure you've got multitouch-enable display 1. Start Unity+xorg session 2. Verify that four-finger tap gesture works (shows unity app search tool) 3. Wait some time for this gesture to stop working - this is another bug, not necessarily xorg one, already known and thought to be connected with Google Chrome running. 4. Once it stops working, quickly tap all icons in the Unity system tray like you would be pretending to play a piano (tapping them individually or slowly does not cause any problems). 5. Xorg crashes immediately. This scenario is 100% reproducible on my setup. I recompiled xorg with debug info enabled and got this nice trace: [ 22705.385] (EE) [ 22705.385] (EE) Backtrace: [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f] [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) [0x7f382f64414f] [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f382f2880bb] [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) [0x7f382f289f5d] [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) [0x7f382f2d22bd] [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) [0x7f382f2d9f7a] [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) [0x7f382f2de0fe] [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) [0x7f382f2e044e] [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32] [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) [0x562a3698428f] [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) [0x562a3698ea8b] [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) [0x562a369bc371] [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) [0x562a3696e488] [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9] [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3] [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f382f2721c1] [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a] [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] Looks like FreeGrab tries to free pGrab for the second time (some multithreading issue?) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 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:Unity7:ubuntu Date: Mon Mar 12 17:03:34 2018 DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2017-09-01 (192 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HES2130Q ProcEnviron: LANGUAGE=pl_PL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 i915.enable_guc_submission=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to artful on 2018-02-11 (29 days ago) dmi.bios.date: 05/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET55W (1.30 ) dmi.board.asset.tag: Not Available
[Desktop-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: ubuntu Status: New => Incomplete -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1828313] Re: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04.
Could you do the logging like in your comment #4 of your question again but in debug mode, as described on https://wiki.ubuntu.com/DebuggingNetworkManager ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1828313 Title: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04. Status in network-manager package in Ubuntu: Incomplete Bug description: pls see my post here https://answers.launchpad.net/ubuntu/+question/680506 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1828313/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
btw, would be helpful to see if installing linux-image-hwe-edge together with the bad mesa would still work.. so, ppa-purge the ppa, then install the edge kernel, reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Committed Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1828134] Re: Wifi not working after suspend/resume cycle
Reported upstream as https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #213 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213 Importance: Unknown Status: Unknown -- 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/1828134 Title: Wifi not working after suspend/resume cycle Status in NetworkManager: Unknown Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1828134/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
Hello Roman, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1.1~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Committed Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1836756] Re: Xorg freeze
** Package changed: ubuntu => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- 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/1836756 Title: Xorg freeze Status in xorg-server package in Ubuntu: New Bug description: i have to hard reboot the system for ubuntu froze,so please fix the bug . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 16 19:42:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (105 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 096C11405F00050660180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836756/+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 1836756] [NEW] Xorg freeze
You have been subscribed to a public bug: i have to hard reboot the system for ubuntu froze,so please fix the bug . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 16 19:42:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (105 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 096C11405F00050660180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1836756 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. -- 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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+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
