[Desktop-packages] [Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address
Note: I'm not using Ubuntu, but I couldn't find a more appropriate place to give more visibility to this bug. -- 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/1730184 Title: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Status in gnome-shell package in Ubuntu: New Bug description: Went to log into my fairly newly upgraded ubuntu artful system today but was presented with a new login instead of a login with all my applications running, similar to #1728474 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ), only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented with one when I came to log in in the morning. syslog gives a clue: Nov 5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Nov 5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost Nov 5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in libglib-2.0.so.0.5400.1[7fcceb6c6000+111000] This, followed by everything that was running failing to various degrees of cleanness. intel-microcode: Installed: 3.20170707.1 Candidate: 3.20170707.1 Version table: *** 3.20170707.1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/restricted amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-intel: Installed: 2:2.99.917+git20170309-0ubuntu1 Candidate: 2:2.99.917+git20170309-0ubuntu1 Version table: *** 2:2.99.917+git20170309-0ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status libglib2.0-0: Installed: 2.54.1-1ubuntu1 Candidate: 2.54.1-1ubuntu1 Version table: *** 2.54.1-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: ubuntu:GNOME Date: Sun Nov 5 07:27:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'libreoffice-calc.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']" b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-04-18 (200 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+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 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address
This caused data loss for me, as I was resizing a large NTFS partition using gparted. ** Attachment added: "teohhanhui journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+attachment/5019114/+files/teohhanhui%20journalctl.log -- 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/1730184 Title: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Status in gnome-shell package in Ubuntu: New Bug description: Went to log into my fairly newly upgraded ubuntu artful system today but was presented with a new login instead of a login with all my applications running, similar to #1728474 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ), only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented with one when I came to log in in the morning. syslog gives a clue: Nov 5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Nov 5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost Nov 5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in libglib-2.0.so.0.5400.1[7fcceb6c6000+111000] This, followed by everything that was running failing to various degrees of cleanness. intel-microcode: Installed: 3.20170707.1 Candidate: 3.20170707.1 Version table: *** 3.20170707.1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/restricted amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-intel: Installed: 2:2.99.917+git20170309-0ubuntu1 Candidate: 2:2.99.917+git20170309-0ubuntu1 Version table: *** 2:2.99.917+git20170309-0ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status libglib2.0-0: Installed: 2.54.1-1ubuntu1 Candidate: 2.54.1-1ubuntu1 Version table: *** 2.54.1-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: ubuntu:GNOME Date: Sun Nov 5 07:27:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'libreoffice-calc.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']" b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-04-18 (200 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+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 1736664] [NEW] /usr/bin/gnome-shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.26.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 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-shell (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-18.04 -- 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/1736664 Title: /usr/bin/gnome- shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.26.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 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-shell/+bug/1736664/+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 1736595] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de o
*** 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/1736595 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: the app do not install ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 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 Date: Tue Dec 5 17:13:20 2017 ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote libsane1:i386 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 tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote 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/1736595/+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 1719797] Re: Firmware update seemingly not working
** Changed in: gnome-software Status: Confirmed => In Progress -- 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/1719797 Title: Firmware update seemingly not working Status in GNOME Software: In Progress Status in gnome-software package in Ubuntu: Triaged Bug description: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+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 789472] Re: libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev
** Changed in: libgpod (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgpod in Ubuntu. https://bugs.launchpad.net/bugs/789472 Title: libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev Status in libgpod package in Ubuntu: Fix Released Status in libgpod package in Debian: Fix Released Bug description: libgpod doesn't depend on GTK2, only gdk-pixbuf, which is shared by GTK2 and GTK3. However, building GTK3 applications with ibgpod unnecessarily causes GTK2 development files to be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/789472/+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 1735363] Re: inkscape: Use/Port of Python3 needed, or considering demotion
Matthias, I dropped the usb seed and I did a tasksel upload that I think dropped the usb task. I don't see any reverse-depends for the inkscape in main. Can you figure out why inkscape is still in main but is not showing up on the component mismatches report? -- 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/1735363 Title: inkscape: Use/Port of Python3 needed, or considering demotion Status in Inkscape: New Status in inkscape package in Ubuntu: New Status in inkscape package in Debian: New Bug description: inkscape: Use/Port of Python3 needed, or considering demotion. Currently seeded in usb (???), owned by desktop-packages. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1735363/+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 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
@Gunnar Hjalmarsson It is my pleasure :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? Status in language-selector package in Ubuntu: In Progress Status in lubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Released Bug description: In Ubuntu 16.04 Noto Sans CJK is the default font for rendering Chinese. After having struggled with a few issues, I believe that we finally achieved the desired improvement of the rendering experience. So now I ask: Is there an interest from Japanese and Korean users to consider a switch to Noto Sans? (The fonts are already installed for all users on Ubuntu 16.04.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+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 1434986] Re: Not working network connection after boot
All, Is anyone working on this considering this issue is marked critical? -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1733136] Re: wayland session in Ubuntu 18.04 chooses vmware driver on intel hardware
More info re the video card: it's using the i915 driver. lshw -c video *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 04 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:135 memory:eb00-ebff memory:8000-8fff ioport:f000(size=64) memory:c-d ** Summary changed: - gnome-shell no longer offers wayland session in Ubuntu 18.04 + wayland session in Ubuntu 18.04 chooses vmware driver on intel hardware ** Description changed: I upgraded to 18.04 and I no longer get an option to run a wayland session (17.10 offered both the default ubuntu wayland session and xorg on this laptop). + + gnome-shell runs under the llvmpipe driver. (Unity used to run when I + first upgraded, but now gnome-shell is the only option because the gdm + login screen offers no login options.) The upgrade did force me to remove bumblebee and nvidia, but afterwards I manually reinstalled bumblebee and nvidia-387 and reset to using intel via prime-select (installing nvidia changes some of the symlinks so that gnome-shell no longer boots, but "sudo prime-select intel" fixes this). The nvidia-387 modules are blacklisted in /etc/modprobe.d, and bumblebee isn't reporting any errors - bbswitch reports that the nvidia card is off, so I don't think it's an issue with hybrid graphics. (primusrun does work, as well.) Attached are the mutter logs that I generated via the environment variables mentioned in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583 comment #20. I suspect that the culprit is hinted at in this message: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extensio - n for GBM renderer: EGL_KHR_platform_gbm, Missing EGL extensions required for EGLDevice renderer: + n for GBM renderer: EGL_KHR_platform_gbm, Missing EGL extensions required for EGLDevice renderer: EGL_EXT_device_base ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 Uname: Linux 4.14.0-041400-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 10:28:10 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-16 (94 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. + Users in the 'systemd-journal' group can see all messages. Pass -q to + turn off this notice. + No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2017-11-17 (1 days ago) -- 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/1733136 Title: wayland session in Ubuntu 18.04 chooses vmware driver on intel hardware Status in gnome-shell package in Ubuntu: New Bug description: I upgraded to 18.04 and I no longer get an option to run a wayland session (17.10 offered both the default ubuntu wayland session and xorg on this laptop). gnome-shell runs under the llvmpipe driver. (Unity used to run when I first upgraded, but now gnome-shell is the only option because the gdm login screen offers no login options.) The upgrade did force me to remove bumblebee and nvidia, but afterwards I manually reinstalled bumblebee and nvidia-387 and reset to using intel via prime-select (installing nvidia changes some of the symlinks so that gnome-shell no longer boots, but "sudo prime-select intel" fixes this). The nvidia-387 modules are blacklisted in /etc/modprobe.d, and bumblebee isn't reporting any errors - bbswitch reports that the nvidia card is off, so I don't think it's an issue with hybrid graphics. (primusrun does work, as well.) Attached are the mutter logs that I generated via the environment variables mentioned in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583 comment #20. I suspect that the culprit is hinted at in this message: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extensio n for GBM
[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
This is affecting me as well on a thinkpad x1 carbon running pop os (ubuntu 17.10 derivative). -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+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 1728588] Re: Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
This just started happening to me after I switched from 16.04 to 17.10. I have a KVM switch (to switch my keyboard/mouse to multiple machines) and an HDMI switch (to switch the monitors). When I was running 16.04 I could switch the physical display away from the Linux box for days and the session was still live when I switched the monitor back to it. After installing 17.10 just switching the monitor trashes the session - making that switch a really expensive operation in terms of work context. -- 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/1728588 Title: Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 Status in xorg-server package in Ubuntu: New Bug description: I turned off my screen for a few hours then turned it on again and my session was no longer there and i had to login again. The following lines from syslog at the time that i turned on the screen again look suspicious. My hypothesis is that the error from the Intel kernel driver caused the "Fatal server error" "wl_registry@2: error 0: invalid global wl_output (36)" in gnome-shell. Since the screen is actually still operational (after all, the computer didn't crash, only that session, and i was immediately shown the login screen and able to login again), what should have happened is that gnome- shell should have gracefully dealt with whatever happened without a fatal error. This is the first time this has happened, and it did not used to happen before my upgrade to Artful a few days ago. Oct 30 05:46:16 bshanks-SP4 kernel: [358036.641989] [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd13c c40 Gjs_ShowAppsIcon.dash-item-container] connect method ... (a bunch of similar warnings about addSignalMethods) ... Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: Fatal server error: Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) wl_registry@2: error 0: invalid global wl_output (36) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: ubuntu:GNOME Date: Mon Oct 30 06:01:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-06 (572 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1728588/+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 1726906] Re: invalid read in the plugin loader code
** Changed in: gnome-software Status: Confirmed => 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/1726906 Title: invalid read in the plugin loader code Status in GNOME Software: Incomplete Status in gnome-software package in Ubuntu: Triaged Bug description: Using the 17.10 version valgrind shows that error (the system has an invalid snap store login account configured so it might be due to that) ==4467== Invalid read of size 8 ==4467==at 0x52E7747: g_type_check_instance_is_a (gtype.c:4008) ==4467==by 0x175E3C: GS_IS_PLUGIN_EVENT (gs-plugin-event.h:34) ==4467==by 0x175E3C: gs_plugin_event_add_flag (gs-plugin-event.c:210) ==4467==by 0x52C1F9C: g_closure_invoke (gclosure.c:804) ==4467==by 0x52D4CDD: signal_emit_unlocked_R (gsignal.c:3635) ==4467==by 0x52DD4B4: g_signal_emit_valist (gsignal.c:3391) ==4467==by 0x52DDECE: g_signal_emit (gsignal.c:3447) ==4467==by 0x52C6463: g_object_dispatch_properties_changed (gobject.c:1080) ==4467==by 0x52C8838: g_object_notify_by_spec_internal (gobject.c:1173) ==4467==by 0x52C8838: g_object_notify (gobject.c:1221) ==4467==by 0x17AECF: gs_plugin_loader_notify_idle_cb (gs-plugin-loader.c:297) ==4467==by 0x5550E24: g_main_dispatch (gmain.c:3148) ==4467==by 0x5550E24: g_main_context_dispatch (gmain.c:3813) ==4467==by 0x55511EF: g_main_context_iterate.isra.30 (gmain.c:3886) ==4467==by 0x555127B: g_main_context_iteration (gmain.c:3947) ==4467== Address 0x2bf16960 is 0 bytes inside a block of size 72 free'd ==4467==at 0x4C30D3B: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4467==by 0x52E6AB0: g_type_free_instance (gtype.c:1943) ==4467==by 0x1783F1: glib_autoptr_cleanup_GObject (gobject-autocleanups.h:25) ==4467==by 0x1783F1: glib_autoptr_cleanup_GsPluginEvent (gs-plugin-event.h:34) ==4467==by 0x1783F1: gs_plugin_loader_create_event_from_error (gs-plugin-loader.c:332) ==4467==by 0x1783F1: gs_plugin_error_handle_failure (gs-plugin-loader.c:410) ==4467==by 0x17953F: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:742) ==4467==by 0x17A073: gs_plugin_loader_run_refine_internal (gs-plugin-loader.c:816) ==4467==by 0x17A58E: gs_plugin_loader_run_refine (gs-plugin-loader.c:950) ==4467==by 0x17B14F: gs_plugin_loader_process_thread_cb (gs-plugin-loader.c:3170) ==4467==by 0x58A5D55: g_task_thread_pool_thread (gtask.c:1328) ==4467==by 0x557900F: g_thread_pool_thread_proxy (gthreadpool.c:307) ==4467==by 0x5578644: g_thread_proxy (gthread.c:784) ==4467==by 0x82D07FB: start_thread (pthread_create.c:465) ==4467==by 0x85FCB0E: clone (clone.S:95) ==4467== Block was alloc'd at ==4467==at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==4467==by 0x5556578: g_malloc (gmem.c:94) ==4467==by 0x556E0F5: g_slice_alloc (gslice.c:1025) ==4467==by 0x556E588: g_slice_alloc0 (gslice.c:1051) ==4467==by 0x52E66D4: g_type_create_instance (gtype.c:1848) ==4467==by 0x52C75E7: g_object_new_internal (gobject.c:1797) ==4467==by 0x52C8D84: g_object_new_with_properties (gobject.c:1965) ==4467==by 0x52C9800: g_object_new (gobject.c:1637) ==4467==by 0x175F91: gs_plugin_event_new (gs-plugin-event.c:319) ==4467==by 0x178294: gs_plugin_loader_create_event_from_error (gs-plugin-loader.c:347) ==4467==by 0x178294: gs_plugin_error_handle_failure (gs-plugin-loader.c:410) ==4467==by 0x17953F: gs_plugin_loader_call_vfunc (gs-plugin-loader.c:742) ==4467==by 0x17A073: gs_plugin_loader_run_refine_internal (gs-plugin-loader.c:816) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1726906/+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 1736375] Re: Graphics Nvidia bugs_ HP zbook g3
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1736375 Title: Graphics Nvidia bugs_ HP zbook g3 Status in xorg package in Ubuntu: New Bug description: Graphics Nvidia bugs_ HP zbook g3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 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: Tue Dec 5 11:26:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GM107GLM [Quadro M1000M] [103c:8108] MachineType: HP HP ZBook Studio G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=b5469c85-6863-426f-890e-cf89ceba4df7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2017 dmi.bios.vendor: HP dmi.bios.version: N82 Ver. 01.19 dmi.board.name: 80D4 dmi.board.vendor: HP dmi.board.version: KBC Version 11.6F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN82Ver.01.19:bd09/26/2017:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.6F:cvnHP:ct10:cvr: dmi.product.name: HP ZBook Studio G3 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.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: Tue Dec 5 10:01:31 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1736375/+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 1580605] Re: gnome-shell crashes often
I find that Gnome crashes frequently when using Google Chrome, as well as when I'm undertaking computation-heavy tasks (statistical analysis, etc.) Log output: INFO: task gnome-shell:1491 blocked for more than 120 seconds. Unrecoverable failure in required component org.gnome.Shell.desktop CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- 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/1580605 Title: gnome-shell crashes often Status in gnome-shell package in Ubuntu: Confirmed Bug description: I don't have full stacktrace right now unfortunately but gnome-shell appears to be crashing a lot for me. I am running it with multiple monitors and it crashes with following errors: [58566.199387] gnome-shell[11622]: segfault at e8 ip 7f577582c582 sp 7ffc18448048 error 4 in libgdk-3.so.0.1800.9[7f57757ef000+d4000] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 11 09:16:52 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-17 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1580605/+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 1728791] Update Released
The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1728791 Title: [SRU] pulseaudio-droid module crashes on start Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Xenial: Fix Released Bug description: Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4 [Impact] * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) from using the pulseaudio-modules-droid on android devices. * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates enabled. * Last 3 releases of pulseaudio included multiple patches which modified behavior of pulsecore library but required changes were not made in pulseaudio-module-droid. * This results in crash in pulseaudio-modules-droid #0 init_profile (u=0x59528) at modules/droid/module-droid-card.c:370 #1 module_droid_card_22_LTX_pa__init (m=0x3c3f8) at modules/droid/module-droid-card.c:923 #2 0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 "module-droid-card-22", argument=0x0) at pulsecore/module.c:180 #3 0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, fail=0x3c1f4) at pulsecore/cli-command.c:439 #4 0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at pulsecore/cli-command.c:2134 #5 0xf76f6fc8 in pa_cli_command_execute_line (c=, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155 #6 0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153 #7 0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at pulsecore/ioline.c:269 #8 do_read (l=0x3c208) at pulsecore/ioline.c:337 #9 do_work (l=0x3c208) at pulsecore/ioline.c:386 #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655 #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898 #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, retval=0xfffef1c4) at pulse/mainloop.c:929 #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944 #14 0x000158ca in main (argc=, argv=) at daemon/main.c:1152 [Test Case] * Start pulseaudio * From another session run pacmd * In prompt type load-module module-droid-discover * On ubuntu touch devices, it will crash at startup [Regression Potential] * There is no regression potential for other parts of pulseaudio components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+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 1728791] Re: [SRU] pulseaudio-droid module crashes on start
This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.7 --- pulseaudio (1:8.0-0ubuntu3.7) xenial; urgency=medium * debian/patches/0901-droid-fix-crash-on-module-load.patch: [Fix the crash on module load, this crash was result of patch backported in release 1:8.0-0ubuntu3.3] (LP: #1728791) -- Bhushan Shah Fri, 10 Nov 2017 04:57:42 + ** Changed in: pulseaudio (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1728791 Title: [SRU] pulseaudio-droid module crashes on start Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Xenial: Fix Released Bug description: Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4 [Impact] * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) from using the pulseaudio-modules-droid on android devices. * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates enabled. * Last 3 releases of pulseaudio included multiple patches which modified behavior of pulsecore library but required changes were not made in pulseaudio-module-droid. * This results in crash in pulseaudio-modules-droid #0 init_profile (u=0x59528) at modules/droid/module-droid-card.c:370 #1 module_droid_card_22_LTX_pa__init (m=0x3c3f8) at modules/droid/module-droid-card.c:923 #2 0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 "module-droid-card-22", argument=0x0) at pulsecore/module.c:180 #3 0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, fail=0x3c1f4) at pulsecore/cli-command.c:439 #4 0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at pulsecore/cli-command.c:2134 #5 0xf76f6fc8 in pa_cli_command_execute_line (c=, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155 #6 0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153 #7 0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at pulsecore/ioline.c:269 #8 do_read (l=0x3c208) at pulsecore/ioline.c:337 #9 do_work (l=0x3c208) at pulsecore/ioline.c:386 #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655 #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898 #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, retval=0xfffef1c4) at pulse/mainloop.c:929 #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944 #14 0x000158ca in main (argc=, argv=) at daemon/main.c:1152 [Test Case] * Start pulseaudio * From another session run pacmd * In prompt type load-module module-droid-discover * On ubuntu touch devices, it will crash at startup [Regression Potential] * There is no regression potential for other parts of pulseaudio components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+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 1728791] Re: [SRU] pulseaudio-droid module crashes on start
** Also affects: pulseaudio (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1728791 Title: [SRU] pulseaudio-droid module crashes on start Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Xenial: Fix Committed Bug description: Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4 [Impact] * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) from using the pulseaudio-modules-droid on android devices. * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates enabled. * Last 3 releases of pulseaudio included multiple patches which modified behavior of pulsecore library but required changes were not made in pulseaudio-module-droid. * This results in crash in pulseaudio-modules-droid #0 init_profile (u=0x59528) at modules/droid/module-droid-card.c:370 #1 module_droid_card_22_LTX_pa__init (m=0x3c3f8) at modules/droid/module-droid-card.c:923 #2 0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 "module-droid-card-22", argument=0x0) at pulsecore/module.c:180 #3 0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, fail=0x3c1f4) at pulsecore/cli-command.c:439 #4 0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at pulsecore/cli-command.c:2134 #5 0xf76f6fc8 in pa_cli_command_execute_line (c=, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155 #6 0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153 #7 0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at pulsecore/ioline.c:269 #8 do_read (l=0x3c208) at pulsecore/ioline.c:337 #9 do_work (l=0x3c208) at pulsecore/ioline.c:386 #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655 #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898 #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, retval=0xfffef1c4) at pulse/mainloop.c:929 #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944 #14 0x000158ca in main (argc=, argv=) at daemon/main.c:1152 [Test Case] * Start pulseaudio * From another session run pacmd * In prompt type load-module module-droid-discover * On ubuntu touch devices, it will crash at startup [Regression Potential] * There is no regression potential for other parts of pulseaudio components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+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 1716633] Update Released
The verification of the Stable Release Update for gnome-software 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1716633 Title: Installed, popular and featured snaps are loaded in parallel threads can crash Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Zesty: Triaged Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] GNOME Software has a cache that can be accessed by multiple threads. This can cause GNOME Software to crash. This seems to have been caused by adding support for featured snaps (bug 1663097) as the popular, featured and installed snaps are all requested on different threads. [Test Case] Since this is a random crash there's not a good test case. Could be checked by looking at errors.ubuntu.com crash reports or repeated restarts of GNOME Software to see if it crashes on startup. [Regression Potential] Solution is to add a lock around this cache. Some risk of breaking related code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716633/+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 1722183] Re: When several snaps are being installed, cancelling an installation does not cancel the right one.
This bug was fixed in the package gnome-software - 3.26.1-0ubuntu2.17.10.1 --- gnome-software (3.26.1-0ubuntu2.17.10.1) artful; urgency=medium [ Robert Ancell ] * debian/patches/0001-snap-Don-t-crash-on-unknown-snap-types.patch: - Fix crash when broken snaps installed (LP: #1720442) * debian/patches/0001-snap-Protect-store-cache-with-a-lock.patch: - Fix crash due to multiple threads accessing a cache (LP: #1716633) * debian/patches/0001-snap-Don-t-attempt-to-refine-snaps-without-a-valid-n.patch: - Fix potential crash from invalid snaps * debian/patches/0001-snap-Remove-unused-variables.patch: - Trivial patch added to make above patches apply cleanly * debian/patches/0001-Add-a-cancellable-to-GsApp-objects.patch: * debian/patches/0001-Allow-to-cancel-app-ops-in-the-details-view-that-wer.patch: - Fix cancelling with multiple installs (LP: #1722183) * debian/control: - Add Vcs-Bzr link [ Jeremy Bicha ] * Cherry-pick 0001-Don-t-error-out-for-over-500-results.patch: - Fix empty Addons > Shell Extensions category (LP: #1722809) -- Robert Ancell Wed, 15 Nov 2017 11:58:57 +1300 ** Changed in: gnome-software (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1722183 Title: When several snaps are being installed, cancelling an installation does not cancel the right one. Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Zesty: Triaged Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: gnome-software 3.26.1-0ubuntu1~ppa1 Test Case 1. Install several snaps successively (from the main page, click on a snap, install, go back and repeat several times) 2. Select a snap and cancel the installation Expected result: The snap that is cancelled is cancelled and not another one. Actual result For example, install atom, brackets, discord, wavebox, heroku. Cancel discord and observe that wavebox is cancelled instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 10:42:21 2017 InstallationDate: Installed on 2013-09-03 (1496 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1722183/+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 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software
This bug was fixed in the package gnome-software - 3.26.1-0ubuntu2.17.10.1 --- gnome-software (3.26.1-0ubuntu2.17.10.1) artful; urgency=medium [ Robert Ancell ] * debian/patches/0001-snap-Don-t-crash-on-unknown-snap-types.patch: - Fix crash when broken snaps installed (LP: #1720442) * debian/patches/0001-snap-Protect-store-cache-with-a-lock.patch: - Fix crash due to multiple threads accessing a cache (LP: #1716633) * debian/patches/0001-snap-Don-t-attempt-to-refine-snaps-without-a-valid-n.patch: - Fix potential crash from invalid snaps * debian/patches/0001-snap-Remove-unused-variables.patch: - Trivial patch added to make above patches apply cleanly * debian/patches/0001-Add-a-cancellable-to-GsApp-objects.patch: * debian/patches/0001-Allow-to-cancel-app-ops-in-the-details-view-that-wer.patch: - Fix cancelling with multiple installs (LP: #1722183) * debian/control: - Add Vcs-Bzr link [ Jeremy Bicha ] * Cherry-pick 0001-Don-t-error-out-for-over-500-results.patch: - Fix empty Addons > Shell Extensions category (LP: #1722809) -- Robert Ancell Wed, 15 Nov 2017 11:58:57 +1300 ** Changed in: gnome-software (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1722809 Title: GNOME Shell Extensions subcategory is empty in GNOME Software Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Fix Released Bug description: Impact == In the Ubuntu/GNOME Software app, the Addons > Shell Extensions category is empty. This makes it really difficult to browse for GNOME Shell extensions. Test Case = Install the update. Run Ubuntu/GNOME Software It should prompt your to reload the Software app itself since it has been updated. (Or log out and log back in.) On the home screen, click Addons. Click Shell Extensions. It should show a list of available extensions after a few moments. Regression Potential This minimal patch was cherry-picked from the gnome-3-26 stable branch. Fedora 27 applies the patch. Other Info == The issue is that GNOME Software limited results to 500 but there are more than 800 Shell Extensions now. Maybe in the future, there should be some pagination or organization instead of a massive alphabetical list of extensions. Workaround == You can still look up and install a special GNOME Shell extension if you search for it. Original Bug Report === The Shell Extensions subcategory in GNOME Software is empty. I am using the latest (3.26.1-0ubuntu1) GNOME Software package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1722809/+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 1720442] Re: Crashes if broken snaps installed
This bug was fixed in the package gnome-software - 3.26.1-0ubuntu2.17.10.1 --- gnome-software (3.26.1-0ubuntu2.17.10.1) artful; urgency=medium [ Robert Ancell ] * debian/patches/0001-snap-Don-t-crash-on-unknown-snap-types.patch: - Fix crash when broken snaps installed (LP: #1720442) * debian/patches/0001-snap-Protect-store-cache-with-a-lock.patch: - Fix crash due to multiple threads accessing a cache (LP: #1716633) * debian/patches/0001-snap-Don-t-attempt-to-refine-snaps-without-a-valid-n.patch: - Fix potential crash from invalid snaps * debian/patches/0001-snap-Remove-unused-variables.patch: - Trivial patch added to make above patches apply cleanly * debian/patches/0001-Add-a-cancellable-to-GsApp-objects.patch: * debian/patches/0001-Allow-to-cancel-app-ops-in-the-details-view-that-wer.patch: - Fix cancelling with multiple installs (LP: #1722183) * debian/control: - Add Vcs-Bzr link [ Jeremy Bicha ] * Cherry-pick 0001-Don-t-error-out-for-over-500-results.patch: - Fix empty Addons > Shell Extensions category (LP: #1722809) -- Robert Ancell Wed, 15 Nov 2017 11:58:57 +1300 ** Changed in: gnome-software (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1720442 Title: Crashes if broken snaps installed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] GNOME Software crashes if a broken snap is installed. [Test Case] 1. Create and install a local snap: $ mkdir -p /tmp/broken-snap/meta $ printf "name: broken-snap\nversion: 1\n" > /tmp/broken-snap/meta/snap.yaml $ sudo snap try /tmp/broken-snap 2. Break the snap $ rm /tmp/broken-snap/meta/snap.yaml 3. Confirm the snap is broken: $ snap list Name VersionRev Developer Notes broken-snap x1 try,broken 4. Restart gnome-software $ killall gnome-software 5. Open GNOME Software and go to installed tab. Wait for items to load. Expected result: Installed snaps are shown Observed result: GNOME Software crashes. [Regression Potential] Fix is to handle fields missing in broken snaps. Some risk of breaking related code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1720442/+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 1722809] Update Released
The verification of the Stable Release Update for gnome-software 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1722809 Title: GNOME Shell Extensions subcategory is empty in GNOME Software Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Fix Released Bug description: Impact == In the Ubuntu/GNOME Software app, the Addons > Shell Extensions category is empty. This makes it really difficult to browse for GNOME Shell extensions. Test Case = Install the update. Run Ubuntu/GNOME Software It should prompt your to reload the Software app itself since it has been updated. (Or log out and log back in.) On the home screen, click Addons. Click Shell Extensions. It should show a list of available extensions after a few moments. Regression Potential This minimal patch was cherry-picked from the gnome-3-26 stable branch. Fedora 27 applies the patch. Other Info == The issue is that GNOME Software limited results to 500 but there are more than 800 Shell Extensions now. Maybe in the future, there should be some pagination or organization instead of a massive alphabetical list of extensions. Workaround == You can still look up and install a special GNOME Shell extension if you search for it. Original Bug Report === The Shell Extensions subcategory in GNOME Software is empty. I am using the latest (3.26.1-0ubuntu1) GNOME Software package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1722809/+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 1716633] Re: Installed, popular and featured snaps are loaded in parallel threads can crash
This bug was fixed in the package gnome-software - 3.26.1-0ubuntu2.17.10.1 --- gnome-software (3.26.1-0ubuntu2.17.10.1) artful; urgency=medium [ Robert Ancell ] * debian/patches/0001-snap-Don-t-crash-on-unknown-snap-types.patch: - Fix crash when broken snaps installed (LP: #1720442) * debian/patches/0001-snap-Protect-store-cache-with-a-lock.patch: - Fix crash due to multiple threads accessing a cache (LP: #1716633) * debian/patches/0001-snap-Don-t-attempt-to-refine-snaps-without-a-valid-n.patch: - Fix potential crash from invalid snaps * debian/patches/0001-snap-Remove-unused-variables.patch: - Trivial patch added to make above patches apply cleanly * debian/patches/0001-Add-a-cancellable-to-GsApp-objects.patch: * debian/patches/0001-Allow-to-cancel-app-ops-in-the-details-view-that-wer.patch: - Fix cancelling with multiple installs (LP: #1722183) * debian/control: - Add Vcs-Bzr link [ Jeremy Bicha ] * Cherry-pick 0001-Don-t-error-out-for-over-500-results.patch: - Fix empty Addons > Shell Extensions category (LP: #1722809) -- Robert Ancell Wed, 15 Nov 2017 11:58:57 +1300 ** Changed in: gnome-software (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1716633 Title: Installed, popular and featured snaps are loaded in parallel threads can crash Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Zesty: Triaged Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] GNOME Software has a cache that can be accessed by multiple threads. This can cause GNOME Software to crash. This seems to have been caused by adding support for featured snaps (bug 1663097) as the popular, featured and installed snaps are all requested on different threads. [Test Case] Since this is a random crash there's not a good test case. Could be checked by looking at errors.ubuntu.com crash reports or repeated restarts of GNOME Software to see if it crashes on startup. [Regression Potential] Solution is to add a lock around this cache. Some risk of breaking related code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716633/+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 1720442] Update Released
The verification of the Stable Release Update for gnome-software 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1720442 Title: Crashes if broken snaps installed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] GNOME Software crashes if a broken snap is installed. [Test Case] 1. Create and install a local snap: $ mkdir -p /tmp/broken-snap/meta $ printf "name: broken-snap\nversion: 1\n" > /tmp/broken-snap/meta/snap.yaml $ sudo snap try /tmp/broken-snap 2. Break the snap $ rm /tmp/broken-snap/meta/snap.yaml 3. Confirm the snap is broken: $ snap list Name VersionRev Developer Notes broken-snap x1 try,broken 4. Restart gnome-software $ killall gnome-software 5. Open GNOME Software and go to installed tab. Wait for items to load. Expected result: Installed snaps are shown Observed result: GNOME Software crashes. [Regression Potential] Fix is to handle fields missing in broken snaps. Some risk of breaking related code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1720442/+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 1722183] Update Released
The verification of the Stable Release Update for gnome-software 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1722183 Title: When several snaps are being installed, cancelling an installation does not cancel the right one. Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Zesty: Triaged Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: gnome-software 3.26.1-0ubuntu1~ppa1 Test Case 1. Install several snaps successively (from the main page, click on a snap, install, go back and repeat several times) 2. Select a snap and cancel the installation Expected result: The snap that is cancelled is cancelled and not another one. Actual result For example, install atom, brackets, discord, wavebox, heroku. Cancel discord and observe that wavebox is cancelled instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 10:42:21 2017 InstallationDate: Installed on 2013-09-03 (1496 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1722183/+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 1736603] [NEW] Port ibus-chewing to gtk3
Public bug reported: gtk3 was declared stable in September 2016 with the gtk 3.22 release. ibus-chewing should switch to gtk3. ** Affects: ibus-chewing (Ubuntu) Importance: Undecided Status: New ** Tags: bionic gtk2-demotion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-chewing in Ubuntu. https://bugs.launchpad.net/bugs/1736603 Title: Port ibus-chewing to gtk3 Status in ibus-chewing package in Ubuntu: New Bug description: gtk3 was declared stable in September 2016 with the gtk 3.22 release. ibus-chewing should switch to gtk3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-chewing/+bug/1736603/+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 1736604] [NEW] Port ibus-unikey to gtk3
Public bug reported: gtk3 was declared stable in September 2016 with the gtk 3.22 release. ibus-unikey should switch to gtk3. ** Affects: ibus-unikey (Ubuntu) Importance: Undecided Status: New ** Tags: bionic gtk2-demotion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-unikey in Ubuntu. https://bugs.launchpad.net/bugs/1736604 Title: Port ibus-unikey to gtk3 Status in ibus-unikey package in Ubuntu: New Bug description: gtk3 was declared stable in September 2016 with the gtk 3.22 release. ibus-unikey should switch to gtk3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1736604/+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 1736605] [NEW] Port gtk-im-libthai to gtk3
Public bug reported: gtk3 was declared stable in September 2016 with the gtk 3.22 release. gtk-im-libthai should switch to gtk3. ** Affects: gtk-im-libthai (Ubuntu) Importance: Undecided Status: New ** Tags: bionic gtk2-demotion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk-im-libthai in Ubuntu. https://bugs.launchpad.net/bugs/1736605 Title: Port gtk-im-libthai to gtk3 Status in gtk-im-libthai package in Ubuntu: New Bug description: gtk3 was declared stable in September 2016 with the gtk 3.22 release. gtk-im-libthai should switch to gtk3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk-im-libthai/+bug/1736605/+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 1736525] Re: [snap] shell looses track of currently running app when snapd updates it to a newer revision
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1736525 Title: [snap] shell looses track of currently running app when snapd updates it to a newer revision Status in chromium-browser package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: This has been reported by at least two users for the libreoffice and chromium snaps. See https://forum.snapcraft.io/t/call-for-testing- libreoffice-5-4-3/2935/6: « My LO just refreshed…I had a document open and the Ubuntu Dock seems to think it’s no longer open even though it is (no orange pip) Also when I tried to open that file it said I had it open and it was ‘locked for editing’, rather than just refocusing on the window I have open. I then got this error when trying to close/save the file: saving the document file:///home/adam/snap/libreoffice/43/.config/libreoffice/4/user/basic/script.xlc: General Error. General input/output error. Presumably this is because the instance I have open is revision 43 and the new one is 44 that Ubuntu Dock is trying to launch from, but LO should ‘just work’ on refreshes. Given refreshes are effectively silent, ordinary users will be confused as to what’s going on here. How could the experience be made better? How can the system recognize that revision 43 is the one that’s open and therefore not try and launch revision 44 whilst revision 43 is open? » Apparently, apps that register as a gapplication don't have the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1736525/+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 1736525] Re: [snap] shell looses track of currently running app when snapd updates it to a newer revision
Status changed to 'Confirmed' because the bug affects multiple users. ** 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1736525 Title: [snap] shell looses track of currently running app when snapd updates it to a newer revision Status in chromium-browser package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: This has been reported by at least two users for the libreoffice and chromium snaps. See https://forum.snapcraft.io/t/call-for-testing- libreoffice-5-4-3/2935/6: « My LO just refreshed…I had a document open and the Ubuntu Dock seems to think it’s no longer open even though it is (no orange pip) Also when I tried to open that file it said I had it open and it was ‘locked for editing’, rather than just refocusing on the window I have open. I then got this error when trying to close/save the file: saving the document file:///home/adam/snap/libreoffice/43/.config/libreoffice/4/user/basic/script.xlc: General Error. General input/output error. Presumably this is because the instance I have open is revision 43 and the new one is 44 that Ubuntu Dock is trying to launch from, but LO should ‘just work’ on refreshes. Given refreshes are effectively silent, ordinary users will be confused as to what’s going on here. How could the experience be made better? How can the system recognize that revision 43 is the one that’s open and therefore not try and launch revision 44 whilst revision 43 is open? » Apparently, apps that register as a gapplication don't have the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1736525/+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 1735912] Re: Firefox reliably crashes on apt upgrade
This happens all the time on my main Ubuntu installation and is not specific to the live environment. I only demonstrated it in the live environment for easy reproducibility, and to show it isn’t some crazy misconfiguration of my specific installation. ** Changed in: firefox (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1735912 Title: Firefox reliably crashes on apt upgrade Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: 1. kvm -cdrom ubuntu-17.10-desktop-amd64.iso -m 4096 2. Select “Try Ubuntu”. 3. Start Firefox. 4. Start Software Updater; uncheck everything except Firefox Web Browser; select “Install Now”. 5. When update finishes, switch back to Firefox and go to www.google.com. Firefox immediately crashes. (This seems to happen after every recent Firefox update, not just 56 to 57.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1735912/+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 1736595] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de
Public bug reported: the app do not install ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 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 Date: Tue Dec 5 17:13:20 2017 ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote libsane1:i386 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 tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote 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/1736595 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: the app do not install ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 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 Date: Tue Dec 5 17:13:20 2017 ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote libsane1:i386 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 tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras instâncias do pacote 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/1736595/+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 1271358] Re: Update to 3.18 (remove controls needed for Unity and other desktops)
I looked into this today. The .desktop for the preferences dialog in Ubuntu's vino 3.8 has OnlyShowIn=GNOME;Unity; set so the removed preferences dialog really only affects Unity. If the removed preferences dialog is not a blocker, we are good with merging vino 3.22 with Debian. The only remaining Ubuntu diff is enabling the system miniupnpc patch. That patch was disabled in Debian in 2012 with this message: "Disable 05_use-system-miniupnpc.patch for now, until we have a patch that is ready to be sent upstream and the Debian maintainer of miniupnpc has learned how to maintain a library package." (The patch forces using the system miniupnpc library instead of making it optional which presumably makes it less interesting to upstream.) I started a community topic for this update request at https://community.ubuntu.com/t/update-vino-to-current-version-affects-unity/2537 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1271358 Title: Update to 3.18 (remove controls needed for Unity and other desktops) Status in vino package in Ubuntu: Triaged Bug description: Update to 3.16. A big change in this release is to remove the preferences dialog, not sure if this is a problem for us. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1271358/+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 1736232] Re: GNOME Software shows U1 login for snaps
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial ** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty -- 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/1736232 Title: GNOME Software shows U1 login for snaps 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 Status in gnome-software source package in Bionic: Fix Released Bug description: As I understood it, GNOME Software is no longer supposed to be asking for U1 logins when installing snaps. I just did a clean up to date install of 16.04.3 and tried launching G-S and it asked me for a U1 login. Steps to reproduce: Install 16.04.3 Update to latest software in the repo Open Ubuntu Software Click the "hiri" banner Click install button Expected behaviour:- Policykit login box appears Actual behaviour:- Ubuntu One login/sign up box appears ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 4 19:56:34 2017 InstallationDate: Installed on 2017-12-04 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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/1736232/+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 1736525] Re: [snap] shell looses track of currently running app when snapd updates it to a newer revision
I was able to reproduce the issue with the chromium snap, by ensuring that the chromium icon was pinned (favourited) to the dock first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1736525 Title: [snap] shell looses track of currently running app when snapd updates it to a newer revision Status in chromium-browser package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: This has been reported by at least two users for the libreoffice and chromium snaps. See https://forum.snapcraft.io/t/call-for-testing- libreoffice-5-4-3/2935/6: « My LO just refreshed…I had a document open and the Ubuntu Dock seems to think it’s no longer open even though it is (no orange pip) Also when I tried to open that file it said I had it open and it was ‘locked for editing’, rather than just refocusing on the window I have open. I then got this error when trying to close/save the file: saving the document file:///home/adam/snap/libreoffice/43/.config/libreoffice/4/user/basic/script.xlc: General Error. General input/output error. Presumably this is because the instance I have open is revision 43 and the new one is 44 that Ubuntu Dock is trying to launch from, but LO should ‘just work’ on refreshes. Given refreshes are effectively silent, ordinary users will be confused as to what’s going on here. How could the experience be made better? How can the system recognize that revision 43 is the one that’s open and therefore not try and launch revision 44 whilst revision 43 is open? » Apparently, apps that register as a gapplication don't have the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1736525/+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 1736586] [NEW] machine wakes immediately after /usr/sbin/pm-suspend
Public bug reported: pm-suspend has stopped working after recent apt upgrade. Instead of suspending, it goes through the motions but then restarts again. Then only issue I can see in the dmesg out put is related to ahci :00:1f.2: port does not support device sleep ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pm-utils 1.4.1-16 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: MATE Date: Tue Dec 5 15:52:01 2017 InstallationDate: Installed on 2016-09-08 (453 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (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 pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1736586 Title: machine wakes immediately after /usr/sbin/pm-suspend Status in pm-utils package in Ubuntu: New Bug description: pm-suspend has stopped working after recent apt upgrade. Instead of suspending, it goes through the motions but then restarts again. Then only issue I can see in the dmesg out put is related to ahci :00:1f.2: port does not support device sleep ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pm-utils 1.4.1-16 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: MATE Date: Tue Dec 5 15:52:01 2017 InstallationDate: Installed on 2016-09-08 (453 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1736586/+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 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
The crash always happens when I enable the Arc Menu extension for Gnome Shell or after opening the app grid. I've created a bug report about it with a symbolic stacktrace here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716068 I'm guessing that the app icon code in Gnome Shell is causing some sort of error. I've noticed that the error stops happening if I use Gnome Shell 3.26 (in Ubuntu 17.10+) so perhaps the new Javascript interpreter fixed it. Still would be great to fix the issue in Ubuntu 16.04 since it's an LTS release which will be supported until 2021. -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() Status in gnome-shell package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 Version table: *** 3.18.5-0ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages Happened during update of these packages Start-Date: 2017-07-24 16:09:37 Commandline: apt-get -y install imagemagick imagemagick-6.q16 imagemagick-common libimage-magick-perl libimage-magick-q16-perl libmagick++-6.q16-5v5 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra libmagickwand-6.q16-2 perlmagick xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy Upgrade: libimage-magick-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xorg-core:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), libimage-magick-q16-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xephyr:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), perlmagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8) End-Date: 2017-07-24 16:12:37 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid next size (fast): 0x05eed540 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jul 24 16:11:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1496068513 InstallationDate: Installed on 2014-10-24 (1004 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/chris ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7cec07de98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7f7cec07df10 "free(): invalid next size (fast)", action=3) at malloc.c:5006 _int_free (av=, p=, have_lock=0) at malloc.c:3867 __GI___libc_free (mem=) at malloc.c:2968 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid next size (fast): 0x05eed540 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+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
This was using Evince 3.24.0 on Ubuntu 17.10. -- 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: New 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 1736583] [NEW] Evince annotations lost on save
Public bug reported: 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. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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: New 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 1728072] [libreoffice/artful] possible regression found
As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of libreoffice from artful- proposed was performed and bug 1734132 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and add the tag "bot- stop-nagging" to bug 1734132 (not this bug). Thanks! ** Tags added: verification-failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1728072 Title: [SRU] libreoffice 5.4.2 for artful Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice-l10n package in Ubuntu: Fix Committed Status in libreoffice source package in Artful: Fix Released Status in libreoffice-l10n source package in Artful: Fix Released Bug description: [Impact] * LibreOffice 5.4.2 is the second bugfix release of the fresh 5.4 line, after 5.4.1 (currently in 17.10). For a list of fixed bugs compared to 5.4.1 see the list of bugs fixed in RC1 and RC2: https://wiki.documentfoundation.org/Releases/5.4.2/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/5.4.2/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. * Libreoffice 5.4.2 (RC2, which is effectively the final release) has been available for users to test since 2017-10-04 in the official "LibreOffice Pre-Releases" PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice- prereleases/+packages). [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. The release went through 2 release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A new release with more than 100 bug fixes always carries the potential for introducing regressions, even though it's a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1728072/+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 1736578] Re: package policykit-1 0.105-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1736578 Title: package policykit-1 0.105-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: instalação de impressora ProblemType: Package DistroRelease: Ubuntu 15.04 Package: policykit-1 0.105-8ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Sat Dec 2 13:34:12 2017 DuplicateSignature: package:policykit-1:0.105-8ubuntu5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-22 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: policykit-1 Title: package policykit-1 0.105-8ubuntu5 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/policykit-1/+bug/1736578/+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 1736578] [NEW] package policykit-1 0.105-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: instalação de impressora ProblemType: Package DistroRelease: Ubuntu 15.04 Package: policykit-1 0.105-8ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Sat Dec 2 13:34:12 2017 DuplicateSignature: package:policykit-1:0.105-8ubuntu5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-22 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: policykit-1 Title: package policykit-1 0.105-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1736578 Title: package policykit-1 0.105-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: instalação de impressora ProblemType: Package DistroRelease: Ubuntu 15.04 Package: policykit-1 0.105-8ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Sat Dec 2 13:34:12 2017 DuplicateSignature: package:policykit-1:0.105-8ubuntu5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-22 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: policykit-1 Title: package policykit-1 0.105-8ubuntu5 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/policykit-1/+bug/1736578/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
on Ubuntu 17.04 am seeing high CPU upon launching Chrome 63.0.3239.70-1 however after about 60 seconds it finishes and CPU usage returns to normal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1736525] Re: [snap] shell looses track of currently running app when snapd updates it to a newer revision
I've tried this, but I can't reproduce here... Manually refreshing from stable to edge, for example, it works as expected. Both with chromium and lo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1736525 Title: [snap] shell looses track of currently running app when snapd updates it to a newer revision Status in chromium-browser package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: This has been reported by at least two users for the libreoffice and chromium snaps. See https://forum.snapcraft.io/t/call-for-testing- libreoffice-5-4-3/2935/6: « My LO just refreshed…I had a document open and the Ubuntu Dock seems to think it’s no longer open even though it is (no orange pip) Also when I tried to open that file it said I had it open and it was ‘locked for editing’, rather than just refocusing on the window I have open. I then got this error when trying to close/save the file: saving the document file:///home/adam/snap/libreoffice/43/.config/libreoffice/4/user/basic/script.xlc: General Error. General input/output error. Presumably this is because the instance I have open is revision 43 and the new one is 44 that Ubuntu Dock is trying to launch from, but LO should ‘just work’ on refreshes. Given refreshes are effectively silent, ordinary users will be confused as to what’s going on here. How could the experience be made better? How can the system recognize that revision 43 is the one that’s open and therefore not try and launch revision 44 whilst revision 43 is open? » Apparently, apps that register as a gapplication don't have the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1736525/+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 1306843] Re: Lenovo X230 Mute Button Does Not Mute Sound
Also not work with Kernel 4.10 Kubuntu 16.04 -- 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/1306843 Title: Lenovo X230 Mute Button Does Not Mute Sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 updated as on 4/11/2014 Action: Listen to audio, Press mute button on keyboard Expected Result: Mute indicator displays, sound is muted. Actual Result: Mute indicator displays, sound is not muted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cprofitt 1988 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 11 20:18:40 2014 InstallationDate: Installed on 2014-03-16 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140315) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [232036U, Realtek ALC269VC, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET32WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 232036U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET32WW(1.12):bd05/30/2012:svnLENOVO:pn232036U:pvrThinkPadX230:rvnLENOVO:rn232036U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 232036U dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1306843/+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 1732878] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
** Tags added: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1732878 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell crashed with signal 5 in g_log_default_handler() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Nov 16 06:57:59 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-11-14 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2017-11-15 (1 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732878/+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 1736573] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1732878 *** https://bugs.launchpad.net/bugs/1732878 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 #1732878, 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/1736573/+attachment/5018898/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1736573/+attachment/5018900/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1736573/+attachment/5018904/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1736573/+attachment/5018905/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1736573/+attachment/5018906/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1736573/+attachment/5018907/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1736573/+attachment/5018908/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1732878 gnome-shell crashed with signal 5 in g_log_default_handler() ** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736573 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: just booted ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Dec 5 07:47:01 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736573/+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 67435] Re: xterm gives strang warning.
Is this a new bug? On Lubuntu 17.10: $ echo test|xmessage -center -file - Warning: Cannot convert string "vlines2" to type Pixmap Warning: Missing charsets in String to FontSet conversion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/67435 Title: xterm gives strang warning. Status in xterm package in Ubuntu: Fix Released Bug description: I am running fully up to date Dapper on AMD64. when I start an xterm I get the following warning: $ xterm Warning: Cannot convert string "vlines2" to type Pixmap This is new in Dapper, never had the problem in Breezy. Also, the X11 colors are not the same in Dapper as they were in Breezy. I don't know if there's a corelation. I am fully available to help solve this. Always supporting Ubuntu and Free software, GF. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/67435/+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 789472] Re: libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev
This bug was fixed in the package libgpod - 0.8.3-11 --- libgpod (0.8.3-11) unstable; urgency=medium * QA upload. * debian/control: Update according to pkgconfig files - Have libpod-cil-dev depend on libgtk2.0-cil-dev - Don't have libgpod-dev depend on libgtk2.0-dev (Closes: #628194) (LP: #789472) -- Jeremy Bicha Mon, 04 Dec 2017 21:50:10 -0500 ** Changed in: libgpod (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgpod in Ubuntu. https://bugs.launchpad.net/bugs/789472 Title: libgpod should only depend on libgdk-pixbuf2.0-dev, not libgtk2.0-dev Status in libgpod package in Ubuntu: Fix Released Status in libgpod package in Debian: Fix Committed Bug description: libgpod doesn't depend on GTK2, only gdk-pixbuf, which is shared by GTK2 and GTK3. However, building GTK3 applications with ibgpod unnecessarily causes GTK2 development files to be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/789472/+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 411688] Re: pulseaudio floods network with multicast packets
killall pulseaudio didn't fix it, but: # chmod 0600 /usr/lib/pulse-10.0/modules/module-rtp-send.so followed by killall pulseaudio again did and this will doubtless work until the package is updated. I have no idea why this issue popped up today. I haven't made any changes to my sound settings for a while and the timestamp on ~/.gconf/system/pulseaudio/modules/rtp-send is July 2012. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030:
[Desktop-packages] [Bug 1736325] Re: ibus-sunpinyin depends on deprecated python-glade2
** Description changed: - ibus-sunpinyin is one of three packages keeping pygtk2 in Ubuntu main. - (The other two are python-pyperclip and system-config-kickstart.) + ibus-sunpinyin and system-config-kickstart are the only packages keeping + pygtk2 in Ubuntu main. pygtk has been unmaintained upstream since around 2011. The way forward is to port ibus-sunpinyin to use GObject Introspection bindings. This also requires porting to GTK3. For more information on GObject Introspection see: https://wiki.gnome.org/Projects/GObjectIntrospection https://wiki.gnome.org/Projects/PyGObject -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-sunpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1736325 Title: ibus-sunpinyin depends on deprecated python-glade2 Status in ibus-sunpinyin package in Ubuntu: New Bug description: ibus-sunpinyin and system-config-kickstart are the only packages keeping pygtk2 in Ubuntu main. pygtk has been unmaintained upstream since around 2011. The way forward is to port ibus-sunpinyin to use GObject Introspection bindings. This also requires porting to GTK3. For more information on GObject Introspection see: https://wiki.gnome.org/Projects/GObjectIntrospection https://wiki.gnome.org/Projects/PyGObject To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-sunpinyin/+bug/1736325/+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 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
Fix committed in https://gitlab.com/inkscape/inkscape/commit/dae7facca7b1bf5ce99aaf9dc71b2da8b46f56c8 Please test this as I want to back-port the fix to 0.92.x if no issues are found. -- 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/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Fix Released Status in inkscape package in Ubuntu: Fix Released Status in inkscape package in Debian: Fix Released Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+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 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
My plan (if upstream agrees with me) is to add an enum option that will havethe the following possible values: - auto, we'll not show the osk if a physical keyboard was detected - always, always show the keyboard when a text-entry was touched - never, don't show the keyboard in any casen Anyway I'm planning to start working in January. On Tue, Dec 5, 2017 at 3:10 PM, Emile Victor <1723...@bugs.launchpad.net> wrote: > I would settle for having it be disable-able at all times. There is no > reason why it should default to on for a device with a physical > keyboard. > > The desired behaviour would be: > > 1. Detect if there is a physical keyboard > 1a. If there is a physical keyboard, on-screen keyboard defaults to hidden > at all times > 1b. If there isn't, default it to shown. > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1723857 > > Title: > onscreen keyboard appears whenever i touch touchscreen > > Status in GNOME Shell: > Confirmed > Status in gnome-shell package in Ubuntu: > Triaged > Status in gnome-shell source package in Artful: > Triaged > > Bug description: > Impact > == > I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It > is disabled in System Preferences > Universal Access. This didn't happen > in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is > GNOME based. > > Test Case > = > 0. Find a laptop with a touch screen that works. > 1. Settings > Universal Access > Typing > Screen Keyboard = OFF > 2. Touch the screen. > > Regression Potential > > > Workaround > == > https://extensions.gnome.org/extension/1326/block-caribou/ > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=gnome-shell; status=Confirmed; importance=Medium; > assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-shell; > component=main; status=Triaged; importance=High; assignee=andrea.azzarone@ > canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=artful; > sourcepackage=gnome-shell; component=main; status=Triaged; importance=High; > assignee=None; > Launchpad-Bug-Tags: caribou onscreen-keyboard > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: 0atman asnod azzar1 electrosam gillies janitor > jbicha nathanel.titane nick-fellows payneio pjsingh5000 tombuntus vanvugt > w32stuxnet > Launchpad-Bug-Reporter: tom (tombuntus) > Launchpad-Bug-Modifier: Emile Victor (w32stuxnet) > Launchpad-Message-Rationale: Assignee > Launchpad-Message-For: azzar1 > -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+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 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
*working on this in January On Tue, Dec 5, 2017 at 6:49 PM, Andrea Azzarone < andrea.azzar...@canonical.com> wrote: > My plan (if upstream agrees with me) is to add an enum option that will > havethe the following possible values: > - auto, we'll not show the osk if a physical keyboard was detected > - always, always show the keyboard when a text-entry was touched > - never, don't show the keyboard in any casen > > Anyway I'm planning to start working in January. > > On Tue, Dec 5, 2017 at 3:10 PM, Emile Victor <1723...@bugs.launchpad.net> > wrote: > >> I would settle for having it be disable-able at all times. There is no >> reason why it should default to on for a device with a physical >> keyboard. >> >> The desired behaviour would be: >> >> 1. Detect if there is a physical keyboard >> 1a. If there is a physical keyboard, on-screen keyboard defaults to >> hidden at all times >> 1b. If there isn't, default it to shown. >> >> -- >> You received this bug notification because you are a bug assignee. >> https://bugs.launchpad.net/bugs/1723857 >> >> Title: >> onscreen keyboard appears whenever i touch touchscreen >> >> Status in GNOME Shell: >> Confirmed >> Status in gnome-shell package in Ubuntu: >> Triaged >> Status in gnome-shell source package in Artful: >> Triaged >> >> Bug description: >> Impact >> == >> I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. >> It is disabled in System Preferences > Universal Access. This didn't >> happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which >> is GNOME based. >> >> Test Case >> = >> 0. Find a laptop with a touch screen that works. >> 1. Settings > Universal Access > Typing > Screen Keyboard = OFF >> 2. Touch the screen. >> >> Regression Potential >> >> >> Workaround >> == >> https://extensions.gnome.org/extension/1326/block-caribou/ >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions >> >> Launchpad-Notification-Type: bug >> Launchpad-Bug: product=gnome-shell; status=Confirmed; importance=Medium; >> assignee=None; >> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-shell; >> component=main; status=Triaged; importance=High; assignee= >> andrea.azzar...@canonical.com; >> Launchpad-Bug: distribution=ubuntu; distroseries=artful; >> sourcepackage=gnome-shell; component=main; status=Triaged; importance=High; >> assignee=None; >> Launchpad-Bug-Tags: caribou onscreen-keyboard >> Launchpad-Bug-Information-Type: Public >> Launchpad-Bug-Private: no >> Launchpad-Bug-Security-Vulnerability: no >> Launchpad-Bug-Commenters: 0atman asnod azzar1 electrosam gillies janitor >> jbicha nathanel.titane nick-fellows payneio pjsingh5000 tombuntus vanvugt >> w32stuxnet >> Launchpad-Bug-Reporter: tom (tombuntus) >> Launchpad-Bug-Modifier: Emile Victor (w32stuxnet) >> Launchpad-Message-Rationale: Assignee >> Launchpad-Message-For: azzar1 >> > > -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+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 862813] Re: Power Managment settings are being ignored
I use kubuntu 16.04 with 4.10 kernel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: My current power settings are as follows: On Battery: Suspend when inactive for 30 minutes; Suspend when lid is closed When Plugged In: Dont suspend when inactive; dont suspend when lid is closed However, even though my Thinkpad x201 is plugged in, the settings are being ignored and the system is suspending the system after periods of inactivity. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Sep 29 17:33:26 2011 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915.1) MachineType: LENOVO 3626R3U ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4757e1d7-4888-4a33-bfbe-8ec8fd9d19bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET46WW (1.16 ) dmi.board.name: 3626R3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3626R3U:pvrThinkPadX201:rvnLENOVO:rn3626R3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626R3U dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO gnome-power-bugreport: Error: [Errno 2] No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+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 862813] Re: Power Managment settings are being ignored
May be my problem is relative. I use x230 on dock station. On kubuntu power manager "when laptop lid is closed" is set to do nothing "Even when a externnal monitor is connected" is checked but when i close laptop all monitors go to sleep -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: My current power settings are as follows: On Battery: Suspend when inactive for 30 minutes; Suspend when lid is closed When Plugged In: Dont suspend when inactive; dont suspend when lid is closed However, even though my Thinkpad x201 is plugged in, the settings are being ignored and the system is suspending the system after periods of inactivity. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Sep 29 17:33:26 2011 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915.1) MachineType: LENOVO 3626R3U ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4757e1d7-4888-4a33-bfbe-8ec8fd9d19bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET46WW (1.16 ) dmi.board.name: 3626R3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3626R3U:pvrThinkPadX201:rvnLENOVO:rn3626R3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626R3U dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO gnome-power-bugreport: Error: [Errno 2] No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Fix Committed -- 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/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 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: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) 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 () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 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: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) 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 () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+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 1736525] [NEW] [snap] shell looses track of currently running app when snapd updates it to a newer revision
Public bug reported: This has been reported by at least two users for the libreoffice and chromium snaps. See https://forum.snapcraft.io/t/call-for-testing- libreoffice-5-4-3/2935/6: « My LO just refreshed…I had a document open and the Ubuntu Dock seems to think it’s no longer open even though it is (no orange pip) Also when I tried to open that file it said I had it open and it was ‘locked for editing’, rather than just refocusing on the window I have open. I then got this error when trying to close/save the file: saving the document file:///home/adam/snap/libreoffice/43/.config/libreoffice/4/user/basic/script.xlc: General Error. General input/output error. Presumably this is because the instance I have open is revision 43 and the new one is 44 that Ubuntu Dock is trying to launch from, but LO should ‘just work’ on refreshes. Given refreshes are effectively silent, ordinary users will be confused as to what’s going on here. How could the experience be made better? How can the system recognize that revision 43 is the one that’s open and therefore not try and launch revision 44 whilst revision 43 is open? » Apparently, apps that register as a gapplication don't have the issue. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Tags added: snap ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1736525 Title: [snap] shell looses track of currently running app when snapd updates it to a newer revision Status in chromium-browser package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: This has been reported by at least two users for the libreoffice and chromium snaps. See https://forum.snapcraft.io/t/call-for-testing- libreoffice-5-4-3/2935/6: « My LO just refreshed…I had a document open and the Ubuntu Dock seems to think it’s no longer open even though it is (no orange pip) Also when I tried to open that file it said I had it open and it was ‘locked for editing’, rather than just refocusing on the window I have open. I then got this error when trying to close/save the file: saving the document file:///home/adam/snap/libreoffice/43/.config/libreoffice/4/user/basic/script.xlc: General Error. General input/output error. Presumably this is because the instance I have open is revision 43 and the new one is 44 that Ubuntu Dock is trying to launch from, but LO should ‘just work’ on refreshes. Given refreshes are effectively silent, ordinary users will be confused as to what’s going on here. How could the experience be made better? How can the system recognize that revision 43 is the one that’s open and therefore not try and launch revision 44 whilst revision 43 is open? » Apparently, apps that register as a gapplication don't have the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1736525/+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
and another: https://git.gnome.org/browse/gnome-session/tree/gnome-session/gsm-util.c?h=gnome-3-26#n99 ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in d-conf package in Ubuntu: New Status in gnome-session package in Ubuntu: New 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/ubuntu/+source/d-conf/+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 1732878] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
@seb128 - reproducible : yes multiple users affected - the gnome-bug reported is pointing a possible wayland/mutter cause, but my report lp:1736512 is opened with gnome on xorg session. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1732878 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell crashed with signal 5 in g_log_default_handler() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Nov 16 06:57:59 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-11-14 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2017-11-15 (1 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732878/+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 1736512] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1732878 *** https://bugs.launchpad.net/bugs/1732878 ** Description changed: That crash happen after trying to use the driver r8168-dkms (which fully fails) for better performance with that r8168e chipset, instead of the kernel builtin r8169 which set a 576 MTU instead of a supported 1500. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Dec 5 17:14:05 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - + ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/false + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: - ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () - g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () + g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Description changed: That crash happen after trying to use the driver r8168-dkms (which fully fails) for better performance with that r8168e chipset, instead of the kernel builtin r8169 which set a 576 MTU instead of a supported 1500. + + This is with a gnome on xorg login session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Dec 5 17:14:05 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- 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/1736512 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: That crash happen after trying to use the driver r8168-dkms (which fully fails) for better performance with that r8168e chipset, instead of the kernel builtin r8169 which set a 576 MTU instead of a supported 1500. This is with a gnome on xorg login session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Dec 5 17:14:05 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736512/+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 1732878] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
** Tags added: bugpattern-needed -- 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/1732878 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell crashed with signal 5 in g_log_default_handler() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Nov 16 06:57:59 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-11-14 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2017-11-15 (1 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732878/+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 1736512] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1732878 *** https://bugs.launchpad.net/bugs/1732878 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 #1732878, 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/1736512/+attachment/5018834/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1736512/+attachment/5018836/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1736512/+attachment/5018839/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1736512/+attachment/5018840/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1736512/+attachment/5018841/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1736512/+attachment/5018842/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1736512/+attachment/5018843/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1732878 gnome-shell crashed with signal 5 in g_log_default_handler() ** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736512 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: That crash happen after trying to use the driver r8168-dkms (which fully fails) for better performance with that r8168e chipset, instead of the kernel builtin r8169 which set a 576 MTU instead of a supported 1500. This is with a gnome on xorg login session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Dec 5 17:14:05 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736512/+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 1711180] Re: [snap] Ubuntu 17.10 Artful Ardvark shows Black Window, requires "Force Quit"
@Luke: are you still seeing the issue? Could it be that you're running on nvidia hardware with the proprietary drivers? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1711180 Title: [snap] Ubuntu 17.10 Artful Ardvark shows Black Window, requires "Force Quit" Status in chromium-browser package in Ubuntu: Incomplete Bug description: Installed it fine, but Artful Aardvark Ubuntu 17.10 show just a black window. Freezes there, and eventually I am prompted to "Wait" or "Force Quit". If I don't force quit it stays black all day. Here are my results: LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch Distributor ID: Ubuntu Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Codename: artful name: chromium summary: "Chromium web browser, open-source version of Chrome" publisher: osomon contact: olivier.til...@canonical.com description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium notes: private: false confinement: strict devmode: false jailmode:false trymode: false enabled: true broken: false tracking: candidate installed: 60.0.3112.101 (5) 151MB refreshed: 2017-08-15 10:17:57 -0400 EDT channels: stable: – candidate: 60.0.3112.101 (5) 151MB - beta:61.0.3163.39 (1) 151MB - edge:↑ --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode:false trymode: false enabled: true broken: false tracking: stable installed: 16-2.26.14 (2462) 84MB refreshed: 2017-07-20 08:45:34 -0400 EDT channels: stable: 16-2.26.14 (2462) 84MB - candidate: 16-2.27 (2601) 85MB - beta:16-2.27.2(2677) 85MB - edge:16-2.27.1+git322.46fa975 (2671) 86MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1711180/+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
Here's another: https://git.gnome.org/browse/dconf/tree/service/dconf-gvdb-utils.c#n177 https://git.gnome.org/browse/dconf/tree/service/dconf-keyfile-writer.c#n210 ** Also affects: d-conf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in d-conf package in Ubuntu: New 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/ubuntu/+source/d-conf/+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 1734092] Re: Evince does not print hyphens in some PDF documents (cairo bug)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cairo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1734092
Title:
Evince does not print hyphens in some PDF documents (cairo bug)
Status in cairo:
Fix Released
Status in cairo package in Ubuntu:
Confirmed
Bug description:
In some PDF files, characters like hyphen (minus sign) and others
symbols are not printed in Evince.
According to https://bugs.freedesktop.org/show_bug.cgi?id=94615, the
bug is in version 1.14 of cairo.
The bug was fixed last year in version 1.15 (see
https://cgit.freedesktop.org/cairo/commit/?id=190678f6444ad879847d603c3c9eaf8e9ab6887a).
I've backported the above patch in Ubuntu 16.04 xenial, and it fixes
the bug.
To reproduce the bug (see attached test files) in Ububtu 16.04 (with
libcairo2 1.14.6-1):
1. Create a LaTeX test document (test.tex) with the following content:
\documentclass{article}
\usepackage[T1]{fontenc}
\begin{document}
a-b---
\end{document}
2. Create a test.pdf from test.tex:
pdflatex test.tex
3. Create a cairo pdf output (or print test.pdf on a printer, using
Evince):
pdftocairo test.pdf -pdf test1.pdf
Open test1.pdf with Evince: as you can see, some of the hyphen signs
have disappeared.
To fix the bug, rebuild the cairo deb packages with the attached patch,
install the packages and do (or print test.pdf on a printer, using Evince):
pdftocairo test.pdf -pdf test2.pdf
Now, open test2.pdf with Evince: there is no more missing hyphen sign.
System: Ubuntu 16.04.3 LTS
Packages: libcairo2 (1.14.6-1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1734092/+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 1735979] Re: installing ubuntu-desktop package on ubuntu-server breaks wlan-config in netplan
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1735979 Title: installing ubuntu-desktop package on ubuntu-server breaks wlan-config in netplan Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Status in nplan package in Ubuntu: New Bug description: Installing Ubuntu 17.10 server uses netplan for wlan-configuration, if the wlan-device is the primary device. After this, installing the ubuntu-desktop package leaves the netplan- config untouched, so that the graphical wlan search is unsuccessfull. After deleting the netplan-file in /etc/netplan/ or setting it to network: version: 2 renderer: NetworkManager the graphical wlan search works without further problems. Im not sure, where is the best place to repair this issue. - using network-manager also in server environment - replacing netplan-file while installing ubuntu-desktop - adding some extra config in netplan-directory, so the network-manager support is additive (is this possible?) - remove the netplan-config while installing ubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735979/+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 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages
:-O! It only took eight years, but we did it folks! Hooray! R On Tue, Dec 5, 2017 at 10:23 AM, Jeremy Bicha wrote: > This is finally "fixed" in Ubuntu 18.04 Alpha by having gnome-user-share > depend on the packages it needs. The depends are not a fully functional > Apache install but just an Apache binary and a WebDav server. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (645391). > https://bugs.launchpad.net/bugs/536766 > > Title: > Personal file sharing preferences dialog does not offer to install > needed packages > > Status in Ayatana Design: > Fix Committed > Status in gnome-user-share package in Ubuntu: > Fix Released > > Bug description: > Binary package hint: nautilus > > What happens -> I open the Personal file sharing preferences dialog via > system-preferences or via nautilus, and Im told that the network sharing > feature can not be enabled because the required packages are not on your pc. > I, as a tech user, went to synaptic, found the package, looked for its > recommends and got the functionality. > A normal user wont be able to do so, and so a button to install those > packages is needed for usabilty's sake. > > -- > > Desired resolution: > > - Change the "Sharing Options" text in them Nautilus right click folder > menu to "Local network share" > - Change the 'Share' tab title text in the Nautilus 'Properties' window > to "Local network share" > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ayatana-design/+bug/536766/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/536766 Title: Personal file sharing preferences dialog does not offer to install needed packages Status in Ayatana Design: Fix Committed Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Binary package hint: nautilus What happens -> I open the Personal file sharing preferences dialog via system-preferences or via nautilus, and Im told that the network sharing feature can not be enabled because the required packages are not on your pc. I, as a tech user, went to synaptic, found the package, looked for its recommends and got the functionality. A normal user wont be able to do so, and so a button to install those packages is needed for usabilty's sake. -- Desired resolution: - Change the "Sharing Options" text in them Nautilus right click folder menu to "Local network share" - Change the 'Share' tab title text in the Nautilus 'Properties' window to "Local network share" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/536766/+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
Here is one: http://bazaar.launchpad.net/~ubuntu-desktop/session-migration/trunk/view/head:/src/session-migration.c#L270 ** Package changed: ubuntu => session-migration (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 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/ubuntu/+source/session-migration/+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 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages
This is finally "fixed" in Ubuntu 18.04 Alpha by having gnome-user-share depend on the packages it needs. The depends are not a fully functional Apache install but just an Apache binary and a WebDav server. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/536766 Title: Personal file sharing preferences dialog does not offer to install needed packages Status in Ayatana Design: Fix Committed Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Binary package hint: nautilus What happens -> I open the Personal file sharing preferences dialog via system-preferences or via nautilus, and Im told that the network sharing feature can not be enabled because the required packages are not on your pc. I, as a tech user, went to synaptic, found the package, looked for its recommends and got the functionality. A normal user wont be able to do so, and so a button to install those packages is needed for usabilty's sake. -- Desired resolution: - Change the "Sharing Options" text in them Nautilus right click folder menu to "Local network share" - Change the 'Share' tab title text in the Nautilus 'Properties' window to "Local network share" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/536766/+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 1714821] Re: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1714821 Title: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main) Status in gnome-user-share package in Ubuntu: Fix Released Status in gnome-user-share source package in Artful: Won't Fix Status in gnome-user-share source package in Bionic: Fix Released Bug description: Please sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main) The version of gnome-user-share currently in Ubuntu has 2 features: Bluetooth and WebDav. Ubuntu has installed gnome-user-share by default for many years so that sending and receiving files over Bluetooth works. That feature is now rovided by gnome-bluetooth and gnome-control-center. Therefore, the new version of gnome-user-share dropped the Bluetooth feature. Ubuntu has delayed packaging a newer version of gnome-user-share because it was using unity-control-center which did not support the new Bluetooth feature. Ubuntu has one long-standing diff from Debian. Ubuntu's gnome-user-share package does not actually include the apache dependencies needed for the WebDav feature to work (LP: #536766). Since that's now the only feature in gnome-user-share, dropping this diff makes sense. $ reverse-depends gnome-user-share Reverse-Recommends == * cinnamon-desktop-environment * gnome-control-center Reverse-Depends === * gnome-core [amd64 arm64 armhf i386 ppc64el] * ubuntu-budgie-desktop [amd64 arm64 armhf i386 ppc64el] * ubuntu-gnome-desktop [amd64 arm64 armhf i386 ppc64el] Step 1 -- Ubuntu and Ubuntu Budgie both use gnome-control-center so gnome-user-share is unused for Bluetooth. a. Drop the dependency on gnome-user-share from at least gnome-control-center b. Demote gnome-user-share to universe. Step 2 -- Sync gnome-user-share from Debian. Therefore, I recommend delaying Step 2 until 18.04 development opens. Explanation of the Ubuntu delta and why it can be dropped: * Add git_add_systemd_service.patch: - Backport commit from 3.22 to add systemd user service file for compatibility with gnome-settings-daemon 3.22 * debian/control.in: - Build-Depend on systemd * d/p/0004-revert-remove-help.patch: Bring back the help files for users of gnome-file-share-properties (LP: #1570230) * debian/patches: 0001-revert-remove-preferences-application.patch Fix launching of Prefences from nautilus share bar under unity and patch infobar color (LP: #1562515) * maintscript: remove old xdg autostart file (lp: #1526894) * New Upstream release (LP: #1518813) * Merge with Debian, Remaining changes: - Suggests the apache2.2-bin and libapache2-mod-dnssd binaries rather than depends on those, we want obex push to work out of the box but we don't really need webdav and the apache binaries on the default installation. - debian/patches: + 0001-revert-remove-preferences-application.patch 0002-revert-data-get-started-by-gsd-sharing.patch 0003-revert-webdav-fix-launching-server.patch: Bring back the
[Desktop-packages] [Bug 1735929] [NEW] security problems with incorrect permissions for ubuntu 17.10
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: 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 ** Affects: session-migration (Ubuntu) Importance: High Status: Confirmed -- security problems with incorrect permissions for ubuntu 17.10 https://bugs.launchpad.net/bugs/1735929 You received this bug notification because you are a member of Desktop Packages, which is subscribed to session-migration 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 883769] Re: "personal file sharing" Dialog not at Systemsettings
In Ubuntu 18.04, if gnome-user-share is installed, it can be configured in Settings > Sharing > File Sharing. gnome-user-share itself no longer provides any other dialog or "app". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/883769 Title: "personal file sharing" Dialog not at Systemsettings Status in gnome-user-share package in Ubuntu: Fix Released Bug description: It is hard to find the "personal file sharing" Dialog. At the moment you can find it in the Dash. I think it schould be at the systemsettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/883769/+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 883769] Re: "personal file sharing" Dialog not at Systemsettings
Ubuntu 18.04 is scheduled for release at the end of April 2018. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/883769 Title: "personal file sharing" Dialog not at Systemsettings Status in gnome-user-share package in Ubuntu: Fix Released Bug description: It is hard to find the "personal file sharing" Dialog. At the moment you can find it in the Dash. I think it schould be at the systemsettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/883769/+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 569894] Re: Personal File Sharing manual points to Statup Applications option that isn't there
The latest version of gnome-user-share does not provide any GUI interface itself but is just a service that can be used by a frontend like the Settings > Sharing > File Sharing panel in gnome-control- center. Its help files have been removed too. Therefore, I am closing this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/569894 Title: Personal File Sharing manual points to Statup Applications option that isn't there Status in gnome-user-share: Fix Released Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Binary package hint: system-config-samba In the Personal File Sharing Manual, which I opened from the Help button on the Personal File Sharing Preferences dialog, section "2.1 Starting gnome-user-share" says... "The gnome-user-share service is normally started by gnome-session when you log in. You can change this by opening Preferences ▸ Startup Applications in the System menu, and modifying the 'User Sharing' entry in the list of startup programs." However when I open "Startup Application" there is no 'User Sharing' entry. I'm assuming this is related to bug #531502, but I'm not certain. This is in the Ubuntu 10.04 LTS release candidate. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-share/+bug/569894/+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 497905] Re: Support Application Indicators
The latest version of gnome-user-share does not provide any GUI interface itself but is just a service that can be used by a frontend like the Settings > Sharing > File Sharing panel in gnome-control- center. Therefore, I am closing this bug since it doesn't need appindicator integration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/497905 Title: Support Application Indicators Status in gnome-user-share package in Ubuntu: Fix Released Bug description: This application should be investigated to be ported to use Application Indicators for Lucid - https://edge.launchpad.net/indicator-application affects ubuntu/gnome-user-share tag indicator-application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/497905/+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 497905] Re: Support Application Indicators
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/497905 Title: Support Application Indicators Status in gnome-user-share package in Ubuntu: Fix Released Bug description: This application should be investigated to be ported to use Application Indicators for Lucid - https://edge.launchpad.net/indicator-application affects ubuntu/gnome-user-share tag indicator-application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/497905/+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 956834] Re: gnome-file-share-properties states to receive files over bluetooth in Downloads folder, while it actually receives in Public folder
The latest version of gnome-user-share does not provide any GUI interface itself but is just a service that can be used by a frontend like the Settings > Sharing > File Sharing panel in gnome-control- center. Therefore, I am closing this bug. ** Also affects: mate-user-share (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/956834 Title: gnome-file-share-properties states to receive files over bluetooth in Downloads folder, while it actually receives in Public folder Status in gnome-user-share package in Ubuntu: Fix Released Status in mate-user-share package in Ubuntu: New Bug description: In gnome-file-share-properties, the option to enable receiving files over bluetooth is labeled “Receive files in Downloads folder over Bluetooth”. In fact, however, it receives files in Public folder. I am not exactly sure which is the desired behavior (Downloads folder would actually make sense to me, but one could also argue in favor of Public folder, which can be shared over Bluetooth). But either way, the label and the behavior should match. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-user-share 3.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Fri Mar 16 11:24:16 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1) SourcePackage: gnome-user-share UpgradeStatus: Upgraded to precise on 2012-01-22 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/956834/+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 1118567] Re: Too long dialogue without samba service
The latest version of gnome-user-share does not provide any GUI interface itself but is just a service that can be used by a frontend like the Settings > Sharing > File Sharing panel in gnome-control- center. Therefore, I am closing this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1118567 Title: Too long dialogue without samba service Status in ubuntu-nexus7: New Status in gnome-user-share package in Ubuntu: Fix Released Bug description: gnome-file-share-porperties dialog is too long in a longitudinal direction to manipulate (over 1300px height). How to reproduce. 1. check uninstalled file share service. 2. open dash, input "share" 3. click "Personal File Sharing" Expected happen: - Open dialog in genellaly screen size Acutually happen: - Dialogue expands over screen size Workarownd: - Use "Alt+Drag" or "Alt+Space and drag" to move dialogue ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Fri Feb 8 02:11:08 2013 ExecutablePath: /usr/bin/gnome-file-share-properties InstallationDate: Installed on 2013-01-26 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130126) MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, no user) LANG=ja_JP.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gnome-user-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1118567/+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 1262066] Re: 'Personal File Sharing Preferences' dialog is too large and out of screen bounds
The latest version of gnome-user-share does not provide any GUI interface itself but is just a service that can be used by a frontend like the Settings > Sharing > File Sharing panel in gnome-control- center. Therefore, I am closing this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1262066 Title: 'Personal File Sharing Preferences' dialog is too large and out of screen bounds Status in Ubuntu GNOME: New Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. 'Personal File Sharing Preferences' dialog is too large and out of screen bounds. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 05:50:32 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131217) SourcePackage: gnome-user-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262066/+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 1395301] Re: Inconsistent terminology for Bluetooth pairing
The latest version of gnome-user-share does not provide any GUI interface itself but is just a service that can be used by a frontend like the Settings > Sharing > File Sharing panel in gnome-control- center. Therefore, I am closing this bug. ** Also affects: mate-user-share (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1395301 Title: Inconsistent terminology for Bluetooth pairing Status in gnome-user-share package in Ubuntu: Fix Released Status in mate-user-share package in Ubuntu: New Bug description: The "Personal File Sharing Preferences" window has two sections relating to Bluetooth, and those use different terminology (and user interface features) to describe Bluetooth pairing, both from one another and from the main Bluetooth settings. Under "Share Files over Bluetooth", the requirement for pairing is controlled by a tickbox labelled "Require remote devices to bond with this computer", while under "Receive Files over Bluetooth", it's controlled by a pop-up menu labelled "Accept files:" with options "Always" and "Only for set up devices". As far as I can tell from the docuementation (which disagrees slightly about how the user interface should look), these controls have equivalent effects and control whether files can be respectively browsed or sent by unpaired devices. Meanwhile, the Bluetooth indicator menu uses the phrase "Set-up [sic] New Device", the Bluetooth pane of System Settings describes certain devices as "Paired", and the Ubuntu Desktop Guide explains how to "Connect your computer to a Bluetooth device" but helpfully explains that "This is also called pairing the Bluetooth devices". Personally, I think that both of these settings should be tickboxes, and their labels should both be phrased in terms of "paired" deviced, since that's standard Bluetooth terminology. For consistency with the Ubuntu Desktop Guide, perhaps "connected" would be better (but I think it's less obvious what it means). PS: I've just found the "Control sharing over Bluetooth" page of the Ubuntu Desktop Guide, which adds to the fun by introducing "trusted devices", which are apparently yet another way of talking about paired devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 22 10:53:26 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-file-share-properties InstallationDate: Installed on 2010-06-09 (1626 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: gnome-user-share UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1395301/+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 883769] Re: "personal file sharing" Dialog not at Systemsettings
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/883769 Title: "personal file sharing" Dialog not at Systemsettings Status in gnome-user-share package in Ubuntu: Fix Released Bug description: It is hard to find the "personal file sharing" Dialog. At the moment you can find it in the Dash. I think it schould be at the systemsettings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/883769/+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 1118567] Re: Too long dialogue without samba service
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1118567 Title: Too long dialogue without samba service Status in ubuntu-nexus7: New Status in gnome-user-share package in Ubuntu: Fix Released Bug description: gnome-file-share-porperties dialog is too long in a longitudinal direction to manipulate (over 1300px height). How to reproduce. 1. check uninstalled file share service. 2. open dash, input "share" 3. click "Personal File Sharing" Expected happen: - Open dialog in genellaly screen size Acutually happen: - Dialogue expands over screen size Workarownd: - Use "Alt+Drag" or "Alt+Space and drag" to move dialogue ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Fri Feb 8 02:11:08 2013 ExecutablePath: /usr/bin/gnome-file-share-properties InstallationDate: Installed on 2013-01-26 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130126) MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, no user) LANG=ja_JP.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gnome-user-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1118567/+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 536766] Re: Personal file sharing preferences dialog does not offer to install needed packages
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/536766 Title: Personal file sharing preferences dialog does not offer to install needed packages Status in Ayatana Design: Fix Committed Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Binary package hint: nautilus What happens -> I open the Personal file sharing preferences dialog via system-preferences or via nautilus, and Im told that the network sharing feature can not be enabled because the required packages are not on your pc. I, as a tech user, went to synaptic, found the package, looked for its recommends and got the functionality. A normal user wont be able to do so, and so a button to install those packages is needed for usabilty's sake. -- Desired resolution: - Change the "Sharing Options" text in them Nautilus right click folder menu to "Local network share" - Change the 'Share' tab title text in the Nautilus 'Properties' window to "Local network share" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/536766/+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 569894] Re: Personal File Sharing manual points to Statup Applications option that isn't there
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/569894 Title: Personal File Sharing manual points to Statup Applications option that isn't there Status in gnome-user-share: Fix Released Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Binary package hint: system-config-samba In the Personal File Sharing Manual, which I opened from the Help button on the Personal File Sharing Preferences dialog, section "2.1 Starting gnome-user-share" says... "The gnome-user-share service is normally started by gnome-session when you log in. You can change this by opening Preferences ▸ Startup Applications in the System menu, and modifying the 'User Sharing' entry in the list of startup programs." However when I open "Startup Application" there is no 'User Sharing' entry. I'm assuming this is related to bug #531502, but I'm not certain. This is in the Ubuntu 10.04 LTS release candidate. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-share/+bug/569894/+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 956834] Re: gnome-file-share-properties states to receive files over bluetooth in Downloads folder, while it actually receives in Public folder
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/956834 Title: gnome-file-share-properties states to receive files over bluetooth in Downloads folder, while it actually receives in Public folder Status in gnome-user-share package in Ubuntu: Fix Released Status in mate-user-share package in Ubuntu: New Bug description: In gnome-file-share-properties, the option to enable receiving files over bluetooth is labeled “Receive files in Downloads folder over Bluetooth”. In fact, however, it receives files in Public folder. I am not exactly sure which is the desired behavior (Downloads folder would actually make sense to me, but one could also argue in favor of Public folder, which can be shared over Bluetooth). But either way, the label and the behavior should match. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-user-share 3.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Fri Mar 16 11:24:16 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1) SourcePackage: gnome-user-share UpgradeStatus: Upgraded to precise on 2012-01-22 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/956834/+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 1262066] Re: 'Personal File Sharing Preferences' dialog is too large and out of screen bounds
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1262066 Title: 'Personal File Sharing Preferences' dialog is too large and out of screen bounds Status in Ubuntu GNOME: New Status in gnome-user-share package in Ubuntu: Fix Released Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. 'Personal File Sharing Preferences' dialog is too large and out of screen bounds. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 05:50:32 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131217) SourcePackage: gnome-user-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262066/+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 1395301] Re: Inconsistent terminology for Bluetooth pairing
This bug was fixed in the package gnome-user-share - 3.18.3-2 --- gnome-user-share (3.18.3-2) unstable; urgency=medium * Fully drop Bluetooth from packaging, obsolete since 3.18.0. * Bump Standards-Version to 4.1.0 -- Jeremy Bicha Sun, 03 Sep 2017 10:28:16 -0400 gnome-user-share (3.18.3-1) unstable; urgency=medium * New upstream release. * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged upstream. * Bump debhelper compat level to 10. * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir. -- Michael Biebl Tue, 20 Sep 2016 12:48:27 +0200 gnome-user-share (3.18.2-1) unstable; urgency=medium * New upstream release. * Add Build-Depends on systemd on Linux to get the correct path for the systemd user unit directory. * Add patch to ensure systemd is not mandatory so we can build on non-Linux architectures. * Bump Standards-Version to 3.9.8. * Drop debian/dirs, no longer needed. * Convert from cdbs to dh. * Bump debhelper compatibility level to 9. * Add patch to properly expand paths in gnome-user-share-webdav.desktop. -- Michael Biebl Fri, 02 Sep 2016 18:16:19 +0200 gnome-user-share (3.18.1-1) unstable; urgency=medium * New upstream release. * Bump Standards-Version to 3.9.7 -- Andreas Henriksson Thu, 24 Mar 2016 16:12:22 +0100 gnome-user-share (3.18.0-1) unstable; urgency=medium * New upstream release. - drops ObexPush support which moved to gnome-bluetooth. * debian/rules: drop moving of obexpush autostart files. -- Andreas Henriksson Fri, 25 Sep 2015 10:15:56 +0200 ** Changed in: gnome-user-share (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1395301 Title: Inconsistent terminology for Bluetooth pairing Status in gnome-user-share package in Ubuntu: Fix Released Status in mate-user-share package in Ubuntu: New Bug description: The "Personal File Sharing Preferences" window has two sections relating to Bluetooth, and those use different terminology (and user interface features) to describe Bluetooth pairing, both from one another and from the main Bluetooth settings. Under "Share Files over Bluetooth", the requirement for pairing is controlled by a tickbox labelled "Require remote devices to bond with this computer", while under "Receive Files over Bluetooth", it's controlled by a pop-up menu labelled "Accept files:" with options "Always" and "Only for set up devices". As far as I can tell from the docuementation (which disagrees slightly about how the user interface should look), these controls have equivalent effects and control whether files can be respectively browsed or sent by unpaired devices. Meanwhile, the Bluetooth indicator menu uses the phrase "Set-up [sic] New Device", the Bluetooth pane of System Settings describes certain devices as "Paired", and the Ubuntu Desktop Guide explains how to "Connect your computer to a Bluetooth device" but helpfully explains that "This is also called pairing the Bluetooth devices". Personally, I think that both of these settings should be tickboxes, and their labels should both be phrased in terms of "paired" deviced, since that's standard Bluetooth terminology. For consistency with the Ubuntu Desktop Guide, perhaps "connected" would be better (but I think it's less obvious what it means). PS: I've just found the "Control sharing over Bluetooth" page of the Ubuntu Desktop Guide, which adds to the fun by introducing "trusted devices", which are apparently yet another way of talking about paired devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 22 10:53:26 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-file-share-properties InstallationDate: Installed on 2010-06-09 (1626 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: gnome-user-share UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1395301/+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 1736452] Re: Parts of login screen move when password entered
** Attachment added: "vlcsnap-2017-12-05-14h42m10s666.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736452/+attachment/5018814/+files/vlcsnap-2017-12-05-14h42m10s666.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736452 Title: Parts of lock screen move when password entered Status in gnome-shell package in Ubuntu: New Bug description: Login to Ubuntu 17.10, lock screen. On lock screen look at position of elements on screen Start typing password Expected behaviour Screen elements stay in the same place, with password appearing in the password field Actual behaviour Password field grows vertically, causing everything above it to shift up, and everything below to shift down. See screenshots of before/after, and comparison between the two images. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: Tue Dec 5 14:47:08 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (124 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736452/+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 1736452] [NEW] Parts of lock screen move when password entered
Public bug reported: Login to Ubuntu 17.10, lock screen. On lock screen look at position of elements on screen Start typing password Expected behaviour Screen elements stay in the same place, with password appearing in the password field Actual behaviour Password field grows vertically, causing everything above it to shift up, and everything below to shift down. See screenshots of before/after, and comparison between the two images. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: Tue Dec 5 14:47:08 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (124 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "vlcsnap-2017-12-05-14h42m06s462.png" https://bugs.launchpad.net/bugs/1736452/+attachment/5018809/+files/vlcsnap-2017-12-05-14h42m06s462.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736452 Title: Parts of lock screen move when password entered Status in gnome-shell package in Ubuntu: New Bug description: Login to Ubuntu 17.10, lock screen. On lock screen look at position of elements on screen Start typing password Expected behaviour Screen elements stay in the same place, with password appearing in the password field Actual behaviour Password field grows vertically, causing everything above it to shift up, and everything below to shift down. See screenshots of before/after, and comparison between the two images. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: Tue Dec 5 14:47:08 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (124 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736452/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Likewise thank you @staedtler-przyborski Your workaround in comment #102 worked perfectly for my Epson V350 on Ubuntu 17.10 -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Released Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends 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/1707352/+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 1736452] Re: Parts of login screen move when password entered
** Attachment added: "compare.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736452/+attachment/5018815/+files/compare.png ** Summary changed: - Parts of login screen move when password entered + Parts of lock screen move when password entered ** Description changed: - Login to Ubuntu 17.01, lock screen. + Login to Ubuntu 17.10, lock screen. On lock screen look at position of elements on screen Start typing password Expected behaviour Screen elements stay in the same place, with password appearing in the password field Actual behaviour Password field grows vertically, causing everything above it to shift up, and everything below to shift down. - See screenshots of before/after, and comparison between the two images. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: Tue Dec 5 14:47:08 2017 DisplayManager: gdm3 GsettingsChanges: - b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" - b'org.gnome.shell' b'app-picker-view' b'uint32 1' - b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" + b'org.gnome.shell' b'app-picker-view' b'uint32 1' + b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (124 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1736452 Title: Parts of lock screen move when password entered Status in gnome-shell package in Ubuntu: New Bug description: Login to Ubuntu 17.10, lock screen. On lock screen look at position of elements on screen Start typing password Expected behaviour Screen elements stay in the same place, with password appearing in the password field Actual behaviour Password field grows vertically, causing everything above it to shift up, and everything below to shift down. See screenshots of before/after, and comparison between the two images. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: Tue Dec 5 14:47:08 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (124 days ago)
[Desktop-packages] [Bug 1736449] [NEW] package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: The bug frequently occurs during updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 5 15:44:07 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2016-07-21 (502 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: metacity Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1736449 Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in metacity package in Ubuntu: New Bug description: The bug frequently occurs during updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 5 15:44:07 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2016-07-21 (502 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: metacity Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1736449/+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 1702522] Re: "Software & Updates" string not marked for translation in Ubuntu 17.10
** Changed in: gnome-software Status: Confirmed => Won't Fix -- 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/1702522 Title: "Software & Updates" string not marked for translation in Ubuntu 17.10 Status in GNOME Software: Won't Fix Status in Ubuntu Translations: Fix Released Status in gnome-software package in Ubuntu: Fix Released Bug description: The "Software & Updates" string is not marked for translation in Ubuntu 17.10. https://translations.launchpad.net/ubuntu/zesty/+source/gnome-software/+pots/gnome-software/cs/+translate?search=Software+%26+Updates https://translations.launchpad.net/ubuntu/artful/+source/gnome-software/+pots/gnome-software/cs/+translate?search=Software+%26+Updates To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1702522/+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 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed
Do you think that this error can break my VPN connection ? I do not know if this is the cause. Here a piece of logs : Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Plugin /usr/lib/pppd/2.4.7/nm-l2tp-pppd-plugin.so loaded. Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Plugin pppol2tp.so loaded. Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: pppd 2.4.7 started by root, uid 0 Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: ((src/devices/nm-device.c:1452)): assertion '' failed Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Using interface ppp0 Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Connect: ppp0 <--> Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: [1512482776.5766] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/7) Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: [1512482776.5940] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: [1512482776.5940] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Dez 05 15:06:18 fgarnier-Latitude-5580 NetworkManager[973]: xl2tpd[26237]: control_finish: Connection closed to 194.209.82.248, serial 1 () Dez 05 15:06:18 fgarnier-Latitude-5580 NetworkManager[973]: xl2tpd[26237]: Terminating pppd: sending TERM signal to pid 26238 -- 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/1728378 Title: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed Status in network-manager package in Ubuntu: Confirmed Bug description: This error shows up in boot logs: "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed". Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728378/+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 1392012] Re: [MIR] libteam
** Changed in: libteam (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libteam in Ubuntu. https://bugs.launchpad.net/bugs/1392012 Title: [MIR] libteam Status in libteam package in Ubuntu: New Bug description: Availability: The package is available in universe, built on all architectures. Rationale: The package is a new (Build-)Depends for network-manager, for network device teaming (aka user-space bonding) support. Security: Could not find any related security advisories. Quality assurance: The package is well-maintained in Debian and expected to not require extensive effort to maintain in Ubuntu. UI standards: Not applicable. Dependencies: All build and binary dependencies are in main. Standards compliance: The package meets requirements. Maintenance: The package meets requirements. Background information: libteam is a library for communicating with the netlink kernel layer in order to create bonded interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libteam/+bug/1392012/+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 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
I would settle for having it be disable-able at all times. There is no reason why it should default to on for a device with a physical keyboard. The desired behaviour would be: 1. Detect if there is a physical keyboard 1a. If there is a physical keyboard, on-screen keyboard defaults to hidden at all times 1b. If there isn't, default it to shown. -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
This bug was fixed in the package totem-pl-parser - 3.26.0-1ubuntu2 --- totem-pl-parser (3.26.0-1ubuntu2) bionic; urgency=medium * totem-pl-parser-xspf.c: Avoid large stutters in video playback due to heavy (and unnecessary) disk syncing (LP: #1698270) -- Daniel van Vugt Tue, 31 Oct 2017 17:07:46 +0800 ** Changed in: totem-pl-parser (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GTK+: Confirmed Status in totem-pl-parser: Confirmed Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gtk package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: In Progress Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698270/+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
