[Desktop-packages] [Bug 1744587] [NEW] hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720
You have been subscribed to a public bug: https://askubuntu.com/questions/990970/how-to-install-hplip-3-17-11 -under-ubuntu-17-10-for-hp-officejet-pro-8720 I'm using Ubuntu 17.10 According to the release notes https://developers.hp.com/hp-linux- imaging-and-printing/release_notes I need hplip 3.17.11. When I install hplip from using apt-get I get the following error when I execute hp-check: The error is the following (distro not supported) File "/usr/share/hplip/installer/core_install.py", line 475, in init self.distro_name = self.distros_index[self.distro] I've tried installing from the shell installer with the following: error: Configure failed with error: libnetsnmp not found When I do the following: sudo apt-get install libsnmp-dev I get libsnmp-dev is already the newest version (5.7.3+dfsg-1.7ubuntu1) And apt is an older version apt-cache policy hplip hplip: Installed: 3.17.7+repack0-3 Candidate: 3.17.7+repack0-3 Version table: *** 3.17.7+repack0-3 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Anyone have any ideas on how I can install and/or debug this? ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720 https://bugs.launchpad.net/bugs/1744587 You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip 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 1433943] Re: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)
** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1433943 Title: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid) Status in evolution-data-server package in Ubuntu: Invalid Bug description: It seems Ubuntu does not enable CardDav scope (https://www.googleapis.com/auth/carddav) in online account. Ubuntu only enables Google Contacts API (Gdata) https://www.google.com/m8/feeds/ which is NOT same as CardDav. As a result when some application( ex. Syncevolution) tries to access it (through oauth2), it gives “authentication failed error”. For example, running following command: ''' SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\ loglevel=2 backend=carddav username=uoa:3,google-contacts\ syncURL=https://www.googleapis.com/.well-known/carddav ''' gives following error: “PROPFIND: Neon error code 1: 403 Forbidden, must not retry” NOTE: It is required that that the scope for accessing CardDAV needs to be specified in the sources too. Having it only in the APIs Console is not enough. Otherwise Google rejects access to the CardDAV resources with a 401 "AuthSub challenge". Discussion on Syncevolution Mailing List: https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1433943/+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 1744587] Re: hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720
** Package changed: ubuntu => hplip (Ubuntu) -- 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/1744587 Title: hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720 Status in hplip package in Ubuntu: New Bug description: https://askubuntu.com/questions/990970/how-to-install-hplip-3-17-11 -under-ubuntu-17-10-for-hp-officejet-pro-8720 I'm using Ubuntu 17.10 According to the release notes https://developers.hp.com/hp-linux- imaging-and-printing/release_notes I need hplip 3.17.11. When I install hplip from using apt-get I get the following error when I execute hp-check: The error is the following (distro not supported) File "/usr/share/hplip/installer/core_install.py", line 475, in init self.distro_name = self.distros_index[self.distro] I've tried installing from the shell installer with the following: error: Configure failed with error: libnetsnmp not found When I do the following: sudo apt-get install libsnmp-dev I get libsnmp-dev is already the newest version (5.7.3+dfsg-1.7ubuntu1) And apt is an older version apt-cache policy hplip hplip: Installed: 3.17.7+repack0-3 Candidate: 3.17.7+repack0-3 Version table: *** 3.17.7+repack0-3 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Anyone have any ideas on how I can install and/or debug this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1744587/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
Giving the working note what I'm doing currently: In order to analyze the issue, I tried to remove the /etc/resolv.conf in the normal mode and traced the syslog if any systemd service restored the file. What I observed is NM will go through this line of writing DNS, and reported the warning from calling /etc/resolvconf/update.d/libc: [1516604239.0578] dns-mgr: Writing DNS information to /sbin/resolvconf warning "/etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf" I'm thinking the /etc/resolv.conf will be dynamically recreated, and then NM moved on to finish its service (so NM is able to keep alive). However, under the recovery mode, the NM can't normally start its service and exit due to catch the signal SIGTERM (not sure if it's related to nm_dispatcher). So seems like we have two problems here: 1. why does NM fail to start 2. why does NM not try to call /etc/resolvconf/update.d/libc to restore the file in the recovery mode -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1741095] Re: Ubuntu 17.10 crashes unexpectedly. Can't read the "details" since they appear in a blacked out window.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- 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/1741095 Title: Ubuntu 17.10 crashes unexpectedly. Can't read the "details" since they appear in a blacked out window. Status in sane-backends package in Ubuntu: Confirmed Bug description: I'm a very unskilled user of Ubuntu 17.10. I have no idea why this is happening and cannot positively state that what is happening is a "bug". I was automatically brought to this page by the reporting system. I'm using Ubuntu 17.10 on a Dell E6500 Latitude (yes, it's old) with 4Gb RAM. I don't have enough understanding to know what to ask so if anyone can be of help in getting the needed information to figure this out, I'd be very grateful. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 AptOrdering: libieee1284-3:i386: Install libsane1:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jan 3 12:57:53 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /var/cache/apt/archives/libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-08-31 (124 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741095/+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 1741095] Re: Ubuntu 17.10 crashes unexpectedly. Can't read the "details" since they appear in a blacked out window.
Experienced the same problem when installing wine. The cause of this behaviour seams to be the differing time stamp in the mentioned file. This is also true for the file /lib/udev/rules.d/60-libsane1.rules. --- 20-sane.hwdb32 +++ 20-sane.hwdb64 @@ -1,5 +1,5 @@ # This file was automatically created based on description files (*.desc) -# by sane-desc 3.5 from sane-backends 1.0.27 on Fri Oct 27 06:54:18 2017 +# by sane-desc 3.5 from sane-backends 1.0.27 on Fri Oct 27 06:58:13 2017 # # hwdb file for supported USB devices # Workaround would be manualley downloading libsane1:amd64 and libsane1:i386 and installing both with sudo dpkg -i --force-all . -- 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/1741095 Title: Ubuntu 17.10 crashes unexpectedly. Can't read the "details" since they appear in a blacked out window. Status in sane-backends package in Ubuntu: Confirmed Bug description: I'm a very unskilled user of Ubuntu 17.10. I have no idea why this is happening and cannot positively state that what is happening is a "bug". I was automatically brought to this page by the reporting system. I'm using Ubuntu 17.10 on a Dell E6500 Latitude (yes, it's old) with 4Gb RAM. I don't have enough understanding to know what to ask so if anyone can be of help in getting the needed information to figure this out, I'd be very grateful. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 AptOrdering: libieee1284-3:i386: Install libsane1:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jan 3 12:57:53 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /var/cache/apt/archives/libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-08-31 (124 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741095/+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 1744657] Re: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver()
** Tags removed: wayland-session ** Tags added: wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744657 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() Status in gnome-screensaver package in Ubuntu: New Bug description: Today I upgraded from Ubuntu 2016.04.1 LTS with "sudo do-release-upgrade -d" I also switch back from Gnome to Ubuntu's default desktop environment, which I had left about a year ago because of bugs. Now Ubuntu seems to be working fine, but I received this error report out of nowhere. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 16:18:38 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-screensaver InstallationDate: Installed on 2016-03-21 (672 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-screensaver --no-daemon Signal: 11 SourcePackage: gnome-screensaver StacktraceTop: XGetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() UpgradeStatus: Upgraded to bionic on 2018-01-22 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744657/+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 1738503] Re: Cannot Install SNAPS from Gnome-Software Bionic - invalid credentials
** Summary changed: - Cannot Install SNAPS from Gnome-Software Bionic + Cannot Install SNAPS from Gnome-Software Bionic - invalid credentials -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1738503 Title: Cannot Install SNAPS from Gnome-Software Bionic - invalid credentials Status in gnome-software package in Ubuntu: New Bug description: Error captured in attached Screengrab. I don't recall making any changes, how would I fix this locally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 15 18:36:40 2017 InstallationDate: Installed on 2017-09-25 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) InstalledPlugins: gnome-software-plugin-flatpak 3.26.3-2ubuntu1 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 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/1738503/+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 1744653] Re: gnome-control-center crashed with SIGSEGV in panel_refresh_device_titles()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744653 Title: gnome-control-center crashed with SIGSEGV in panel_refresh_device_titles() Status in gnome-control-center package in Ubuntu: New Bug description: This error occurred for no apparent reason. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 04:33:40 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-12 (71 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x556a65d4c303:mov0x8(%rax),%edx PC (0x556a65d4c303) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1744653/+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 1744668] [NEW] /usr/bin/gnome-control-center:11:net_device_simple_get_speed:device_ethernet_refresh_ui:g_cclosure_marshal_VOID__BOOLEANv:_g_closure_invoke_va:g_signal_emit_vali
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/cd9e575af5c75cea1778ce0df4bc549e2e77e7d7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744668 Title: /usr/bin/gnome-control- center:11:net_device_simple_get_speed:device_ethernet_refresh_ui:g_cclosure_marshal_VOID__BOOLEANv:_g_closure_invoke_va:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/cd9e575af5c75cea1778ce0df4bc549e2e77e7d7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1744668/+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 1371274] Re: Unable to use the widevine plugin with Chromium
*** This bug is a duplicate of bug 1652110 *** https://bugs.launchpad.net/bugs/1652110 chromium builds don't include widevine, only chrome does. There may be a stub libwidevinecdm.so along with a chromium build, but it won't serve to actually decode DRM-encoded content. AFAIK armhf is not supported by upstream chrome. ** This bug has been marked a duplicate of bug 1652110 Chromium 55+ doesn't support Widevine library -- 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/1371274 Title: Unable to use the widevine plugin with Chromium Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium is unable to use the widevine component from google chrome : libwidevinecdmadapter.so and libwidevinecdm.so How to reproduce : - copy the 2 files the chrome archive in /usr/lib/chromium-browser - check chrome://components/ - Widevine does not appear Solution : With the help from several people (hogliux for patch and saiarcot895 for PPA) , a PPA is available with this feature : - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev - You need the binary widevine plugin plugin (2 files) : https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz To be copied in /usr/lib/chromium - Launch netflix.com and see if it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Thu Sep 18 21:11:17 2014 InstallationDate: Installed on 2013-10-02 (350 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1371274/+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 1744671] [NEW] /usr/bin/gnome-screensaver:11:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch:g_main_dispatch
*** This bug is a duplicate of bug 1744657 *** https://bugs.launchpad.net/bugs/1744657 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-8ubuntu1, the problem page at https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-17.10 precise xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744671 Title: /usr/bin/gnome- screensaver:11:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch:g_main_dispatch Status in gnome-screensaver package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-8ubuntu1, the problem page at https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744671/+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 1744671] Re: /usr/bin/gnome-screensaver:11:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch:g_main_dispatch
*** This bug is a duplicate of bug 1744657 *** https://bugs.launchpad.net/bugs/1744657 ** This bug has been marked a duplicate of bug 1744657 gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744671 Title: /usr/bin/gnome- screensaver:11:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch:g_main_dispatch Status in gnome-screensaver package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-8ubuntu1, the problem page at https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744671/+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 1744672] Re: /usr/bin/gnome-screensaver:11:_XGetRequest:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch
*** This bug is a duplicate of bug 1744657 *** https://bugs.launchpad.net/bugs/1744657 ** This bug has been marked a duplicate of bug 1744671 /usr/bin/gnome-screensaver:11:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch:g_main_dispatch ** This bug is no longer a duplicate of bug 1744671 /usr/bin/gnome-screensaver:11:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch:g_main_dispatch ** This bug has been marked a duplicate of bug 1744657 gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744672 Title: /usr/bin/gnome- screensaver:11:_XGetRequest:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch Status in gnome-screensaver package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-7ubuntu5, the problem page at https://errors.ubuntu.com/problem/b582a7de9c13d1b87dcbe585f107e0fc2643e7bc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744672/+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 1744672] [NEW] /usr/bin/gnome-screensaver:11:_XGetRequest:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch
*** This bug is a duplicate of bug 1744657 *** https://bugs.launchpad.net/bugs/1744657 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-7ubuntu5, the problem page at https://errors.ubuntu.com/problem/b582a7de9c13d1b87dcbe585f107e0fc2643e7bc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744672 Title: /usr/bin/gnome- screensaver:11:_XGetRequest:XGetScreenSaver:disable_builtin_screensaver:watchdog_timer:g_timeout_dispatch Status in gnome-screensaver package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-screensaver. This problem was most recently seen with package version 3.6.1-7ubuntu5, the problem page at https://errors.ubuntu.com/problem/b582a7de9c13d1b87dcbe585f107e0fc2643e7bc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744672/+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 1726960] Re: Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso
*** This bug is a duplicate of bug 1742403 *** https://bugs.launchpad.net/bugs/1742403 ** This bug has been marked a duplicate of bug 1742403 package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 -- 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/1726960 Title: Installation of network-manager-config-connectivity-ubuntu fails when installing ubuntu-desktop task from mini.iso Status in network-manager package in Ubuntu: Confirmed Bug description: Installation of this package as part of the Ubuntu Desktop task fails if being executed from the mini.iso after installation. This is due to teh Network Manager service not running when it tries to install itself. This seems like it might be related to https://bugs.launchpad.net/ubuntu/+source/network-manager- applet/+bug/1726958 in some way, as they both happened on a 17.10 installation installed from the mini.iso and the command line (no GUI initially). This issue does *not* happen with the Ubuntu Desktop ISOs. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:17:34 2017 IpRoute: default via 192.168.226.2 dev ens33 proto dhcp src 192.168.226.131 metric 100 192.168.226.0/24 dev ens33 proto kernel scope link src 192.168.226.131 192.168.226.2 dev ens33 proto dhcp scope link src 192.168.226.131 metric 100 IwConfig: ens33 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH ens33 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4disconnected started unknown enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726960/+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 1744631] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat
*** This bug is a duplicate of bug 1742403 *** https://bugs.launchpad.net/bugs/1742403 ** This bug has been marked a duplicate of bug 1742403 package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 -- 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/1744631 Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in network-manager package in Ubuntu: New Bug description: Happened during dist-upgrade from 17.04 to 17.10. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 12:37:27 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-22 (306 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.20.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.20.0/24 dev enp4s0 proto kernel scope link src 192.168.20.95 metric 100 IwConfig: lono wireless extensions. enp4s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 RfKill: SourcePackage: network-manager Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ab27d84f-6bda-350b-b1c1-1cb2c4f13e6f 802-3-ethernet 1516588648 Mon 22 Jan 2018 12:37:28 AEST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp4s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ab27d84f-6bda-350b-b1c1-1cb2c4f13e6f /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744631/+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 1744355] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat
*** This bug is a duplicate of bug 1742403 *** https://bugs.launchpad.net/bugs/1742403 ** This bug has been marked a duplicate of bug 1742403 package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 -- 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/1744355 Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in network-manager package in Ubuntu: New Bug description: The only thing I know is error message about conflict about network. And then, the system asked me about to send a report and I agreed it. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 19 14:28:22 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-19 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) IpRoute: default via 192.168.0.1 dev enp0s25 proto dhcp src 192.168.0.10 metric 100 192.168.0.0/24 dev enp0s25 proto kernel scope link src 192.168.0.10 192.168.0.1 dev enp0s25 proto dhcp scope link src 192.168.0.10 metric 100 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: network-manager Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- enp0s25 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4disconnected started unknown enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1744355/+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 1744657] Re: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744657 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver → disable_builtin_screensaver → watchdog_timer → g_timeout_dispatch → g_main_dispatch Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Today I upgraded from Ubuntu 2016.04.1 LTS with "sudo do-release-upgrade -d" I also switch back from Gnome to Ubuntu's default desktop environment, which I had left about a year ago because of bugs. Now Ubuntu seems to be working fine, but I received this error report out of nowhere. Instance on errors.u.c https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 16:18:38 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-screensaver InstallationDate: Installed on 2016-03-21 (672 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-screensaver --no-daemon Signal: 11 SourcePackage: gnome-screensaver StacktraceTop: XGetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() UpgradeStatus: Upgraded to bionic on 2018-01-22 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744657/+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 1744657] Re: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver()
** Description changed: Today I upgraded from Ubuntu 2016.04.1 LTS with "sudo do-release-upgrade -d" I also switch back from Gnome to Ubuntu's default desktop environment, which I had left about a year ago because of bugs. Now Ubuntu seems to be working fine, but I received this error report out of nowhere. + + Instance on errors.u.c + https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 + ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 16:18:38 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-screensaver InstallationDate: Installed on 2016-03-21 (672 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-screensaver --no-daemon Signal: 11 SourcePackage: gnome-screensaver StacktraceTop: - XGetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6 - () - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + XGetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6 + () + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() UpgradeStatus: Upgraded to bionic on 2018-01-22 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark ** Changed in: gnome-screensaver (Ubuntu) Importance: Medium => High ** Summary changed: - gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() + gnome-screensaver crashed with SIGSEGV in XGetScreenSaver → disable_builtin_screensaver → watchdog_timer → g_timeout_dispatch → g_main_dispatch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744657 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver → disable_builtin_screensaver → watchdog_timer → g_timeout_dispatch → g_main_dispatch Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Today I upgraded from Ubuntu 2016.04.1 LTS with "sudo do-release-upgrade -d" I also switch back from Gnome to Ubuntu's default desktop environment, which I had left about a year ago because of bugs. Now Ubuntu seems to be working fine, but I received this error report out of nowhere. Instance on errors.u.c https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 16:18:38 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-screensaver InstallationDate: Installed on 2016-03-21 (672 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-screensaver --no-daemon Signal: 11 SourcePackage: gnome-screensaver StacktraceTop: XGetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() UpgradeStatus: Upgraded to bionic on 2018-01-22 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744657/+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 1739777] Re: /usr/bin/unity-control-center:11:__GI_____strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739777 Title: /usr/bin/unity-control- center:11:__GI_strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package Status in unity-control-center package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20170930-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/c72f6ed996cfb00e63e15549fd9faafc0a2a184c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1739777/+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 1744677] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
*** This bug is a duplicate of bug 1724557 *** https://bugs.launchpad.net/bugs/1724557 ** Information type changed from Private to Public -- 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/1744677 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in gnome-shell package in Ubuntu: Confirmed Bug description: report to: https://bugs.launchpad.net/bugs/1744539 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:13:39 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6d4e8cbcf0 : movss 0x38(%rdi),%xmm0 PC (0x7f6d4e8cbcf0) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_move_resize_internal () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: Upgraded to artful on 2018-01-11 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744677/+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 1744677] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
*** This bug is a duplicate of bug 1724557 *** https://bugs.launchpad.net/bugs/1724557 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1744677 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in gnome-shell package in Ubuntu: Confirmed Bug description: report to: https://bugs.launchpad.net/bugs/1744539 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:13:39 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6d4e8cbcf0 : movss 0x38(%rdi),%xmm0 PC (0x7f6d4e8cbcf0) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_move_resize_internal () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: Upgraded to artful on 2018-01-11 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744677/+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 1744677] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
*** This bug is a duplicate of bug 1724557 *** https://bugs.launchpad.net/bugs/1724557 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1724557, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1724557 gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() -- 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/1744677 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in gnome-shell package in Ubuntu: Confirmed Bug description: report to: https://bugs.launchpad.net/bugs/1744539 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:13:39 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6d4e8cbcf0 : movss 0x38(%rdi),%xmm0 PC (0x7f6d4e8cbcf0) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_move_resize_internal () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: Upgraded to artful on 2018-01-11 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744677/+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 1704765] Re: can't drag file from desktop to folder window on Artful
This bug is still a major annoyance. It would be really nice to solve this for 18.04 (Bionic). GNOME has recently removed the desktop code from Nautilus, so it seems very unlikely that this will be solved upstream. So presumably someone from Canonical or a community volunteer will need to fix this. -- 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/1704765 Title: can't drag file from desktop to folder window on Artful Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I'm running Ubuntu 17.10 (Artful). If I create a text file on my desktop and then attempt to drag it into a Nautilus folder window, it fails: when I release the mouse cursor over the folder window nothing happens and the file is not moved. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+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 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.104-0ubuntu0.16.04.1 --- nvidia-graphics-drivers-340 (340.104-0ubuntu0.16.04.1) xenial-proposed; urgency=medium * Support for kernel 4.11 (including 4.13). (LP: #1724872) - New upstream release. - Remove incompatible patches for 4.9 and 4.10. - debian/dkms_nvidia/patches/buildfix_kernel_4.11.patch -- Marcelo Henrique Cerri Mon, 06 Nov 2017 14:52:28 -0200 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1724872 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+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 1724872] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-340 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 nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1724872 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+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 1744696] [NEW] web interface fails on load
Public bug reported: Upstream issue report (fixed in upstream version 2.92) https://github.com/transmission/transmission/issues/476 I am unable to connect to the remote web UI, or use any other remote control application. Transmission itself works, but I can't control it except by ssh-ing into the machine its running on with transmission- remote. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: transmission 2.84-3ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Jan 22 21:57:36 2018 Dependencies: transmission-common 2.84-3ubuntu3.1 InstallationDate: Installed on 2013-06-24 (1673 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to xenial on 2017-02-05 (351 days ago) ** Affects: transmission (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1744696 Title: web interface fails on load Status in transmission package in Ubuntu: New Bug description: Upstream issue report (fixed in upstream version 2.92) https://github.com/transmission/transmission/issues/476 I am unable to connect to the remote web UI, or use any other remote control application. Transmission itself works, but I can't control it except by ssh-ing into the machine its running on with transmission- remote. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: transmission 2.84-3ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Jan 22 21:57:36 2018 Dependencies: transmission-common 2.84-3ubuntu3.1 InstallationDate: Installed on 2013-06-24 (1673 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to xenial on 2017-02-05 (351 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1744696/+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 1744695] [NEW] [HP Pavilion dv2000 (GJ175PA#ACJ), Conexant CX20549 (Venice), Speaker, Internal] No sound at all
Public bug reported: The sound control volume slides automatically to ZERO/mute ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rana 1586 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 22 13:27:45 2018 InstallationDate: Installed on 2016-02-11 (710 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rana 1586 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion dv2000 (GJ175PA#ACJ), Conexant CX20549 (Venice), Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.39 dmi.board.name: 30B2 dmi.board.vendor: Wistron dmi.board.version: 61.65 dmi.chassis.type: 10 dmi.chassis.vendor: Wistron dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.39:bd08/27/2007:svnHewlett-Packard:pnHPPaviliondv2000(GJ175PA#ACJ):pvrF.39:rvnWistron:rn30B2:rvr61.65:cvnWistron:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2000 (GJ175PA#ACJ) dmi.product.version: F.39 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1744695 Title: [HP Pavilion dv2000 (GJ175PA#ACJ), Conexant CX20549 (Venice), Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: The sound control volume slides automatically to ZERO/mute ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rana 1586 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 22 13:27:45 2018 InstallationDate: Installed on 2016-02-11 (710 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rana 1586 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion dv2000 (GJ175PA#ACJ), Conexant CX20549 (Venice), Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.39 dmi.board.name: 30B2 dmi.board.vendor: Wistron dmi.board.version: 61.65 dmi.chassis.type: 10 dmi.chassis.vendor: Wistron dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.39:bd08/27/2007:svnHewlett-Packard:pnHPPaviliondv2000(GJ175PA#ACJ):pvrF.39:rvnWistron:rn30B2:rvr61.65:cvnWistron:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2000 (GJ175PA#ACJ) dmi.product.version: F.39 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1744695/+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 1727653] Re: error: can't start new thread
I think this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1730451 and
that you've just run out of memory for a new thread. Please upgrade to
the newest version and try again.
There are three options:
* Release tarball Install - https://launchpad.net/duplicity/+download
* Daily duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily
* Stable duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/ppa
NOTE: UNinstall duplicity first if it was installed via the distribution
repository. For Ubuntu, that would be "sudo apt-get purge duplicity".
** Changed in: duplicity
Milestone: None => 0.7.17
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in deja-dup package in Ubuntu:
Confirmed
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1744584] Re: Exclude Snap .cache from Dejadup backups
** Changed in: deja-dup Status: New => Triaged ** Changed in: deja-dup Importance: Undecided => Wishlist ** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Changed in: deja-dup (Ubuntu) Status: New => Triaged ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1744584 Title: Exclude Snap .cache from Dejadup backups Status in Déjà Dup: Triaged Status in Snappy: New Status in deja-dup package in Ubuntu: Triaged Bug description: The official Backup solution offered by Ubuntu does not support advanced whitelisting/blacklisting of directories. With the introduction of snaps, the cache of the snap apps is stored in ~/snaps /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't be configured to exclude these directories from backups. Since 2009, there have been several requests from the community to add support of advanced include/exclude support in Dejadup but there is no progress. Do you have any plans to provide minimum support for excluding specific snap folders such as .cache? To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1744584/+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 1740238] Re: 'operation already pending' error when drive gets available, manual start required
** Summary changed: - Backups gives 'operation already pending' error when I connect the drive, and I must open Backups to start this pending operation after closing the error message. + 'operation already pending' error when drive gets available, manual start required -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1740238 Title: 'operation already pending' error when drive gets available, manual start required Status in deja-dup package in Ubuntu: New Bug description: I have scheduled daily backups for a laptop to be kept forever on a drive that is often disconnected from the laptop. I connect it when I can; when I connect it, it gives a 'Backups failed' error stating that an operation is already pending. I must then open Backups from the launcher for this pending backup to begin. Please fix these two bugs (or single bug causing two problems?) so that the backup starts without telling me an operation (presumably the backup that starts) is already pending, and without me having to open Backups for it to start. Description: Ubuntu 16.04.3 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 27 17:51:10 2017 InstallationDate: Installed on 2017-11-20 (36 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1740238/+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 1730451] Re: MemoryError while verifying backup
** Changed in: duplicity Milestone: 0.8.00 => 0.7.17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1730451 Title: MemoryError while verifying backup Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: While trying to verify a backup (launched from deja-dup), I receive the following error. My system currently shows 11G of RAM available plus 23G of swap. Possibly related to #1720159? Traceback (most recent call last): File "/usr/bin/duplicity", line 1546, in with_tempdir(main) File "/usr/bin/duplicity", line 1540, in with_tempdir fn() File "/usr/bin/duplicity", line 1391, in main do_backup(action) File "/usr/bin/duplicity", line 1468, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 731, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 763, in get_fileobj_iter manifest = backup_set.get_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in from_string for match in vi_iterator: MemoryError ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: duplicity 0.7.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 6 10:50:12 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-03 (1190 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: duplicity UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1730451/+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 1732530] Re: Dejadup is not working b/c duplicity is not installed
This change was made to remove Python 2 from the Ubuntu-ISO. There should be a button asking you about installation on first use. ** Changed in: deja-dup (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1732530 Title: Dejadup is not working b/c duplicity is not installed Status in ubuntu-mate: Invalid Status in deja-dup package in Ubuntu: Won't Fix Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Bug description: Ubuntu Mate 17.10 Dejadup is not working b/c duplicity is not installed. After a manual install, Deja-Dup works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+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 1725779] Re: Gnome network manager cannot find authentication binary
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-pptp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1741822] Re: nautilus crashed with SIGABRT in g_assertion_message → g_assertion_message_expr → filesystem_info_stop → start_or_stop_io → nautilus_directory_async_state_change
** Summary changed: - nautilus crashed with SIGABRT in g_assertion_message() + nautilus crashed with SIGABRT in g_assertion_message → g_assertion_message_expr → filesystem_info_stop → start_or_stop_io → nautilus_directory_async_state_change -- 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/1741822 Title: nautilus crashed with SIGABRT in g_assertion_message → g_assertion_message_expr → filesystem_info_stop → start_or_stop_io → nautilus_directory_async_state_change Status in nautilus package in Ubuntu: New Bug description: Simply selected a podcast audio file, but app didn't segfault, and otherwise it appears to be working normally. I'm only reporting this, because Ubuntu-Bug was invoked automatically. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 6 21:46:28 2018 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-12-20 (18 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_directory_async_state_changed () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741822/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
I think you can define a font family like in the attached file - which I've eliminated the Google fonts from, so we're only using the files shipped in Ubuntu. This file renders "as expected" in epiphany (webkit) and Firefox, but not in Chromium (as is the case for the previous example given). It *feels* from those results like a problem in Chrome/Chromium, but maybe not - if Olivier has some time, perhaps he could have a look ... ? I'm not a HTML/CSS expert so I could just be understanding it wrong and I'm getting some undefined behaviour cross-browser. If you use Firefox's inspector you can see that it finds Ubuntu / Ubuntu Light / Ubuntu Bold properly. Unfortunately it looks like Chromium's only shows the family so you can't see in great detail what it's doing. ** Attachment added: "test.html" https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1512111/+attachment/5040935/+files/test.html ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** No longer affects: chromium-browser (Ubuntu Wily) ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in chromium-browser package in Ubuntu: New Status in ubuntu-font-family-sources package in Ubuntu: In Progress Status in ubuntu-font-family-sources source package in Wily: Triaged Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1742050] Re: gnome-software crashed with SIGSEGV in g_io_channel_shutdown()
*** This bug is a duplicate of bug 1722185 *** https://bugs.launchpad.net/bugs/1722185 ** This bug is no longer a duplicate of bug 1740151 gnome-software crashed with SIGSEGV in g_io_channel_shutdown() ** This bug has been marked a duplicate of bug 1722185 /usr/bin/gnome-software:11:g_io_channel_shutdown:pk_client_helper_copy_stdout_cb:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1742050 Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown() Status in gnome-software package in Ubuntu: New Bug description: i tried to install wireshark but this error appear ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 13:05:23 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-01-09 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcCmdline: /usr/bin/gnome-software --gapplication-service SegvAnalysis: Segfault happened at: 0x7fcb7d52252f :cmpq $0x0,0x8(%rdi) PC (0x7fcb7d52252f) ok source "$0x0" ok destination "0x8(%rdi)" (0x4038) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: g_io_channel_shutdown () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1742050/+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 1740579] Re: Pomalý systém
Thanks for your report. Could you please explain in English the issue you're experiencing? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1740579 Title: Pomalý systém Status in xorg package in Ubuntu: Incomplete Bug description: SK.LANG.PRACUJE pomaly,pomaly nabieha systém.Nie som dlho užívateľ Ubuntu,zatiaľ sa iba učím. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompositorRunning: None Date: Sat Dec 30 09:50:44 2017 DistUpgraded: 2017-10-23 19:02:47,148 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:13c7] InstallationDate: Installed on 2017-05-30 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411) MachineType: ASUSTeK Computer Inc. K54C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=6ba22068-04c3-4d1a-8a5e-dac9dd5aec79 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-10-23 (67 days ago) dmi.bios.date: 01/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54C.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54C dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54C.204:bd01/20/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K54C dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 23 16:35:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1740579/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode
I'm pretty sure we didn't use to build on s390x. I have added a hack to work around that test, which should be fine, since we don't really use ubuntu-drivers-common on s390x. On 18 January 2018 at 15:51, Łukasz Zemczak <1728...@bugs.launchpad.net> wrote: > The current ubuntu-drivers-common package in xenial-proposed fails to > build on s390x: > > https://launchpad.net/ubuntu/+source/ubuntu-drivers- > common/1:0.4.17.5/+build/14214850 > > I have re-run the build once already and it's still failing on unit- > tests. Could someone take a look and try to resolve that? This SRU can't > get published if it's not built for all supported architectures. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1728547 > > Title: > SRU: Add support for keeping the dGPU on in power saving mode > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=hwe-next; status=New; importance=Undecided; > assignee=None; > Launchpad-Bug: product=oem-priority; status=Triaged; importance=Medium; > assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix > Committed; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=zesty; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix > Committed; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=artful; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix Released; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Tags: originate-from-1720950 somerville > verification-done-artful verification-done-xenial verification-done-zesty > verification-needed > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone alextu anthonywong brian-murray > janitor sil2100 ycheng-twn > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Łukasz Zemczak (sil2100) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1728547 Title: SRU: Add support for keeping the dGPU on in power saving mode Status in HWE Next: New Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Status in ubuntu-drivers-common source package in Zesty: Fix Committed Status in ubuntu-drivers-common source package in Artful: Fix Released Bug description: SRU Request: [Impact] Some systems don't play well when the dGPU is disabled. It should still be possible to use the Intel iGPU without disabling the dGPU. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the nvidia packages are installed, and enable power saving mode: sudo prime-select intel 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Install the mesa-utils package: sudo apt install mesa-utils 5) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default. This is only for hardware specific workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1740151] Re: gnome-software crashed with SIGSEGV in g_io_channel_shutdown()
*** This bug is a duplicate of bug 1722185 *** https://bugs.launchpad.net/bugs/1722185 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1722185 /usr/bin/gnome-software:11:g_io_channel_shutdown:pk_client_helper_copy_stdout_cb:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1740151 Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown() Status in gnome-software package in Ubuntu: Confirmed Bug description: Installing Opera ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8 Uname: Linux 4.13.0-17-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 Date: Tue Dec 26 12:04:05 2017 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2017-12-22 (3 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171220) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_US LANG=en_US.UTF-8 Signal: 11 SourcePackage: gnome-software StacktraceTop: g_io_channel_shutdown () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-software crashed with SIGSEGV in g_io_channel_shutdown() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1740151/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
Above should fix the situation as I just found out the resolvconf service seems not be triggered when recovery mode is applied... If resolvconf.service can be triggered normally, then it would execute "/sbin/resolvconf --enable-updates". This creates a symbolic link /etc/resolv.conf for /run/resolvconf/resolv.conf. Basically the step is a implementation of "dpkg-reconfigure resolvconf". -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1744704] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
Public bug reported: I was installing WINE from: sudo apt-get install --install-recommends winehq-stable after running the following commands: wget -nc https://dl.winehq.org/wine-builds/Release.key sudo apt-key add Release.key sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 11:52:16 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-cSoSjU/141-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-07-17 (189 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: Upgraded to artful on 2017-11-09 (73 days ago) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- 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/1744704 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: I was installing WINE from: sudo apt-get install --install-recommends winehq-stable after running the following commands: wget -nc https://dl.winehq.org/wine-builds/Release.key sudo apt-key add Release.key sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 11:52:16 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-cSoSjU/141-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-07-17 (189 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: Upgraded to artful on 2017-11-09 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744704/+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 1744704] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
** Tags removed: need-duplicate-check -- 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/1744704 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: I was installing WINE from: sudo apt-get install --install-recommends winehq-stable after running the following commands: wget -nc https://dl.winehq.org/wine-builds/Release.key sudo apt-key add Release.key sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 11:52:16 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-cSoSjU/141-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-07-17 (189 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: Upgraded to artful on 2017-11-09 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744704/+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 1744704] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- 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/1744704 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: I was installing WINE from: sudo apt-get install --install-recommends winehq-stable after running the following commands: wget -nc https://dl.winehq.org/wine-builds/Release.key sudo apt-key add Release.key sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 11:52:16 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-cSoSjU/141-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-07-17 (189 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: Upgraded to artful on 2017-11-09 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744704/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
** Also affects: dconf (Ubuntu) Importance: Undecided Status: New ** Changed in: dconf (Ubuntu) Status: New => Triaged ** Changed in: dconf (Ubuntu) Importance: Undecided => High -- 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/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Confirmed Status in d-conf package in Ubuntu: Triaged Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Triaged Status in session-migration package in Ubuntu: Confirmed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1744711] [NEW] Update gnome-terminal to 3.28 (vte 0.52)
Public bug reported: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in vte2.91 package in Ubuntu: New Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1744711/+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 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
For porting the PCRE2 patches to test releases vte-0.51.3 and gnome- terminal-3.27.4, see the patch and instructions at lp:1721412 comment 9. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in vte2.91 package in Ubuntu: New Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1744711/+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 1721412] Re: Update gnome-terminal to 3.26.1
> Could you please open a new bug for the gnome-terminal 3.28 Yup, filed lp:1744711. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1721412 Title: Update gnome-terminal to 3.26.1 Status in gnome-terminal package in Ubuntu: Fix Committed Status in vte2.91 package in Ubuntu: Fix Committed Bug description: We ended up not having time for this for Ubuntu 17.10. The gnome-terminal developer released a 3.25.1 early and then didn't release another build until just before 3.26.0. We'll need to do a bit of work to update vte with our pcre2 revert patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1721412/+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 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
Here's an updated patch against current VTE master. https://git.gnome.org/browse/vte/commit/?id=b274318f2e is a conflicting upstream change. (By the way, I discovered the bug while porting the patch to the previous version.) The easy way to do the merging was, again, (at least for me), to - revert the conflicting upstream change - apply the existing pcre2 patch - manually re-apply the upstream change - squash these to a single commit ** Patch added: "vte post-0.51.3 revert pcre2" https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1744711/+attachment/5040973/+files/vte-lp1744711-b274318f2e-revert-pcre2.patch ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+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 1744584] Re: Exclude Snap .cache from Dejadup backups
I think it would be reasonable to add an Always-on exclude of ~/snap/*/*/.cache maybe. Doesn’t help for snaps that put their cache somewhere else... but that will get the majority of good actors. I don’t know what canonical’s plan for a program like deja dup to programmatically determine which snap folders are worth backing up / which are not. But we could do this hack until they have something for us to use. (They don’t already right?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1744584 Title: Exclude Snap .cache from Dejadup backups Status in Déjà Dup: Triaged Status in Snappy: New Status in deja-dup package in Ubuntu: Triaged Bug description: The official Backup solution offered by Ubuntu does not support advanced whitelisting/blacklisting of directories. With the introduction of snaps, the cache of the snap apps is stored in ~/snaps /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't be configured to exclude these directories from backups. Since 2009, there have been several requests from the community to add support of advanced include/exclude support in Dejadup but there is no progress. Do you have any plans to provide minimum support for excluding specific snap folders such as .cache? To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1744584/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
The valid CSS would be: font-weight: lighter; In the case of explicitly wanting "Ubuntu Light", once everything is fixed, the CSS access will hopefully be just: font-family: "Ubuntu"; font-weight: 300; -- 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/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in chromium-browser package in Ubuntu: New Status in ubuntu-font-family-sources package in Ubuntu: In Progress Status in ubuntu-font-family-sources source package in Wily: Triaged Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 208217] Re: Masks don't work on print or PDF
Not sure whether it is this one, or Bug #427540, but I am having this issue for 0.92.2 in Windows 10. An svg with a mask saved as a PDF shows a blank pdf output. Also, if I look at the SVG file in a browser (chrome, or IE), the masked item does not show up. The masked item is visible in the inkscape viewer however. -- 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/208217 Title: Masks don't work on print or PDF Status in Inkscape: Fix Released Status in inkscape package in Ubuntu: Fix Released Bug description: When printing on 0.46 branch, objects with masks don't appear on the print. In the attached picture, the turtle sitting in the water has a mask with a gradient to make his feet fade into the water. He prints fine in 0.45.1, but in 0.46 branch he's gone. Exporting to bitmap works fine on 0.46. Printing to bitmap (Render as bitmap) works fine also on 0.46. Save as PDF via cairo keeps the turtle but loses all blurs (blurs not implemented in PDF) and the mask, so his legs are fully visible. I think PDF should be capable of a blend to transparent, because the leaves on the bushes blend to transparent and they export to pdf beautifully. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/208217/+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 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
** Changed in: vte2.91 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: vte2.91 (Ubuntu) Status: New => Triaged ** Changed in: gnome-terminal (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-terminal (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in gnome-terminal package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+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 1744720] [NEW] il lettore parole non leggeva la scalettta delle tracce package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/l
Public bug reported: Thanks a lot for cool time with ubuntu With regards Giuseppe Lombardo ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 14:01:39 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2018-01-22 (0 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1744720 Title: il lettore parole non leggeva la scalettta delle tracce package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: Thanks a lot for cool time with ubuntu With regards Giuseppe Lombardo ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 14:01:39 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2018-01-22 (0 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744720/+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 1744720] Re: il lettore parole non leggeva la scalettta delle tracce package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- 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/1744720 Title: il lettore parole non leggeva la scalettta delle tracce package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: Thanks a lot for cool time with ubuntu With regards Giuseppe Lombardo ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 14:01:39 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2018-01-22 (0 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744720/+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 1742950] Re: Snap sections are not shown in GNOME Software
** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1742950 Title: Snap sections are not shown in GNOME Software Status in gnome-software package in Ubuntu: Triaged Bug description: The Snap Store maintains app sections: $ snap find --section=games NameVersionDeveloper Notes Summary boa 0.3njmcphail - WolfenDoom: Blade of Agony pin-town2.0.79 failsafegames - Help the Pin Pals in this physics puzzle game, inspired by Pachinko … However, GNOME Software does not make use of these. It should be taught to display these and their contents when snap support is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1742950/+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 1744619] Re: libnm-glib removal transition
** Also affects: network-manager-iodine (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm filing this bug to keep these packages from landing in bionic until we're ready. We should cherry-pick the gnome-shell 3.26.2-4 changes first. https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia- maintain...@lists.alioth.debian.org;tag=libnm + + Talk with mbiebl about how this transition should work. + + unity-control-center depends on libnm-glib so someone needs to make sure + it will work with the updated VPN plugins -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1744619 Title: libnm-glib removal transition Status in network-manager-iodine package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in network-manager-vpnc package in Ubuntu: New Bug description: I'm filing this bug to keep these packages from landing in bionic until we're ready. We should cherry-pick the gnome-shell 3.26.2-4 changes first. https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia- maintain...@lists.alioth.debian.org;tag=libnm Talk with mbiebl about how this transition should work. unity-control-center depends on libnm-glib so someone needs to make sure it will work with the updated VPN plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-iodine/+bug/1744619/+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 1744584] Re: Exclude Snap .cache from Dejadup backups
The ~/snap/*/*/ structure is currently hardcoded and I'm not aware that any package changes this. So the idea of always excluding ~/snap/*/*/.cache is sensible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1744584 Title: Exclude Snap .cache from Dejadup backups Status in Déjà Dup: Triaged Status in Snappy: New Status in deja-dup package in Ubuntu: Triaged Bug description: The official Backup solution offered by Ubuntu does not support advanced whitelisting/blacklisting of directories. With the introduction of snaps, the cache of the snap apps is stored in ~/snaps /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't be configured to exclude these directories from backups. Since 2009, there have been several requests from the community to add support of advanced include/exclude support in Dejadup but there is no progress. Do you have any plans to provide minimum support for excluding specific snap folders such as .cache? To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1744584/+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 1744581] Re: Nautilus does not support input method in search box
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1744581 Title: Nautilus does not support input method in search box Status in nautilus package in Ubuntu: New Bug description: Nautilus does not support Chinese input method ibus and fcitx ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 Uname: Linux 4.14.9-gnu x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 01:29:09 2018 InstallationDate: Installed on 2017-10-24 (88 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1744581/+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 1744517] Re: Ubuntu Software
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1744517 Title: Ubuntu Software Status in gnome-software package in Ubuntu: Incomplete Bug description: Initially when I was using the internet, a warning symbol near wi-fi symbol (at top right corner) appeared indicating that the system is not updated and may be in risk. To solve the problem I clicked the symbol and a new message is shown that the system is updated. After that the Ubuntu software package icon (left side) is found to be non- responsive. Please advise. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Date: Sun Jan 21 06:42:26 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:118c] InstallationDate: Installed on 2018-01-06 (14 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Swift SF314-52 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic.efi.signed root=UUID=bf576d98-9349-4939-a505-eb772d5a8d9a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Suntory_KL dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd06/27/2017:svnAcer:pnSwiftSF314-52:pvrV1.05:rvnKBL:rnSuntory_KL:rvrV1.05:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-52 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jan 21 06:40:56 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1744517/+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 1724955] Re: unable to drag monitors in Display Arrangement
** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1724955 Title: unable to drag monitors in Display Arrangement Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: I am unable to drag the displays in the Display Arrangement section. I have a dual monitor setup and they are in the reverse order. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:12:07 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 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/gnome-control-center/+bug/1724955/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Ahoy Paul!
On Mon, Jan 22, 2018 at 01:29:46PM -, Paul Sladen wrote:
> The valid CSS would be:
>
> font-weight: lighter;
>
> In the case of explicitly wanting "Ubuntu Light", once everything is
> fixed, the CSS access will hopefully be just:
>
> font-family: "Ubuntu";
> font-weight: 300;
That works - see the second in my test.html. In fact that one works
even in Chromium.
What seems to not work in Chromium (only, AFAICS) is defining a font
family using @font-face and selecting Ubuntu {,Regular,Light}
explicitly, defining their appropriate weights.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
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/1512111
Title:
"Ubuntu Light" font has heavier weight than "Ubuntu"
Status in One Hundred Papercuts:
In Progress
Status in Ubuntu Font Family:
In Progress
Status in chromium-browser package in Ubuntu:
New
Status in ubuntu-font-family-sources package in Ubuntu:
In Progress
Status in ubuntu-font-family-sources source package in Wily:
Triaged
Bug description:
After upgrading from Vivid to Wily, pages using the "Ubuntu light" font
actually renders with a weight heavier than the regular one in web pages.
This happens with Chrome/Chromium and also the Ubuntu browser.
After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in
place of 0.83-0ubuntu1), the issue is fixed.
See the attached screenshot showing the result seen browing
https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ttf-ubuntu-font-family 0.83-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 1 17:55:19 2015
Dependencies:
InstallationDate: Installed on 2014-10-14 (382 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
PackageArchitecture: all
SourcePackage: ubuntu-font-family-sources
UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)
IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users
which impacts the usability and visual design.
The new version of font package (0.831) corrects the relationship
between Light and Medium weight to follow the commonly used naming
standards:
Ubuntu Light Light Light Italic
UbuntuRegular Italic BoldBold Italic
Ubuntu Medium Medium Medium Italic
Ubuntu Condensed Regular
Ubuntu Mono Regular Italic BoldBold Italic
TEST CASE: in 15.10, go to
https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu
If the Light weight renders heavier than Normal weight, the bug is in
place
REGRESSION POTENTIAL
0.831 was tested by manually running in 15.10 and no regression was
noticed, while the bug was fixed. The potential for regression is
small.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1744719] Re: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744719 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: Hello, I'm trying to delete an "Online Account" from Google Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:53:35 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (100 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center online-accounts SegvAnalysis: Segfault happened at: 0x7fd2c3e16fbf : mov(%rbx),%rdi PC (0x7fd2c3e16fbf) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_dbus_object_get_interface () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 goa_object_peek_account () at /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 () () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1744719/+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 1744725] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1589052 *** https://bugs.launchpad.net/bugs/1589052 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1589052, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1744725/+attachment/5041020/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1744725/+attachment/5041022/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1744725/+attachment/5041025/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1744725/+attachment/5041026/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1744725/+attachment/5041027/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1744725/+attachment/5041028/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1744725/+attachment/5041029/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1589052 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744725 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-control-center package in Ubuntu: New Bug description: Happened after unsuspending. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 09:09:58 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/zsh SegvAnalysis: Segfault happened at: 0x7f2cb63c4de2 : mov(%rdi),%rbp PC (0x7f2cb63c4de2) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-10-24 (90 days ago) UserGroups: adm cdrom dip docker lp lpadmin plugdev sambashare staff sudo video whoopsie wireshark www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1744725/+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 1744719] Re: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface()
** Bug watch added: GNOME Bug Tracker #792785 https://bugzilla.gnome.org/show_bug.cgi?id=792785 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=792785 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744719 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: Hello, I'm trying to delete an "Online Account" from Google Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:53:35 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (100 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center online-accounts SegvAnalysis: Segfault happened at: 0x7fd2c3e16fbf : mov(%rbx),%rdi PC (0x7fd2c3e16fbf) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_dbus_object_get_interface () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 goa_object_peek_account () at /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 () () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1744719/+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 1736583] Re: Evince annotations lost on save
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1736583 Title: Evince annotations lost on save Status in evince package in Ubuntu: Confirmed Bug description: I used Evince to annotate a ~70 page PDF. Over a few hours I added a handful of annotations to each page. After every 5th page or so I would "Save a Copy" in a new file name (same filename on every save). When I finished editing the document I saved and noticed that the modified time was not updating on the file. When opening the copy, no annotations were present. I tried saving as different file names and the same thing occurred. Then, stupidly, I opened the original file and it closed the file I had open with the hundreds of annotations and now no files have the annotations. My computer is currently at this state. I would really like to be able to recover the annotations if they happen to be in a cache file somewhere. Secondly, this seems to be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
FYI: solved. Experienced multiple: segfault at 0 ip 7f4fd1d77c16 sp 7ffd50554da0 error 4 in i965_dri.so (deleted)[7f4fd179a000+82d000] Looks to be related to display: Related to Driver for Intel Skylake Integrated Graphics Chipset My System: description: Desktop Computer product: OptiPlex 380 vendor: Dell Inc. serial: XX width: 64 bits capabilities: smbios-2.5 dmi-2.5 vsyscall32 *-core description: Motherboard product: 0HN7XN vendor: Dell Inc. physical id: 0 version: A01 serial: ... After update: $ sudo apt update && sudo apt upgrade -y Things back to normal. -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1744719] Re: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface()
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1744719 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: New Bug description: Hello, I'm trying to delete an "Online Account" from Google Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:53:35 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (100 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center online-accounts SegvAnalysis: Segfault happened at: 0x7fd2c3e16fbf : mov(%rbx),%rdi PC (0x7fd2c3e16fbf) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_dbus_object_get_interface () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 goa_object_peek_account () at /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 () () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1744719/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
According to https://drafts.csswg.org/css-fonts-3/#src-desc: « When authors would prefer to use a locally available copy of a given font and download it if it’s not, local() can be used. The locally-installed argument to local() is a format-specific string that uniquely identifies a single font face within a larger family. Like its use in font-family, can be a quoted string, or a series of unquoted identifiers which are converted to a face name by concatenating them separated by a space. […] Just as a @font-face rule specifies the characteristics of a single font within a family, the unique name used with local() specifies a single font, not an entire font family » So it looks like chromium is not behaving correctly. Neither is epiphany in my tests. Only firefox seems to implement that CSS rule correctly. -- 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/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in ubuntu-font-family-sources package in Ubuntu: In Progress Status in ubuntu-font-family-sources source package in Wily: Triaged Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1690280] Re: Classic confined snaps don't install
Hello Robert, or anyone else affected, Accepted gnome-software into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.20.5-0ubuntu0.16.04.8 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! ** Changed in: gnome-software (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install Status in GNOME Software: Confirmed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Apps that use classic confinement show up in search results but don't install. [Test Case] 1. Open GNOME Software 2. Search for a classic snap, e.g. "atom" 3. Install snap Expected result: Either: a) Snap is installed b) Snap is not installed and error given c) Snap is installed but user needs to provide some sort of confirmation since it is not confined. Observed result: Snap is not installed, no error given. [Regression Potential] Patch changes the code path used to request installation of all snap packages. Ensure that strict confined snaps continue to be installed with correct confinement. For example, try installing "ohmygiraffe" via gnome-software, then run "snap info ohmygiraffe" from a terminal. The "installed:" line should not include the word "classic". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
This is upstream bug https://bugs.chromium.org/p/chromium/issues/detail?id=627143 (see also https://bugzilla.mozilla.org/show_bug.cgi?id=1287089#c1) ** Bug watch added: Mozilla Bugzilla #1287089 https://bugzilla.mozilla.org/show_bug.cgi?id=1287089 ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in ubuntu-font-family-sources package in Ubuntu: In Progress Status in ubuntu-font-family-sources source package in Wily: Triaged Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1744584] Re: Exclude Snap .cache from Dejadup backups
mvo, that’s good. But I’m also leery of assuming what apps do with their own space. Not everyone is going to use .cache. But I’m sure that gets the majority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1744584 Title: Exclude Snap .cache from Dejadup backups Status in Déjà Dup: Triaged Status in Snappy: New Status in deja-dup package in Ubuntu: Triaged Bug description: The official Backup solution offered by Ubuntu does not support advanced whitelisting/blacklisting of directories. With the introduction of snaps, the cache of the snap apps is stored in ~/snaps /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't be configured to exclude these directories from backups. Since 2009, there have been several requests from the community to add support of advanced include/exclude support in Dejadup but there is no progress. Do you have any plans to provide minimum support for excluding specific snap folders such as .cache? To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1744584/+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 1744750] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welche
Public bug reported: package sane-backends could not be found ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 16:27:07 2018 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist InstallationDate: Installed on 2017-12-04 (49 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1744750 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Status in sane-backends package in Ubuntu: New Bug description: package sane-backends could not be found ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 16:27:07 2018 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist InstallationDate: Installed on 2017-12-04 (49 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744750/+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 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
The attachment "vte post-0.51.3 revert pcre2" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in gnome-terminal package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+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 883319] Re: xrandr --scale restricts area in which mouse moves
Here's a script to get this working when using panning: https://gist.github.com/3v1n0/772d48481cffc5b8ca1527d6dcc62f38 Just call it as: ./xrandr-scale.sh i.e: ./xrandr-scale.sh eDP1 0.8 -- 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/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Fix Released Status in xorg-server source package in Quantal: Fix Released Status in xorg-server source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+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 1744750] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- 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/1744750 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Status in sane-backends package in Ubuntu: New Bug description: package sane-backends could not be found ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 16:27:07 2018 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist InstallationDate: Installed on 2017-12-04 (49 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744750/+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 1727653] Re: error: can't start new thread
@Kenneth: The call stack is clearly different. Also, it does not explain
the hanging threads in Duplicity and processes of GPG waiting on pipe
write to return. Also, I have been running the PPA version last few
months.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in deja-dup package in Ubuntu:
Confirmed
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1744764] [NEW] Please sync qpdf 7.1.0 from debian unstable
Public bug reported: If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu 8.04. This is binary compatible with 7.0.0, which is currently in Ubuntu. I thought this happened automatically, so forgive me if this report is superfluous. qpdf 7.1.0 has been in debian unstable for a week and has migrated to testing already. ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1744764 Title: Please sync qpdf 7.1.0 from debian unstable Status in qpdf package in Ubuntu: New Bug description: If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu 8.04. This is binary compatible with 7.0.0, which is currently in Ubuntu. I thought this happened automatically, so forgive me if this report is superfluous. qpdf 7.1.0 has been in debian unstable for a week and has migrated to testing already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1744764/+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 1704765] Re: can't drag file from desktop to folder window on Artful
It is so disappointing that this is not fixed 6 months after it was reported. I just freshly installed 17.10. This bug renders Chrome, text editor, and more unusable. -- 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/1704765 Title: can't drag file from desktop to folder window on Artful Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I'm running Ubuntu 17.10 (Artful). If I create a text file on my desktop and then attempt to drag it into a Nautilus folder window, it fails: when I release the mouse cursor over the folder window nothing happens and the file is not moved. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+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 1735991] Re: QL-570 printer : the led flashes red and nothing happens
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ptouch-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ptouch-driver in Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens Status in ptouch-driver package in Ubuntu: Confirmed Bug description: The label printer Brother QL-570 refuses to print ... When I ask the printer to print, the led flashes red and nothing happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: printer-driver-ptouch 1.4.2-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 13:46:56 2017 InstallationDate: Installed on 2017-12-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: ptouch-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+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 1744657] Re: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver → disable_builtin_screensaver → watchdog_timer → g_timeout_dispatch → g_main_dispatch
Just got the same error again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1744657 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver → disable_builtin_screensaver → watchdog_timer → g_timeout_dispatch → g_main_dispatch Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Today I upgraded from Ubuntu 2016.04.1 LTS with "sudo do-release-upgrade -d" I also switch back from Gnome to Ubuntu's default desktop environment, which I had left about a year ago because of bugs. Now Ubuntu seems to be working fine, but I received this error report out of nowhere. Instance on errors.u.c https://errors.ubuntu.com/problem/db9f31c05086077179fffc889aa4fa02c8e57f46 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 16:18:38 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-screensaver InstallationDate: Installed on 2016-03-21 (672 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-screensaver --no-daemon Signal: 11 SourcePackage: gnome-screensaver StacktraceTop: XGetScreenSaver () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() UpgradeStatus: Upgraded to bionic on 2018-01-22 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1744657/+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 1744767] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) l
Public bug reported: It happened during update. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 18:20:18 2018 ErrorMessage: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól InstallationDate: Installed on 2017-06-24 (212 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól UpgradeStatus: Upgraded to artful on 2017-10-24 (90 days ago) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1744767 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól Status in sane-backends package in Ubuntu: New Bug description: It happened during update. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 18:20:18 2018 ErrorMessage: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól InstallationDate: Installed on 2017-06-24 (212 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól UpgradeStatus: Upgraded to artful on 2017-10-24 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744767/+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 1744564] Re: Evince misses the cursor position.
** Description changed: - Evince is getting wrong the position of the cursor in the window. I'm expecting to choose the menu where the cursor actually points to. The bug appears when the application is closed after side dragging the window and reopened with the same pdf document. + Evince is getting the wrong position of the cursor in the window. I'm expecting to choose the menu where the cursor actually points to but I can only choose the menu when the cursor is beside the menu not pointed to it (see the attachment). The bug appears when the application is closed after side dragging the window and reopened with the same pdf document. I’m using Ubuntu 17.10 and evince version: 3.26.0-1 I have made some more pictures about the bug: http://people.inf.elte.hu/gpeter/complete/evince1.png http://people.inf.elte.hu/gpeter/complete/evince2.png http://people.inf.elte.hu/gpeter/complete/evince3.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1744564 Title: Evince misses the cursor position. Status in evince package in Ubuntu: New Bug description: Evince is getting the wrong position of the cursor in the window. I'm expecting to choose the menu where the cursor actually points to but I can only choose the menu when the cursor is beside the menu not pointed to it (see the attachment). The bug appears when the application is closed after side dragging the window and reopened with the same pdf document. I’m using Ubuntu 17.10 and evince version: 3.26.0-1 I have made some more pictures about the bug: http://people.inf.elte.hu/gpeter/complete/evince1.png http://people.inf.elte.hu/gpeter/complete/evince2.png http://people.inf.elte.hu/gpeter/complete/evince3.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1744564/+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 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)
Hello, Thank you Julian K for the packaging. I've tested it and it works. My braille display has been correctly detected after the BRLTTY service was launched. The BRLTTy service is not activated by default at startup. I don't know what was the behavior on the previous version. @Samuel: Do you know ? Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1741070 Title: Please merge brltty (main) 5.5-4 from Debian unstable (main) Status in brltty package in Ubuntu: Fix Committed Bug description: Dear Ubuntu team, BRLTTY 5.5 was published in April 2017. It comes with several fixes and support of new braille devices. Could it be possible to upload it for Ubuntu 18.04 ? Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1741070/+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 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)
I don't know how ubuntu manages that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1741070 Title: Please merge brltty (main) 5.5-4 from Debian unstable (main) Status in brltty package in Ubuntu: Fix Committed Bug description: Dear Ubuntu team, BRLTTY 5.5 was published in April 2017. It comes with several fixes and support of new braille devices. Could it be possible to upload it for Ubuntu 18.04 ? Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1741070/+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 1744764] Re: Please sync qpdf 7.1.0 from debian unstable
Thanks for reporing. It was indeed synced automatically, however it is currently stuck in bionic-proposed, waiting to be built on some architectures (https://bugs.launchpad.net/ubuntu/+source/qpdf/7.1.0-1). ** Changed in: qpdf (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1744764 Title: Please sync qpdf 7.1.0 from debian unstable Status in qpdf package in Ubuntu: Fix Released Bug description: If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu 8.04. This is binary compatible with 7.0.0, which is currently in Ubuntu. I thought this happened automatically, so forgive me if this report is superfluous. qpdf 7.1.0 has been in debian unstable for a week and has migrated to testing already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1744764/+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 1744764] Re: Please sync qpdf 7.1.0 from debian unstable
** Changed in: qpdf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1744764 Title: Please sync qpdf 7.1.0 from debian unstable Status in qpdf package in Ubuntu: Fix Released Bug description: If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu 8.04. This is binary compatible with 7.0.0, which is currently in Ubuntu. I thought this happened automatically, so forgive me if this report is superfluous. qpdf 7.1.0 has been in debian unstable for a week and has migrated to testing already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1744764/+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 1744764] Re: Please sync qpdf 7.1.0 from debian unstable
Launchpad had correctly picked up the new version for auto-sync. See here: https://launchpad.net/ubuntu/+source/qpdf Unfortunately there is a problem with the build servers having stopped the release of new Bionic packages for several days. Therefore the package does not appear for download in system updates. You see here that 2 architectures (server-only AFAIK) are not building: https://launchpad.net/ubuntu/+source/qpdf/7.1.0-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1744764 Title: Please sync qpdf 7.1.0 from debian unstable Status in qpdf package in Ubuntu: Fix Released Bug description: If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu 8.04. This is binary compatible with 7.0.0, which is currently in Ubuntu. I thought this happened automatically, so forgive me if this report is superfluous. qpdf 7.1.0 has been in debian unstable for a week and has migrated to testing already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1744764/+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 1744764] Re: Please sync qpdf 7.1.0 from debian unstable
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1744764 Title: Please sync qpdf 7.1.0 from debian unstable Status in qpdf package in Ubuntu: Fix Released Bug description: If possible, please sync qpdf 7.1.0-1 from debian unstable for Ubuntu 8.04. This is binary compatible with 7.0.0, which is currently in Ubuntu. I thought this happened automatically, so forgive me if this report is superfluous. qpdf 7.1.0 has been in debian unstable for a week and has migrated to testing already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1744764/+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 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)
One of our changes is Disable brltty.service by default, but enable it if the user configures Braille at install time for a non-USB display -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1741070 Title: Please merge brltty (main) 5.5-4 from Debian unstable (main) Status in brltty package in Ubuntu: Fix Committed Bug description: Dear Ubuntu team, BRLTTY 5.5 was published in April 2017. It comes with several fixes and support of new braille devices. Could it be possible to upload it for Ubuntu 18.04 ? Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1741070/+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 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)
OK, it was the behavior I've experienced on my test, so for me it works. Thanks a lot. Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1741070 Title: Please merge brltty (main) 5.5-4 from Debian unstable (main) Status in brltty package in Ubuntu: Fix Committed Bug description: Dear Ubuntu team, BRLTTY 5.5 was published in April 2017. It comes with several fixes and support of new braille devices. Could it be possible to upload it for Ubuntu 18.04 ? Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1741070/+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 1744775] [NEW] "Operation was cancelled" when trying to use Transparency Unit in Canon 9000F Mark II
Public bug reported: I'm trying to scan foto negatives using this command (that used to work in previous Ubuntu versions): scanimage --device-name pixma:04A9190D --source "Transparency Unit" --resolution "2400" --format "tiff" --mode Color -l 76 -x 66 > test.tiff But I get this error: scanimage: sane_read: Operation was cancelled Note: scanning regular images (using the Flatbed source) works fine. My current ubuntu verison is Ubuntu 17.10 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New -- 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/1744775 Title: "Operation was cancelled" when trying to use Transparency Unit in Canon 9000F Mark II Status in sane-backends package in Ubuntu: New Bug description: I'm trying to scan foto negatives using this command (that used to work in previous Ubuntu versions): scanimage --device-name pixma:04A9190D --source "Transparency Unit" --resolution "2400" --format "tiff" --mode Color -l 76 -x 66 > test.tiff But I get this error: scanimage: sane_read: Operation was cancelled Note: scanning regular images (using the Flatbed source) works fine. My current ubuntu verison is Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744775/+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 1744619] Re: libnm-glib removal transition
** Also affects: network-manager-l2tp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1744619 Title: libnm-glib removal transition Status in network-manager-iodine package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in network-manager-vpnc package in Ubuntu: New Bug description: I'm filing this bug to keep these packages from landing in bionic until we're ready. We should cherry-pick the gnome-shell 3.26.2-4 changes first. https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia- maintain...@lists.alioth.debian.org;tag=libnm Talk with mbiebl about how this transition should work. unity-control-center depends on libnm-glib so someone needs to make sure it will work with the updated VPN plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-iodine/+bug/1744619/+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 1737168] Re: package python3-louis 2.6.4-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: liblouis (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liblouis in Ubuntu. https://bugs.launchpad.net/bugs/1737168 Title: package python3-louis 2.6.4-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in liblouis package in Ubuntu: Confirmed Bug description: cannot install packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-louis 2.6.4-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Dec 8 08:06:30 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 liblouis-data 2.6.4-2ubuntu0.1 liblouis9 2.6.4-2ubuntu0.1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-12-08 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: liblouis Title: package python3-louis 2.6.4-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblouis/+bug/1737168/+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 1724926] Re: No button to launch nm-connection-editor for Advanced functionality like VLANs
** Package changed: network-manager-applet (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1724926 Title: No button to launch nm-connection-editor for Advanced functionality like VLANs Status in gnome-control-center package in Ubuntu: New Bug description: Gnome removed the ability to add/remove VLANs. When people ask / complain about how this is to be accomplished, they are usually referred to nm-connection-editor. Can a Gnome developer please add an "Advanced Configuration" button that launches nm-connection-editor? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-gnome 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 11:38:58 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.50.253 dev vlan757 proto static metric 400 169.254.0.0/16 dev vlan757 scope link metric 1000 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 400 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369 vlan 1508438283 Thu 19 Oct 2017 11:38:03 AM PDT yes 0 no/org/freedesktop/NetworkManager/Settings/4 yes vlan757 activated /org/freedesktop/NetworkManager/ActiveConnection/8 -- Wired connection 1 23ca82a4-d9c5-3d59-ac84-56db17873201 802-3-ethernet 1508433170 Thu 19 Oct 2017 10:12:50 AM PDT no 4294966297 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724926/+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 1744767] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) lib
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- 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/1744767 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól Status in sane-backends package in Ubuntu: New Bug description: It happened during update. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 22 18:20:18 2018 ErrorMessage: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól InstallationDate: Installed on 2017-06-24 (212 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a megosztott „/lib/udev/hwdb.d/20-sane.hwdb” felülírási kísérlete, amely eltér a(z) libsane1:i386 csomag egyéb példányaitól UpgradeStatus: Upgraded to artful on 2017-10-24 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744767/+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 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode
I don't understand why that bug was marked as fixed when the standard vlc package in Ubuntu is obviously not fixed and still causing those crashes and bothering users. And I really don't see the point for opening a new bug report for the same old problem, so I just changed the status of this bug. Side note: In the current snap package of vlc 3.0.0-rc7 those crashes are not happening any more. As there are other minor issues in that snap (like no disabling of screen timeout while video playback), that is not a perfect workaround yet for users who prefer vlc. ** Changed in: vlc (Ubuntu) Status: Fix Released => Confirmed -- 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/1720901 Title: VLC under Wayland causes system freezes in fullscreen mode Status in gnome-shell package in Ubuntu: Invalid Status in vlc package in Ubuntu: Confirmed Status in vlc package in Debian: Fix Released Bug description: Ubuntu version: 17.10 (most recent updates as of October 3rd) vlc version: 2.2.6-6 Whan I expect to happen: When playing a video in vlc and switching to fullscreen mode everything should work fine. Also when changing to a different position of a movie in fullscreen I expect the player to just switch to that position. What actually happens: It seems to depend a little on the file type of the video, mostly I get problems when going to fullscreen mode and then switching to a different position with the playback position bar. With some videos it was even enough to just open the fullscreen mode. The video freezes just displaying a frame while the audio keeps playing. The computer does not react any more to mouse or keyboard input, I have to perform a hard reboot. This problem only appears under the Wayland session, in the Xorg session everything works fine as expected. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-30 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: vlc 2.2.6-6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720901/+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 950352] Re: Online Accounts UI Missing
Same for me, using Lubuntu 17.10.1 Can open it with “gnome-control-center online-accounts” from a console (although there are two warning message, see below), but that's not clean to have to open a console to open it. I came to that issue while learning more about Ubuntu WebApps. Additionally, opening the missing control panel from a console, I get these two messages: ** (gnome-control-center:10977): WARNING **: Could not find settings panel "online-accounts" ** (gnome-control-center:10977): WARNING **: Could not load setting panel "online-accounts": Unknown error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/950352 Title: Online Accounts UI Missing Status in empathy package in Ubuntu: Expired Status in gnome-online-accounts package in Ubuntu: Expired Bug description: Recently upgraded from 11.10 to 12.04B1. I have no "Online Account..." option in the UI. Previously it was an option in the User Indicator. Though I was unable to find it in Settings or Searching Unity, I was able to access it through "Empathy" using the "Edit Connection Parameters..." for my Google chat account that was previously setup via GOA. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-online-accounts 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 15:48:23 2012 ProcEnviron: LANGUAGE=en TERM=xterm LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to precise on 2012-03-03 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/950352/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
The issue is not NM, but in the friendly-recovery, and I already prepare the patch to be reviewed. -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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
