[Desktop-packages] [Bug 2067613] Re: CVE-2024-5290 : Fix loading of arbitrary shared objects
** Also affects: wpa (Debian) Importance: Undecided Status: New ** Changed in: wpa (Debian) Importance: Undecided => High ** Changed in: wpa (Debian) Status: New => Fix Released ** Changed in: wpa (Debian) Assignee: (unassigned) => Andrej Shadura (andrew.sh) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2067613 Title: CVE-2024-5290 : Fix loading of arbitrary shared objects Status in wpa package in Ubuntu: Fix Released Status in wpa package in Debian: Fix Released Bug description: Hello team We received a vulnerability report a while back - that lets users load arbitrary shared object files in the context of the wpa_supplicant process running as root in affected Ubuntu systems. TLDR : Upstream released a fix : https://w1.fi/cgit/hostap/commit/?id=c84388ee4c66bcd310db57489eac4a75fc600747 that includes a compile time config for allow-listing a set of shared objects. Details here : `wpa_supplicant` is a binary package of source `wpa` ```sh $ umt search wpa Running search command. Ubuntu packages: Release Version Pocket Component trusty 2.1-0ubuntu1.7 security main trusty/esm 2.1-0ubuntu1.7+esm4 security main xenial 2.4-0ubuntu6.8 security main bionic 2:2.6-15ubuntu2.8 security main focal 2:2.9-1ubuntu4.3security main jammy 2:2.10-6ubuntu2 updates main lunar 2:2.10-12release main mantic 2:2.10-15release main noble 2:2.10-21build4 release main Other packages: Release Version Pocket Component bookworm 2:2.10-12release main bullseye 2:2.9.0-21 release main buster 2:2.7+git20190128+0c1e29f-6+deb10u4 updates main testing 2:2.10-21.1 release main unstable 2:2.10-21.1 release main ``` Upstream - https://w1.fi/cgit upstream examples point to config that lets all users in group `wheel` access the frontend. debian and ubuntu use group membership to control access to D-Bus So in `debian/patches/02_dbus_group_policy.patch` ``` diff --git a/wpa_supplicant/dbus/dbus-wpa_supplicant.conf b/wpa_supplicant/dbus/dbus-wpa_supplicant.conf index e81b495..413c049 100644 --- a/wpa_supplicant/dbus/dbus-wpa_supplicant.conf +++ b/wpa_supplicant/dbus/dbus-wpa_supplicant.conf @@ -9,6 +9,11 @@ + + + + + ``` to allow `netdev` users access to the wpa_supplicant which gets started as a service ``` diff --git a/wpa_supplicant/systemd/wpa_supplicant.service.in b/wpa_supplicant/systemd/wpa_supplicant.service.in index 18cbc11..f02bc15 100644 --- a/wpa_supplicant/systemd/wpa_supplicant.service.in +++ b/wpa_supplicant/systemd/wpa_supplicant.service.in @@ -8,8 +8,11 @@ IgnoreOnIsolate=true [Service] Type=dbus BusName=fi.w1.wpa_supplicant1 -ExecStart=@BINDIR@/wpa_supplicant -u -s -O /run/wpa_supplicant +ExecStart=@BINDIR@/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev" ExecReload=/bin/kill -HUP $MAINPID +Group=netdev +RuntimeDirectory=wpa_supplicant +RuntimeDirectoryMode=0750 [Install] WantedBy=multi-user.target ``` If a user is able to escalate to `netdev` - they will be able to interact with the dbus interface. One of the interface `fi.w1.wpa_supplicant1` lets the user create a network interface via `CreateInterface` - See [`wpas_dbus_handler_create_interface`](http://w1.fi/wpa_supplicant/devel/dbus__new__handlers_8h.html#a4c504285e9504dc5508f35646278f867) `ConfigFile` has configurations for a network interface * for loading an opensc engine with `opensc_engine_path`which is a path to a shared object. See [`opensc_engine_path`](https://w1.fi/wpa_supplicant/devel/structwpa__config.html#a791fade4701a30852dbb2b25866ba359) * for loading a PKCS#11 engine with `pkcs11_engine_path` which is a path to a shared object. See [`pkcs11_engine_path`](https://w1.fi/wpa_supplicant/devel/structwpa__config.html#adf38e52ccfe1b621ef5a18b78b1c3a9e) Both these paths don't check for paths - any arbitrary location - leading to arbitrary code execution. Overall any user within the group `netdev` would be able to load arbitrary shared objects - in the context of a process running as root - granting privilege escalation to `root` The process that loads these
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
** Bug watch added: Debian Bug tracker #1010603 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010603 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010603 Importance: Unknown Status: Unknown ** Changed in: wpa (Debian) Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Unknown Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
** Also affects: wpa (Debian) Importance: Undecided Status: New ** Changed in: wpa (Debian) Importance: Undecided => Wishlist ** Changed in: wpa (Debian) Status: New => Fix Released ** Changed in: wpa (Debian) Assignee: (unassigned) => Andrej Shadura (andrew.sh) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Status in wpa package in Debian: Fix Released Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1893563] Re: netplan: can't login to ap mode with psk
Right, my apologies, I was too quick to be angry: I only checked the patch proposed here but not the actual one committed — and apparently I haven’t read the discussion to the end. Having checked the actual package, I see it is in fact a patch from the upstream Git. Still, it’d be great if you could at least notify me, and it would be much better if we could first push such changes into Debian first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1893563] Re: netplan: can't login to ap mode with psk
I’ve just verified and in fact not only this hasn’t been submitted upstream, but the upstream has shipped an alternative implementation of this by Beniamino Galvani (@bengal). I’d really appreciate if Ubuntu didn’t add non-trivial patches without discussion with the upstream and me as the Debian maintainer for this package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1893563] Re: netplan: can't login to ap mode with psk
@seb128, @mhodson, @shemgp, has this patch been submitted to the upstream? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Bug watch added: Debian Bug tracker #954457 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954457 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954457 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Status in wpa package in Debian: Unknown Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
@racb, it’s been committed to the upstream package in Debian; just a sync is needed. ** Package changed: wpasupplicant (Ubuntu) => wpa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
Speaking of which, it would be great if this patch was dropped: - debian/patches/session-ticket.patch: disable the TLS Session Ticket extension to fix auth with 802.1x PEAP on some hardware. This has been superseded by upstream changes a couple of releases ago and is no longer needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1183765] Re: During typography thumbnailing, the Font Viewer window becomes very unresponsive
https://gitlab.gnome.org/GNOME/gnome-font-viewer/issues/2 ** Changed in: gnome-font-viewer Importance: Medium => Undecided ** Changed in: gnome-font-viewer Remote watch: GNOME Bug Tracker #701005 => None ** Bug watch added: gitlab.gnome.org/GNOME/gnome-font-viewer/issues #2 https://gitlab.gnome.org/GNOME/gnome-font-viewer/issues/2 ** Changed in: gnome-font-viewer Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1183765 Title: During typography thumbnailing, the Font Viewer window becomes very unresponsive Status in GNOME Font Viewer: Fix Released Status in One Hundred Papercuts: Triaged Status in gnome-font-viewer package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Close Font Viewer. 2. Install "edubuntu-fonts" package. 3. Launch Font Viewer, and scroll through the listed typographies. * BEHAVIOUR * - EXPECTED: The scrolling to be fluid. - REAL: The scrolling is very choppy; with the window being very unresponsive for a long time, because the thumbnailing not being performed as a background process. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-font-viewer 3.7.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 24 12:09:03 2013 InstallationDate: Installed on 2013-05-21 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-font-viewer/+bug/1183765/+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 1375819] Re: gnome-font-viewer freezes up itself or the X session
*** This bug is a duplicate of bug 1183765 *** https://bugs.launchpad.net/bugs/1183765 ** This bug has been marked a duplicate of bug 1183765 During typography thumbnailing, the Font Viewer window becomes very unresponsive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1375819 Title: gnome-font-viewer freezes up itself or the X session Status in gnome-font-viewer package in Ubuntu: Triaged Status in gnome-font-viewer package in Fedora: Won't Fix Bug description: When I open gnome-font-viewer by clicking on font file (tried on TTF and PFB) it sometimes locks up. Then nothing can be done within the window, but the rest of X session works. However sometimes the whole X session freezes, only mouse cursor moves. It can be worked around by switching to tty1 and killall'ing gnome-font-viewer. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-font-viewer 3.12.0-1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 30 16:46:07 2014 InstallationDate: Installed on 2013-07-21 (436 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) SourcePackage: gnome-font-viewer UpgradeStatus: Upgraded to utopic on 2014-09-25 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819/+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 1407149] Re: Opened up Font Viewer, now it won't close
*** This bug is a duplicate of bug 1183765 *** https://bugs.launchpad.net/bugs/1183765 ** This bug is no longer a duplicate of bug 1375819 gnome-font-viewer freezes up itself or the X session ** This bug has been marked a duplicate of bug 1183765 During typography thumbnailing, the Font Viewer window becomes very unresponsive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1407149 Title: Opened up Font Viewer, now it won't close Status in gnome-font-viewer package in Ubuntu: New Bug description: I opened up the Fonts Viewer, and now it won't close. I just now opened the System Monitor and before I could select the Font Viewer Process to kill it, a popup window came up saying "Font Viewer has failed to respond. Click here to terminate it or here to Wait." I terminated the process. ProblemType: Bug DistroRelease: elementary OS 0.3 Package: elementary-desktop 1.354+398~ubuntu0.3.1 [origin: LP-PPA-elementary-os-daily] ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CrashDB: elementary_meta CurrentDesktop: Pantheon Date: Fri Jan 2 13:27:02 2015 InstallationDate: Installed on 2014-12-27 (6 days ago) InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20140810) ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: elementary-meta SuspiciousXErrors: ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1407149/+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 1425786] Re: Installing font via font viewer freezes system
*** This bug is a duplicate of bug 1183765 *** https://bugs.launchpad.net/bugs/1183765 ** This bug is no longer a duplicate of bug 1375819 gnome-font-viewer freezes up itself or the X session ** This bug has been marked a duplicate of bug 1183765 During typography thumbnailing, the Font Viewer window becomes very unresponsive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1425786 Title: Installing font via font viewer freezes system Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: Installing fonts for a specific program (trelby), if we open the font in font viewer and press the install button, it will install fine but the system will become unresponsive on successful install. cannot open terminal for xkill, nor does any force close warning come up. The only way to get control is to ctrl+alt+f1 into commandline and sudo reboot the system. This is on an older laptop running Freya Beta 2 32bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1425786/+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 1429539] Re: The system hangs during installation of fonts with font viewer elementary
*** This bug is a duplicate of bug 1183765 *** https://bugs.launchpad.net/bugs/1183765 ** This bug is no longer a duplicate of bug 1375819 gnome-font-viewer freezes up itself or the X session ** This bug has been marked a duplicate of bug 1183765 During typography thumbnailing, the Font Viewer window becomes very unresponsive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1429539 Title: The system hangs during installation of fonts with font viewer elementary Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: When installing the elementary sources freezes and only back to typing Ctrl + Alt + F2 and reboot. It has always happened, the fonts are .ttf. ProblemType: Bug DistroRelease: elementary OS 0.3 Package: elementary-desktop 1.368+414~ubuntu0.3.1 [origin: LP-PPA-elementary-os-daily] Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CrashDB: elementary_meta CurrentDesktop: Pantheon Date: Sun Mar 8 05:47:35 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-08 (0 days ago) InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20150208) SourcePackage: elementary-meta SuspiciousXErrors: ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1429539/+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 1827751] Re: Shield screen is displayed after blanking even when lock screen disabled
Quoting Florian Müllner from https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/767#note_627334: > The new lock screen design (which are currently in the process of being > implemented and will be in 3.36) no longer have the shield. > It doesn't look useful to add a work-around that will only be included in few > unstable development releases (and removing the screen fade very much is a > work-around). Meanwhile, maybe reworked patch from that MR can be included in Ubuntu? -- 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/1827751 Title: Shield screen is displayed after blanking even when lock screen disabled Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-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 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827751/+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 1840370] [NEW] Please use Debian packaging
Public bug reported: There was already LP: #539009 about this, but once again Ubuntu seems to be packaging Shotwell on their own then the Debian maintainer does a very good job keeping the package up to date. Please review the Ubuntu-only patches and switch to the Debian packages, submitting Ubuntu delta upstream or to Debian, if needed. Thanks, Andrej, a Shotwell user and the sponsor of the uploads of Shotwell to Debian ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Description changed: - There was already #539009 about this, but once again Ubuntu seems to be - packaging Shotwell on their own then the Debian maintainer does a very - good job keeping the package up to date. + There was already LP: #539009 about this, but once again Ubuntu seems to + be packaging Shotwell on their own then the Debian maintainer does a + very good job keeping the package up to date. Please review the Ubuntu-only patches and switch to the Debian packages, submitting Ubuntu delta upstream or to Debian, if needed. Thanks, Andrej, a Shotwell user and the sponsor of the uploads of Shotwell to Debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1840370 Title: Please use Debian packaging Status in shotwell package in Ubuntu: New Bug description: There was already LP: #539009 about this, but once again Ubuntu seems to be packaging Shotwell on their own then the Debian maintainer does a very good job keeping the package up to date. Please review the Ubuntu-only patches and switch to the Debian packages, submitting Ubuntu delta upstream or to Debian, if needed. Thanks, Andrej, a Shotwell user and the sponsor of the uploads of Shotwell to Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1840370/+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 1799213] Re: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Since it’s not a crash, it’d be difficult to get traces. The issue is in the patch Ubuntu ships for the indicator menu; the warnings don’t appear when the indicator menu is not used. ** Changed in: network-manager-applet (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1799213 Title: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Ubuntu 18.10, network-manager-gnome 1.8.18-2 Every three minutes or less, the applet writes to stderr these messages: (nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-CRITICAL **: 08:09:47.640: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-WARNING **: 08:09:47.668: Can't set a parent on widget which has a parent (nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-CRITICAL **: 08:10:50.616: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:3677): Gtk-WARNING **: 08:10:50.639: Can't set a parent on widget which has a parent Steps to reproduce: - install network-manager-gnome, add the nm-applet to the panel - wait Expected outcome: - not filling up error logs Seen outcome: - filling up error logs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager-gnome 1.8.18-2ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Oct 22 08:08:37 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-05 (869 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.111 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager-applet UpgradeStatus: Upgraded to cosmic on 2018-10-21 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b ethernet 1540209985 Mon 22 Oct 2018 08:06:25 AM EDT yes -999 no/org/freedesktop/NetworkManager/Settings/1 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ac8e86d9-6cff-3015-828a-e5fdbd9f5b0b /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1799213/+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 1758653] Re: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied
** Bug watch added: Debian Bug tracker #831329 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831329 ** Also affects: gvfs (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831329 Importance: Unknown Status: Unknown ** Package changed: gvfs (Debian) => gnome-vfs (Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1758653 Title: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied Status in gvfs package in Ubuntu: Confirmed Status in gnome-vfs package in Debian: Unknown Bug description: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied /var/cache/ has no 'samba' subdir nor file. oem@ubuntu:~$ ls -la /var/cache/ total 80 drwxr-xr-x 18 root root 4096 Feb 19 18:57 . drwxr-xr-x 14 root root 4096 Dec 1 20:15 .. drwxr-xr-x 2 root root 4096 Sep 15 2017 apparmor drwxr-xr-x 4 root root 4096 Dec 1 20:15 app-info drwxr-xr-x 3 root root 4096 Mar 25 14:11 apt drwxr-xr-x 3 root root 4096 Feb 19 18:00 apt-xapian-index drwxr-xr-x 2 root root 4096 Dec 1 20:15 cracklib drwxrwx--- 3 root lp4096 Mar 25 07:35 cups drwxr-xr-x 2 root root 4096 Mar 23 04:41 debconf drwxr-xr-x 2 root root 4096 Dec 1 18:55 dictionaries-common drwxr-xr-x 2 root root 12288 Mar 19 04:28 fontconfig drwxr-xr-x 2 root root 4096 Oct 9 19:50 gdm drwx-- 2 root root 4096 Mar 25 14:11 ldconfig drwxr-xr-x 2 root root 4096 Dec 1 19:13 localepurge drwxr-xr-x 13 man man 4096 Mar 25 14:11 man -rw-r--r-- 1 root root 0 Mar 25 08:24 motd-news drwxr-xr-x 3 root root 4096 Dec 1 19:57 PackageKit drwxr-xr-x 2 root root 4096 Mar 24 14:56 snapd drwxr-xr-x 2 root root 4096 Feb 20 04:57 ubuntu-advantage-tools ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:28:21 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1758653/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
@mapreri: Hmm, it didn’t seem like it worked, that’s why I changed it to manual. Changing it back now. ** Changed in: inkscape (Debian) Importance: Medium => Unknown ** Changed in: inkscape (Debian) Status: Fix Committed => Unknown ** Changed in: inkscape (Debian) Remote watch: None => Debian Bug tracker #910379 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: Fix Committed Status in inkscape package in Debian: Unknown Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
** Changed in: inkscape (Debian) Status: Unknown => New ** Changed in: inkscape (Debian) Remote watch: Debian Bug tracker #910379 => None ** Changed in: inkscape (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: Fix Committed Status in inkscape package in Debian: Fix Committed Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
** Changed in: inkscape (Debian) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: Fix Committed Status in inkscape package in Debian: Unknown Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
** Bug watch added: Debian Bug tracker #910379 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910379 ** Also affects: inkscape (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910379 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: New Status in inkscape package in Debian: Unknown Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
** Information type changed from Private to Public ** Also affects: inkscape Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
** Attachment added: "GIF animation of the crash" https://bugs.launchpad.net/inkscape/+bug/1796046/+attachment/5197018/+files/crash%20recording.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1796046] Re: inkscape crashes when resizing elements with snapping on
** Attachment added: "SVG file on which Inkscape crashes" https://bugs.launchpad.net/inkscape/+bug/1796046/+attachment/5197017/+files/test-crash.svg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1796046 Title: inkscape crashes when resizing elements with snapping on Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: I’ve repeatedly experienced crashes when trying to resize elements in a drawing while having certain snapping modes on. One of the most typical examples was trying to draw a strictly vertical line, holding Ctrl while dragging, getting a crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-3 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 4 10:24:05 2018 ExecutablePath: /usr/bin/inkscape InstallationDate: Installed on 2018-02-16 (229 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: inkscape Signal: 6 SourcePackage: inkscape Title: inkscape crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker geoclue kvm lp lpadmin plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1796046/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
@cyphermox, has there been any proper solution of this since then? Is the patch still needed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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
