Re: [Desktop-packages] [Bug 1725932] Re: gnome-shell freezes randomly
Hi Daniel, After downgrading apport to the version you specified, I was able to submit a new bug 1727603 : https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603 I was notified that this report contains private information and it was automatically selected as private. I changed the visibility to public after going through the .txt files. Please let me know if I should change the bug visibility back to private. Thanks On Thu, Oct 26, 2017 at 2:22 PM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please try this: > > https://wiki.ubuntu.com/Apport#Why_is_apport_disabled_by_default.3F > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1725932 > > Title: > gnome-shell freezes randomly > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > +++UBUNTU RELEASE+++ > > Description: Ubuntu 17.10 > Release: 17.10 > > +++PACKAGE VERSION+++ > > gnome-shell: > Installed: 3.26.1-0ubuntu5 > Candidate: 3.26.1-0ubuntu5 > Version table: >*** 3.26.1-0ubuntu5 500 > 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 > Packages > 100 /var/lib/dpkg/status >3.26.1-0ubuntu4 500 > 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages > > First found this bug when I copied some files into /opt/ via root > access nautilus. After clicking on another window, Ubuntu froze. > > This happened again and possibly recreated by performing root > operations and navigating around gnome. > > Here is something I found interesting in the /var/log/syslog: > > Oct 22 19:03:14 hiruna-ubuntu-XPS kernel: [ 9031.695578] traps: gnome- > shell[1813] general protection ip:7f91e14a6de2 sp:7ffd8ed31070 error:0 > in libgobject-2.0.so.0.5400.1[7f91e1471000+52000] > > This ^ was about the time when it froze the laptop. > > Also it should be noted that this keeps repeating over and over: > > Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: > addSignalMethods is replacing existing [0x564478e7a990 > Gjs_ShowAppsIcon.dash-item-container] connect method > Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: > addSignalMethods is replacing existing [0x564478e7a990 > Gjs_ShowAppsIcon.dash-item-container] disconnect method > Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: > addSignalMethods is replacing existing [0x564478e7a990 > Gjs_ShowAppsIcon.dash-item-container] emit method > Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create > file '/run/user/1000/dconf/user': Permission denied. dconf will not work > properly. > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 60 > times: [ unable to create file '/run/user/1000/dconf/user': Permission > denied. dconf will not work properly.] > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: > [AppIndicatorSupport-DEBUG] Reload detected, destroying old watchdog > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create > file '/run/user/1000/dconf/user': Permission denied. dconf will not work > properly. > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated > 568 times: [ unable to create file '/run/user/1000/dconf/user': Permission > denied. dconf will not work properly.] > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session[1763]: > gnome-session-binary[1763]: dconf-CRITICAL: unable to create file > '/run/user/1000/dconf/user': Permission denied. dconf will not work > properly. > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session-binary[1763]: > dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': > Permission denied. dconf will not work properly. > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create > file '/run/user/1000/dconf/user': Permission denied. dconf will not work > properly. > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 30 > times: [ unable to create file '/run/user/1000/dconf/user': Permission > denied. dconf will not work properly.] > Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create > file '/run/user/1000/dconf/user': Too many open files. dconf will not work > properly. > > > I will attach a syslog below. > > 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 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Oct 22 19:18:47 2017 > DisplayManager: gdm3 > InstallationDate: Installed on 2017-05-24 (151 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago) > > To manage notifications about this bug go to: >
[Desktop-packages] [Bug 1727603] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727603/+attachment/4995934/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727603 Title: gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly Status in gnome-shell package in Ubuntu: New Bug description: This is a re-submission of a bug 1725932, with required information as requested +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. -- How I was able to recreate the crash multiple times: 1. Login 2. Open terminal, run sudo nautilus --> I get this error : Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused (nautilus:4129): Gtk-WARNING **: cannot open display: :0 3. Run su, login and run nautilus 4. Navigate to /opt/ 5. Open a file and close it 6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case) 7. Open the file normally from the non root user --> Immediate freeze ProblemType: Crash 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 00:05:00 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1508395111 InstallationDate: Installed on 2017-05-24 (154 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/hiruna ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: __GI___libc_free (mem=0x5576c018b700) at malloc.c:3141 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_key_file_load_from_file () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in __GI___libc_free() UpgradeStatus: Upgraded to artful on 2017-10-19 (5 days ago) UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727603] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1727603/+attachment/4995935/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727603 Title: gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly Status in gnome-shell package in Ubuntu: New Bug description: This is a re-submission of a bug 1725932, with required information as requested +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. -- How I was able to recreate the crash multiple times: 1. Login 2. Open terminal, run sudo nautilus --> I get this error : Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused (nautilus:4129): Gtk-WARNING **: cannot open display: :0 3. Run su, login and run nautilus 4. Navigate to /opt/ 5. Open a file and close it 6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case) 7. Open the file normally from the non root user --> Immediate freeze ProblemType: Crash 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 00:05:00 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1508395111 InstallationDate: Installed on 2017-05-24 (154 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/hiruna ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: __GI___libc_free (mem=0x5576c018b700) at malloc.c:3141 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_key_file_load_from_file () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in __GI___libc_free() UpgradeStatus: Upgraded to artful on 2017-10-19 (5 days ago) UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727603] gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly
StacktraceTop: __GI___libc_free (mem=mem@entry=0x5576c018b700) at malloc.c:3141 g_free (mem=mem@entry=0x5576c018b700) at ../../../../glib/gmem.c:189 g_key_file_parse_key_value_pair (error=0x7ffedd9767b0, length=, line=, key_file=0x5576c01800f0) at ../../../../glib/gkeyfile.c:1418 g_key_file_parse_line (error=0x7ffedd9767a8, length=, line=, key_file=0x5576c01800f0) at ../../../../glib/gkeyfile.c:1248 g_key_file_flush_parse_buffer (key_file=key_file@entry=0x5576c01800f0, error=error@entry=0x7ffedd976820) at ../../../../glib/gkeyfile.c:1511 -- 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/1727603 Title: gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly Status in gnome-shell package in Ubuntu: New Bug description: This is a re-submission of a bug 1725932, with required information as requested +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. -- How I was able to recreate the crash multiple times: 1. Login 2. Open terminal, run sudo nautilus --> I get this error : Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused (nautilus:4129): Gtk-WARNING **: cannot open display: :0 3. Run su, login and run nautilus 4. Navigate to /opt/ 5. Open a file and close it 6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case) 7. Open the file normally from the non root user --> Immediate freeze ProblemType: Crash 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 00:05:00 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1508395111 InstallationDate: Installed on 2017-05-24 (154 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/hiruna ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: __GI___libc_free (mem=0x5576c018b700) at malloc.c:3141 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_key_file_load_from_file () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in __GI___libc_free() UpgradeStatus: Upgraded to artful on 2017-10-19 (5 days ago) UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727603] Re: gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727603 Title: gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly Status in gnome-shell package in Ubuntu: New Bug description: This is a re-submission of a bug 1725932, with required information as requested +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. -- How I was able to recreate the crash multiple times: 1. Login 2. Open terminal, run sudo nautilus --> I get this error : Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused (nautilus:4129): Gtk-WARNING **: cannot open display: :0 3. Run su, login and run nautilus 4. Navigate to /opt/ 5. Open a file and close it 6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case) 7. Open the file normally from the non root user --> Immediate freeze ProblemType: Crash 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 00:05:00 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1508395111 InstallationDate: Installed on 2017-05-24 (154 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/hiruna ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: __GI___libc_free (mem=0x5576c018b700) at malloc.c:3141 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_key_file_load_from_file () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in __GI___libc_free() UpgradeStatus: Upgraded to artful on 2017-10-19 (5 days ago) UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727603] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727603/+attachment/4995936/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1727603/+attachment/4995923/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** 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/1727603 Title: gnome-shell crashed with signal 5 in __GI___libc_free() | freezes randomly Status in gnome-shell package in Ubuntu: New Bug description: This is a re-submission of a bug 1725932, with required information as requested +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. -- How I was able to recreate the crash multiple times: 1. Login 2. Open terminal, run sudo nautilus --> I get this error : Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused (nautilus:4129): Gtk-WARNING **: cannot open display: :0 3. Run su, login and run nautilus 4. Navigate to /opt/ 5. Open a file and close it 6. Copy that file to my non root desktop (/home/hiruna/Desktop in my case) 7. Open the file normally from the non root user --> Immediate freeze ProblemType: Crash 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 00:05:00 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1508395111 InstallationDate: Installed on 2017-05-24 (154 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/hiruna ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: __GI___libc_free (mem=0x5576c018b700) at malloc.c:3141 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_key_file_load_from_file () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in __GI___libc_free() UpgradeStatus: Upgraded to artful on 2017-10-19 (5 days ago) UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725288] Re: [artful] gnome-shell missing dependency on gir1.2-gdm-1.0
After installing gnoms-shell 3.26.1-0ubuntu5, I verified that I was able to install lightdm then uninstall gdm3 and I was still able to reboot adn log in to the default Ubuntu session. I was unable to uninstall gir1.2-gdm-1.0 without uninstalling gnome-shell. ** Tags removed: verification-needed verification-needed-artful ** Tags added: verification-done verification-done-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/1725288 Title: [artful] gnome-shell missing dependency on gir1.2-gdm-1.0 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Artful: Fix Committed Bug description: Impact == A user who tries to use a different display manager than GDM might easily uninstall a package needed by GNOME Shell and therefore will be unable to log in to the default Ubuntu session or to GNOME or to GNOME Classic Test Case = Before applying the update - sudo apt install lightdm (Choose lightdm when asked which display manager to use) sudo apt remove gdm3 gir1.2-gdm-1.0 (This will uninstall ubuntu-desktop.) Reboot Try to log in to Ubuntu A black screen shows and you will get returned to the log in screen The systemd journal shows this error: gnome-shell: JS ERROR: Error: Requiring Gdm, version none: Typelib file for namespace 'Gdm' (any version) not found After applying the update - You won't be able to uninstall gir1.2-gdm-1.0 without uninstalling gnome-shell. You should be able to log in to Ubuntu now from lightdm if gnome-shell and ubuntu-session are installed. Regression Potential None. This simply restores a dependency that was accidentally not restored earlier. The dependency was dropped in https://launchpad.net/ubuntu/+source/gnome-shell/3.24.2-0ubuntu5 but ultimately it ended up being too difficult to run gnome-shell without gir1.2-gdm-1.0 installed so the Ubuntu Desktop Team decided to use GDM instead of LightDM plus the GDM gir by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
** Changed in: pulseaudio (Ubuntu) Status: In Progress => Triaged -- 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/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Triaged Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724738] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 It happened just after adding a Google account. +1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1724738 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: Confirmed Bug description: g-c-c hangs then crashes after successful adding online account ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 Uname: Linux 4.13.7-041307-generic x86_64 NonfreeKernelModules: 8723bu ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 19 11:13:19 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-08-30 (49 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center background SegvAnalysis: Segfault happened at: 0x7f85caf39b3b:mov0x8(%rax),%rax PC (0x7f85caf39b3b) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: adm cdrom dip i2c lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579174] Re: Close All Terminals not Working as Expected
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1579174/+attachment/4657408/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1579174 Title: Close All Terminals not Working as Expected Status in gnome-terminal package in Ubuntu: New Bug description: The "Close All Terminals" File menu option in Gnome Terminal on an Ubuntu Gnome 16.04 LTS 64-bit live session does not actually close all terminal windows - it only closes the window on which it is selected. To reproduce : 1. Open a new Gnome terminal window. 2. Select "Open Terminal" under the File menu on the first terminal. 3. Select "Close All Terminals" under the File menu on the second terminal. It will only close the second terminal window even though there are two terminal windows open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: GNOME Date: Fri May 6 18:11:52 2016 LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1579174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+attachment/4660325/+files/CurrentDmesg.txt -- 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/1580394 Title: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power Status in alsa-driver package in Ubuntu: New Bug description: I have noticed that when I am on battery power on a Dell Latitude 3340 laptop with headphones plugged in , and there is no audio playing on the computer, there is a consistent static sound that comes through the headphones at a constant volume that is not affected by changing the volume level. I think it may be picking up some kind of analog loopback signal because keyboard presses and disk activity seem to influence the noise. When I plug the power cable into the laptop , the static immediately goes away. I reported this earlier to the upstream Linux Kernel bug tracker, but it seems to be fixed in any distro running a 4.4 kernel or greater that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This make me think it is not a kernel level issue and is found somewhere either in the audio settings on Ubuntu MATE or a pulseaudio bug. I cannot reproduce it on any other 16.04 distro version, but it also affects all the 14.04.4 distros as well. Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent the static. The BIOS Firmware version is up to date. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu-mate 1718 F pulseaudio /dev/snd/controlC0: ubuntu-mate 1718 F pulseaudio CasperVersion: 1.376 CurrentDesktop: MATE Date: Wed May 11 00:43:52 2016 LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717635] Re: Admin authentication prompt not shown first time Install is clicked
@seb128 Happened almost every time. Also observed with other debs such as https://atom.io/download/deb -- 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/1717635 Title: Admin authentication prompt not shown first time Install is clicked Status in gnome-software package in Ubuntu: Incomplete Bug description: To reproduce: As a standard non-admin user, download Google Chrome .deb file and open it with software install. Click the Install button Expected: Authenticate prompt for administrator password, and proceeds with installation on clicking install the first time. Actual: Nothing happens, orange progress seen on button, but no admin prompt first time. Have to click install a second time after this for the admin prompt to be displayed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 16 00:29:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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-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/1717635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"
[Expired for system-config-printer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: system-config-printer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1707193 Title: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'" Status in system-config-printer package in Ubuntu: Expired Bug description: Adding a Hewlett-Packard HP Color LaserJet MFP M476dn as IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'". The error message is unhelpful and can't be copied. The output of the console is > system-config-printer (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_insert_after: assertion 'G_NODE (sibling->user_data)->parent == G_NODE (parent->user_data)' failed (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)' failed (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)' failed (system-config-printer.py:21002): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/newprinter.py", line 4196, in getNPPPD ppd = cups.PPD(f) RuntimeError: ppdOpenFile failed Continuing anyway.. which looks like the error message could be improved dramatically. The same issue happens for Driverless IPP. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: system-config-printer 1.5.7+20160812-0ubuntu9 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jul 28 14:40:51 2017 InstallationDate: Installed on 2015-12-12 (594 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: Gerät für HP_Color_LaserJet_MFP_M476dn: hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5 Gerät für QL-570: usb://Brother/QL-570?serial=F4Z735525 MachineType: LENOVO 20221 PackageArchitecture: all Papersize: a4 PpdFiles: QL-570: Brother QL-570 CUPS v1.1 HP_Color_LaserJet_MFP_M476dn: HP Color LaserJet Pro MFP M476 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: system-config-printer UpgradeStatus: Upgraded to zesty on 2017-05-01 (88 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717635] Re: Admin authentication prompt not shown first time Install is clicked
** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1717635/+attachment/4951011/+files/ProcCpuinfoMinimal.txt -- 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/1717635 Title: Admin authentication prompt not shown first time Install is clicked Status in gnome-software package in Ubuntu: Incomplete Bug description: To reproduce: As a standard non-admin user, download Google Chrome .deb file and open it with software install. Click the Install button Expected: Authenticate prompt for administrator password, and proceeds with installation on clicking install the first time. Actual: Nothing happens, orange progress seen on button, but no admin prompt first time. Have to click install a second time after this for the admin prompt to be displayed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 16 00:29:56 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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-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/1717635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702203] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from _meta_idle_monitor_watch_fire() from g_list_foreach() from
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1702203 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from _meta_idle_monitor_watch_fire() from g_list_foreach() from meta_idle_monitor_xsync_handle_xevent() Status in gnome-shell package in Ubuntu: Confirmed 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.18.5-0ubuntu0.3, the problem page at https://errors.ubuntu.com/problem/280ae858593e624b9a9f1ac0533b7673b2e35a60 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 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/1702203/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723874] Re: First installation of a snap reports an error "Connection reset by peer"
I re-uploaded as 1.24-0ubuntu0.17.10.1~ppa1 as this is the version number that will be used in the artful SRU. -- 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/1723874 Title: First installation of a snap reports an error "Connection reset by peer" Status in gnome-software package in Ubuntu: Triaged Status in snapd-glib package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: New Status in gnome-software source package in Zesty: New Status in snapd-glib source package in Artful: Fix Committed Bug description: Test Case 1. On a freshly installed system when snapd has never been used or initialized before (ie core is not installed) open gnome-software 2. Select a snap 3. Install it 4. Wait until it is installed Actual result At some point gnome-software reports an error "Installation failed: connection reset by peer" It was actually installing core, restarted snapd, then the package. But gnome-software reports the error when snapd is restarted, loses the connection to the daemon and does not track the progress of the installation of the snap package Expected result It reports the installation of core then the installation of the snap package, or report everything in a single transaction but in any case does not report an error since everything is going as expected. Attached the changes that are occurring when the first snap is installed on a fresh system ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 09:26:38 2017 InstallationDate: Installed on 2013-09-03 (1503 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.1-0ubuntu1 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/ubuntu/+source/gnome-software/+bug/1723874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616943] Re: Can't auth against U1 in g-s
** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1616943 Title: Can't auth against U1 in g-s Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in snapd-glib source package in Xenial: Fix Released Status in gnome-software source package in Yakkety: Fix Released Bug description: [Impact] Authentication using Ubuntu One credentials to install/remove snaps always fails. This is due to a behaviour change in snapd (no longer accepts login requests from non-root users). Existing credentials continue to work. [Test Case] 1. Delete any existing credentials by deleting passwords marked "com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse. 2. Start GNOME Software 3. Search for a snap (e.g. "moon-buggy") 4. Install Snap 5. Enter Ubuntu One credentials when prompted Observed result: Dialog says "Incorrect email or password". Expected result: Authentication completes and the snap is installed. [Regression Potential] The solution is to use a new D-Bus service (snapd-login-service) and new library (snapd-glib) to get the Macaroon from snapd. This has some risk of introducing new bugs. The change is minimised (other snapd code paths unchanged) and the alternative is login to be impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616943] Re: Can't auth against U1 in g-s
** Changed in: gnome-software (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1616943 Title: Can't auth against U1 in g-s Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in snapd-glib source package in Xenial: Fix Released Status in gnome-software source package in Yakkety: Fix Released Bug description: [Impact] Authentication using Ubuntu One credentials to install/remove snaps always fails. This is due to a behaviour change in snapd (no longer accepts login requests from non-root users). Existing credentials continue to work. [Test Case] 1. Delete any existing credentials by deleting passwords marked "com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse. 2. Start GNOME Software 3. Search for a snap (e.g. "moon-buggy") 4. Install Snap 5. Enter Ubuntu One credentials when prompted Observed result: Dialog says "Incorrect email or password". Expected result: Authentication completes and the snap is installed. [Regression Potential] The solution is to use a new D-Bus service (snapd-login-service) and new library (snapd-glib) to get the Macaroon from snapd. This has some risk of introducing new bugs. The change is minimised (other snapd code paths unchanged) and the alternative is login to be impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725932] Re: gnome-shell freezes randomly
Please try this: https://wiki.ubuntu.com/Apport#Why_is_apport_disabled_by_default.3F -- 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/1725932 Title: gnome-shell freezes randomly Status in gnome-shell package in Ubuntu: Incomplete Bug description: +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. Here is something I found interesting in the /var/log/syslog: Oct 22 19:03:14 hiruna-ubuntu-XPS kernel: [ 9031.695578] traps: gnome- shell[1813] general protection ip:7f91e14a6de2 sp:7ffd8ed31070 error:0 in libgobject-2.0.so.0.5400.1[7f91e1471000+52000] This ^ was about the time when it froze the laptop. Also it should be noted that this keeps repeating over and over: Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] connect method Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] disconnect method Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] emit method Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 60 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: [AppIndicatorSupport-DEBUG] Reload detected, destroying old watchdog Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 568 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session[1763]: gnome-session-binary[1763]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session-binary[1763]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 30 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Too many open files. dconf will not work properly. I will attach a syslog below. 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 19:18:47 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-24 (151 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725932] Re: gnome-shell freezes randomly
Ugg. Sorry about that. I don't fully understand the Ubuntu policy on that myself, but it did change over night: https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu3.1 You might have some luck by downgrading your apport packages to the previous version first: https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu3/+build/13569366 Again, sorry about that. I need to get in contact with the relevant Canonical staff and ask what the rationale for periodically disabling crash reports is... -- 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/1725932 Title: gnome-shell freezes randomly Status in gnome-shell package in Ubuntu: Incomplete Bug description: +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages First found this bug when I copied some files into /opt/ via root access nautilus. After clicking on another window, Ubuntu froze. This happened again and possibly recreated by performing root operations and navigating around gnome. Here is something I found interesting in the /var/log/syslog: Oct 22 19:03:14 hiruna-ubuntu-XPS kernel: [ 9031.695578] traps: gnome- shell[1813] general protection ip:7f91e14a6de2 sp:7ffd8ed31070 error:0 in libgobject-2.0.so.0.5400.1[7f91e1471000+52000] This ^ was about the time when it froze the laptop. Also it should be noted that this keeps repeating over and over: Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] connect method Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] disconnect method Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: WARNING: addSignalMethods is replacing existing [0x564478e7a990 Gjs_ShowAppsIcon.dash-item-container] emit method Oct 22 19:03:13 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 60 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: [AppIndicatorSupport-DEBUG] Reload detected, destroying old watchdog Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 568 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session[1763]: gnome-session-binary[1763]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-session-binary[1763]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: message repeated 30 times: [ unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Oct 22 19:03:14 hiruna-ubuntu-XPS gnome-shell[1813]: unable to create file '/run/user/1000/dconf/user': Too many open files. dconf will not work properly. I will attach a syslog below. 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 19:18:47 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-24 (151 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1727402] Re: gnome-shell crashed after login
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] -- 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/1727402 Title: gnome-shell crashed after login Status in gnome-shell package in Ubuntu: New Bug description: This is a recurrent crash, which does not have any practical effect, besides the report window appearing after a login. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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: GNOME-Greeter:GNOME Date: Wed Oct 25 15:52:28 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-20 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() 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/1727402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727421] Re: Desktop focus border radius not matching overview panel border radius
** Tags added: visual-quality ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1727421 Title: Desktop focus border radius not matching overview panel border radius Status in gnome-shell package in Ubuntu: New Bug description: When enabling the activities overview, the current thickness/border- radius values of the currently focused desktop conflict with the outer perimeter of the overview panel. Solution: Decrease the focus border thickness and/or enable a border-radius value to the ubuntu.css override for the desktop/window focus border so that both corner roundings match and do not conflict visually. See attached image for details. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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 25 12:11:03 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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/1727421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727210] Re: Totum locks up with 17.10
It seems bug 1720820 is similar. But for the moment this bug is owned by Ernest and is awaiting his reply. ** Also affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New ** Changed in: gstreamer-vaapi (Ubuntu) Status: New => Incomplete ** Summary changed: - Totum locks up with 17.10 + Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1727210 Title: Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo) Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: when trying to play videos in Totum on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo), the timer shows it's playing but there is no video. After about 10 seconds I get the "Video is not responding" "what do you want to do" "wait/force close" window. the only way to close it is to force it closed. Same result with MP4 and FLV videos. totum version= 3.26.0-0ubuntu1 Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1727210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727415] Re: ubuntu dock border radius not matching icon focus border radius
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727415 Title: ubuntu dock border radius not matching icon focus border radius Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: When disabling the dock's full height and straight corner enforcement via dconf-editor, the border radiuses do not coincide and protrude from the inner focus highlight of the icon onto the dock's perimeter. Although not necessarily supported by the official visual guideline (which aims to be Unity-like), all available features and options that can be customised or triggered by a user should be verified and tested for design consistency. Solution: The dock's icon highlight (focus) should have a higher border-radius value to accommodate the dock's corner rounding. See attached image for detail. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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 25 12:00:31 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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-extension-ubuntu-dock/+bug/1727415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727466] Re: ubuntu 17.10 gdm numlockx cannot be activated
** Bug watch added: GNOME Bug Tracker #784774 https://bugzilla.gnome.org/show_bug.cgi?id=784774 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=784774 Importance: Unknown Status: Unknown ** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1727466 Title: ubuntu 17.10 gdm numlockx cannot be activated Status in gdm: Unknown Status in gdm3 package in Ubuntu: Confirmed Bug description: In ubuntu 17.10 i am not able to activate numlock on the login screen. Tried with and without wayland. Cannot get numlockx working as I always did in other *ubuntu's with gdm. /etc/gdm3/Init/Default is not working anymore. is there a way to do it? Guyd To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1727466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics
Thanks. Please try this as a workaround: sudo apt remove mesa-va-drivers ** Tags added: radeon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1720820 Title: Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD Fury graphics card and open source drivers. Video output is just a black frame and crash happens within just a few seconds after video playback starts. Could not reproduce bug on two older Intel laptops with iGPU's where hardware acceleration seemed to work fine under Wayland. Issue is only present on Wayland, not x. I can get hardware accelerated video playback working on Wayland with 'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only way I have found so far. Even in mpv, no other option than vaapi-copy works. gst-play-1.0 outputs the following error: ERROR Internal error: could not render surface for file:///*** ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 totem 3.25.90.1-0ubuntu3 gstreamer1.0-vaapi:amd641.12.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics
Although if you really need hardware acceleration then just use Xorg sessions rather than Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1720820 Title: Totem with gstreamer1.0-vaapi and Wayland crashes on AMD graphics Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD Fury graphics card and open source drivers. Video output is just a black frame and crash happens within just a few seconds after video playback starts. Could not reproduce bug on two older Intel laptops with iGPU's where hardware acceleration seemed to work fine under Wayland. Issue is only present on Wayland, not x. I can get hardware accelerated video playback working on Wayland with 'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only way I have found so far. Even in mpv, no other option than vaapi-copy works. gst-play-1.0 outputs the following error: ERROR Internal error: could not render surface for file:///*** ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 totem 3.25.90.1-0ubuntu3 gstreamer1.0-vaapi:amd641.12.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727395] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] -- 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/1727395 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with signal 5 in _XIOError() ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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: GNOME-Greeter:GNOME Date: Sun Oct 22 00:02:21 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-21 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() 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/1727395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Wayland does not start up
Please run this command to help us collect more information: apport-collect 1727356 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - Wayland does not start up + Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed ** Bug watch added: GNOME Bug Tracker #789489 https://bugzilla.gnome.org/show_bug.cgi?id=789489 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=789489 Importance: Unknown Status: Unknown -- 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/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725062] Re: Network Manager Applet can't connect to VPN, but nmtui does
Anyone filed an upstream bug at https://bugzilla.gnome.org yet? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1725062 Title: Network Manager Applet can't connect to VPN, but nmtui does Status in network-manager-applet package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 Fresh install 2) network-manager-pptp/artful,now 1.2.4-4 amd64 VPN connection, created in network manager can't even turn on - slider goes back to off right after your click on it. Connect via "connect" does nothing too. I've tried to change option - store password/do not store password. No errors shown,except syslog: Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5923] audit: op="connection-activate" uuid="709047eb-3254-419f-a152-0a8ff0c3a04b" name="Schastye" pid=1603 uid=1000 result="success" Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5966] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Started the VPN service, PID 5992 Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6019] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Saw the service appear; activating connection Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6336] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Failed to request VPN secrets #3: No agents were available for this request. Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6347] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: VPN plugin: state changed: stopped (6) If i try to connect to VPN via nmtui - everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type()
** Information type changed from Private to Public ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() + gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers() -- 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/1727365 Title: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers() Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This bug is triggered for me by leaving the system inactive for a time and it happens whether the system settings is set to lock the screen or not, but I can be provoked by locking the screen. At the time when I want to reactivate the system (as I can see on the time stamp on the crash report), something happens and I loose the entire login session and am dropped at the login screen to login anew. This has lead me to believe that this has to do with re-enabling the display. The effect of this bug is that I loose *all* running programs in my session and has to start everything up again, which means that Ubuntu 17.10 is basically unusable for me. For this reason, of course depending on how many people are affected, I think this should be considered a high priority bug. This is a fresh install with no shenanigans except installing a few programs that I needed. I happy to provide any extra information is required and to any kind of testing that might be required as long as I can return to a non- modified system after test. Mandatory info: lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 apt-cache policy gnome-shell gnome-shell: Installeret: 3.26.1-0ubuntu4 Kandidat:3.26.1-0ubuntu4 Versionstabel: *** 3.26.1-0ubuntu4 500 500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 16:11:36 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['workspace-g...@mathematical.coffee.gmail.com', 'commandout...@elken.tdos.gmail.com']" b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-23 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f37ebf9cf80:push %rdx PC (0x7f37ebf9cf80) in non-executable VMA region: 0x7f37ebf99000-0x7f37ec00 rw-p None source "%rdx" ok destination "(%rsp)" (0x7fff6f7a1cb8) ok SegvReason: executing writable VMA None Signal: 11 SourcePackage: gnome-shell StacktraceTop: __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so Title: gnome-shell crashed with SIGSEGV in __bss_start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727330] Re: is not adjusted for natural scrolling in the mouse control panel
Are you using a mouse or the laptop touchpad? If using the touchpad then you'll need to switch on/off natural scrolling for the touchpad and not the mouse. Also, what model laptop are you using? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727330 Title: is not adjusted for natural scrolling in the mouse control panel Status in gnome-shell package in Ubuntu: Incomplete Bug description: is not adjusted for natural scrolling in the mouse control panel. Change the position of the switch does not change the settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:57:58 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727321] Re: drag and drop through the side panel to activate the window is not working.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727321 Title: drag and drop through the side panel to activate the window is not working. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: drag and drop through the side panel to activate the window is not working. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:39:57 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1727321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727322] Re: tasks in the calendar are not added and not synced with Google
** Bug watch added: GNOME Bug Tracker #546088 https://bugzilla.gnome.org/show_bug.cgi?id=546088 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=546088 Importance: Unknown Status: Unknown -- 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/1727322 Title: tasks in the calendar are not added and not synced with Google Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: tasks in calendar (above) are not added and not synced with Google ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:42:20 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome
Also, are you looking at the laptop screens or VGA output? Just need to ask :) -- 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/1727269 Title: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome. This is really just a cosmetic issue. The window edges (mostly only top left) and window buttons were sharper and clearer in Ubuntu 16.04 und the versions before. The rough window egdges do not appear in all windows, it is especially obvious with Firfox. The impression with the buttons is always present. This is apparent in stock Ubuntu 17.10 on various laptops (Thinkpad x220, Acer Aspire 5253, Macbook Pro late 2010). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome
I'm looking at both 16.04 and 17.10 on identical monitors and can't see the problem you're talking about. Can you take screenshots of the issue? Just press PrtScn and then look in your Pictures... ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727269 Title: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome. This is really just a cosmetic issue. The window edges (mostly only top left) and window buttons were sharper and clearer in Ubuntu 16.04 und the versions before. The rough window egdges do not appear in all windows, it is especially obvious with Firfox. The impression with the buttons is always present. This is apparent in stock Ubuntu 17.10 on various laptops (Thinkpad x220, Acer Aspire 5253, Macbook Pro late 2010). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727310] Re: change screen brightness not working
Thanks for the bug report. Can you tell us what model laptop you're using? Also what do you get when you run this command?; ls /sys/class/backlight/ ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727310 Title: change screen brightness not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: changing the screen brightness does not work when you try to change the slider on the toolbar at the top right ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:10:04 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727293] Re: gnome-shell crashed with signal 5 in _XIOError() as soon as my computer finished booting
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] -- 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/1727293 Title: gnome-shell crashed with signal 5 in _XIOError() as soon as my computer finished booting Status in gnome-shell package in Ubuntu: New Bug description: My computer started, and the crash window appeared ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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: GNOME-Greeter:GNOME Date: Tue Oct 24 18:01:54 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-18 (6 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727280] Re: The Dropbox status icon is too small and offers no left- or right-click menu
*** This bug is a duplicate of bug 1723827 *** https://bugs.launchpad.net/bugs/1723827 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1723827, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1723827 App indicator icon size is too small -- 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/1727280 Title: The Dropbox status icon is too small and offers no left- or right- click menu Status in gnome-shell package in Ubuntu: New Bug description: The Dropbox status icon is too small and offers no left- or right- click menu. The size of the icon seems to be about 16px and has no interactive funcionality. That means that Dropbox cannot be configured via the menu and one cannot prevent Dropbox from autostarting. This is the case in stock Ubuntu 17.10 in both the wayland- and xorg- session (Thinkpad x220 and Macbook Pro 2010). The Dropbox status icon should have the same resolution as the other icons in the top-panel, for example the battery indicator, and offer a left- or right-click menu. gnome-shell: Installed: 3.26.1-0ubuntu4 Candidate: 3.26.1-0ubuntu4 Version table: *** 3.26.1-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status nautilus-dropbox: Installed: 2015.10.28-1ubuntu2 Candidate: 2015.10.28-1ubuntu2 Version table: *** 2015.10.28-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu artful/multiverse amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727308] Re: when you try to change the layout for a long time reacts
Do you mean keyboard layout? And can you explain the problem in more detail? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727308 Title: when you try to change the layout for a long time reacts Status in gnome-shell package in Ubuntu: Incomplete Bug description: when you try to change the layout for a long time reacts and uses caps lock to change the size of letters simultaneously with the change of layout. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:06:55 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568490] Re: Can no longer move windows controls to the right (16.04) - gsettings has no effect now
*** This bug is a duplicate of bug 1309942 *** https://bugs.launchpad.net/bugs/1309942 So I notice that the buttons work for chrome windows, but not work for other applications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1568490 Title: Can no longer move windows controls to the right (16.04) - gsettings has no effect now Status in unity-settings-daemon package in Ubuntu: Confirmed Status in unity-tweak-tool package in Ubuntu: Confirmed Bug description: Just installed 16.04 beta2 (plus latest updates), I can no longer move the window controls to the right. On previous ubuntu versions I would use the command # gsettings set org.gnome.desktop.wm.preferences button-layout 'menu:minimize,maximize,close' But this has no effect, neither does 'window controls' section of the unity-tweak-tool any longer - if I choose right nothing happens. If I check the setting with # gsettings list-recursively | grep button-layout I see org.gnome.desktop.wm.preferences button-layout 'menu:minimize,maximize,close' How can I move the window buttons to the right now ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-settings-daemon 15.04.1+16.04.20160209-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 10 11:52:21 2016 InstallationDate: Installed on 2016-04-09 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1568490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721735] Re: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed
I've got an (as yet unmerged) snapd branch to help with this: https://github.com/snapcore/snapd/pull/4055 It got a review yesterday, so should go in the next snapd release. This is basically doing (1), returning a Forbidden error when the user dismisses the dialog. -- 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/1721735 Title: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Artful: Triaged Bug description: With snapd 16-2.28.1 from the candidate channel Test Case 1. With gnome-software, install a snap 2. When the polkit auth dialog is displayed, click "Cancel" Actual result The Ubuntu One authentication dialog is displayed Expected result The polkit authentication dialog is dismissed and the user returns to the main screen of gnome-software. The U1 dialog is not displayed 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: Fri Oct 6 12:05:54 2017 InstallationDate: Installed on 2013-09-03 (1493 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/ubuntu/+source/gnome-software/+bug/1721735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Wayland does not start up
"wayland" is just the bare protocol libraries, so not relevant here. The package you want is one of: gnome-shell mutter gdm3 -- 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/1727356 Title: Wayland does not start up Status in gnome-shell package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Wayland does not start up
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up Status in gnome-shell package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725686] Re: Computer freezes when logging into Ubuntu 17.10 on Wayland
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725686 Title: Computer freezes when logging into Ubuntu 17.10 on Wayland Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I first installed Ubuntu 17.10, I logged into Wayland and it worked fine. There were some minor issues, but it was still functional. However, I started screencasting my computer with Ctrl- Alt-Shift-R, but my computer became very slow and I decided to shut it down. I closed all applications before shutting it down, but forgot to stop the screencast. Now, when I try to log into Ubuntu 17.10 using Wayland, the screen goes gray and my cursor is stuck in the middle of the screen. I can't move my cursor at all and the desktop never actually loads. I can still transition to other ttys, though, by using the Ctrl-Alt-(F key) commands. However, logging into Ubuntu on Xorg or Unity still works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726224] Re: wacom invisible mouse pointer in wayland
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726224 Title: wacom invisible mouse pointer in wayland Status in gnome-shell package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet, which has touch and pen functionality. Controlling the mouse pointer through the touch functionality seems to work fine, but using the stylus produced very strange behaviour, depending the program. - With Firefox there there are two pointers - one that is moving in accordance with the stylus movements, and one stays put at the position, when the stylus movement was detected. - With Darktable the mouse pointer becomes invisible, once it's moved inside of the application window (it registers clicks though). Once the pointer is moved outside of the application window, it appears again. I'm running Ubuntu inside of a wayland session. libwacom2: 0.24-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726497] Re: nautilus crashed with SIGABRT in wl_abort()
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726497 Title: nautilus crashed with SIGABRT in wl_abort() Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: This crash occurred when I was browsing my folders. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 08:55:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () wl_proxy_marshal_array_constructor_versioned () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 wl_proxy_marshal () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGABRT in wl_proxy_marshal_array_constructor_versioned() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1726497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727363] Re: Wayland dock "crash" after thumb (horizontal) scroll
** Package changed: wayland (Ubuntu) => gnome-shell-extension-ubuntu- dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727363 Title: Wayland dock "crash" after thumb (horizontal) scroll Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I'm using Ubuntu 17.10 with 3 monitors (I don't know if this is relevant) I don't know if this is the right place to leave this issue. The problem is very simple to reproduce if you have a Logitech MX Master mouse: if you make a horizontal scroll through the "thumb scroll wheel", the icons on the wayland dock will disappear. To display them again, you need to restart the session. If you tell me where I can pick a log, I'll be happy to provide it. Sorry for my english. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1727363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I have a theory that Bose devices are probably just noticing they've been connected in HSP mode by default and that's when they say "call from". In that case this might be fixed with bug 1720684, so keep an eye on that one. ** Tags added: bose -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1
** Tags added: bose -- 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/1716127 Title: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12,1 Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
OK, I maintain the theory that this is a kernel regression then. When everything worked for you that was kernel 4.10, and now you're on 4.13. Plus the log snippet in comment #2 shows the hang is probably occurring in the call. Please try some older kernels, starting with 4.10... http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D The nvidia driver uses DKMS so should get automatically recompiled for each kernel you install. And in this case even an "old" kernel is pretty recent so nvidia shouldn't have any problem with them. ** Changed in: linux (Ubuntu) Status: Invalid => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Plus the log snippet in comment #2 shows the hang is probably occurring in the kernel. -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721762] Re: Cancelled installation of snap continues
https://github.com/snapcore/snapd/pull/4079 -- 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/1721762 Title: Cancelled installation of snap continues Status in gnome-software package in Ubuntu: In Progress Status in snapd-glib package in Ubuntu: Fix Committed Status in gnome-software source package in Artful: In Progress Status in snapd-glib source package in Artful: New Status in gnome-software source package in Bionic: In Progress Status in snapd-glib source package in Bionic: Fix Committed Bug description: with core candidate: 16-2.28.1 Test Case 1. Install a snap package 2. When the installation is ongoing, press Cancel 3. Verify that installation stopped (snap changes then snap change ID) Expected result Installation is cancelled Actual result It continues in the background and gnome-software shows the wrong state 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: Fri Oct 6 13:38:01 2017 InstallationDate: Installed on 2014-07-23 (1170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: Upgraded to artful on 2017-06-13 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725062] Re: Network Manager Applet can't connect to VPN, but nmtui does
Tomas, I forgot to mention - workaround works for me only on saved connection. You need to create it first,save it and then choose 'save password for all users' option. If you change anything else after choosing 'save password..' option, the problem may be persist. Also i assume your problem is a little bit broader. If I right, and you need PPTP connection for RDP sessions - it won't work out of the box in Ubuntu. You need to upgrade remmina from ppa, and check 'send echo packets PPP' and check 'use these connection for these network resourses only'. Aslo i recommend to try to connect via 'nmtui' the way i mentioned above, if my workaround not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1725062 Title: Network Manager Applet can't connect to VPN, but nmtui does Status in network-manager-applet package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 Fresh install 2) network-manager-pptp/artful,now 1.2.4-4 amd64 VPN connection, created in network manager can't even turn on - slider goes back to off right after your click on it. Connect via "connect" does nothing too. I've tried to change option - store password/do not store password. No errors shown,except syslog: Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5923] audit: op="connection-activate" uuid="709047eb-3254-419f-a152-0a8ff0c3a04b" name="Schastye" pid=1603 uid=1000 result="success" Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5966] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Started the VPN service, PID 5992 Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6019] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Saw the service appear; activating connection Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6336] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Failed to request VPN secrets #3: No agents were available for this request. Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6347] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: VPN plugin: state changed: stopped (6) If i try to connect to VPN via nmtui - everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721735] Re: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed
James - any thoughts on this? -- 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/1721735 Title: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Artful: Triaged Bug description: With snapd 16-2.28.1 from the candidate channel Test Case 1. With gnome-software, install a snap 2. When the polkit auth dialog is displayed, click "Cancel" Actual result The Ubuntu One authentication dialog is displayed Expected result The polkit authentication dialog is dismissed and the user returns to the main screen of gnome-software. The U1 dialog is not displayed 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: Fri Oct 6 12:05:54 2017 InstallationDate: Installed on 2013-09-03 (1493 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/ubuntu/+source/gnome-software/+bug/1721735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
** Also affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Triaged ** Also affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: snapd-glib (Ubuntu Bionic) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Artful) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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 package in Ubuntu: Triaged Status in snapd-glib package in Ubuntu: Fix Committed Status in gnome-software source package in Artful: Triaged Status in snapd-glib source package in Artful: New Status in gnome-software source package in Bionic: Triaged Status in snapd-glib source package in Bionic: Fix Committed 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/ubuntu/+source/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 1725062] Re: Network Manager Applet can't connect to VPN, but nmtui does
Heytimc, your problem looks like firewall block - the connection tries to establish, but it fails. You can check if you affected by this bug via terminal. Try to connect via terminal->type nmtui->choose connect->select your vpn connection. If connection fails - it some kind of network problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1725062 Title: Network Manager Applet can't connect to VPN, but nmtui does Status in network-manager-applet package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 Fresh install 2) network-manager-pptp/artful,now 1.2.4-4 amd64 VPN connection, created in network manager can't even turn on - slider goes back to off right after your click on it. Connect via "connect" does nothing too. I've tried to change option - store password/do not store password. No errors shown,except syslog: Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5923] audit: op="connection-activate" uuid="709047eb-3254-419f-a152-0a8ff0c3a04b" name="Schastye" pid=1603 uid=1000 result="success" Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5966] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Started the VPN service, PID 5992 Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6019] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Saw the service appear; activating connection Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6336] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Failed to request VPN secrets #3: No agents were available for this request. Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6347] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: VPN plugin: state changed: stopped (6) If i try to connect to VPN via nmtui - everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721762] Re: Cancelled installation of snap continues
snapd-glib 1.24 now sends the cancel to snapd, however if you are using a Polkit enabled snapd this method doesn't work through Polkit. This causes an Ubuntu One dialog to pop up if not logged in. This should be fixed in snapd so that cancels can occur the same way as install/remove. ** Also affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: High Assignee: Robert Ancell (robert-ancell) Status: In Progress ** Also affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: snapd-glib (Ubuntu Artful) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Bionic) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Artful) Importance: Undecided => High -- 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/1721762 Title: Cancelled installation of snap continues Status in gnome-software package in Ubuntu: In Progress Status in snapd-glib package in Ubuntu: Fix Committed Status in gnome-software source package in Artful: In Progress Status in snapd-glib source package in Artful: New Status in gnome-software source package in Bionic: In Progress Status in snapd-glib source package in Bionic: Fix Committed Bug description: with core candidate: 16-2.28.1 Test Case 1. Install a snap package 2. When the installation is ongoing, press Cancel 3. Verify that installation stopped (snap changes then snap change ID) Expected result Installation is cancelled Actual result It continues in the background and gnome-software shows the wrong state 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: Fri Oct 6 13:38:01 2017 InstallationDate: Installed on 2014-07-23 (1170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: Upgraded to artful on 2017-06-13 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727564] Re: zenity crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1625281 *** https://bugs.launchpad.net/bugs/1625281 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 #1625281, 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/1727564/+attachment/4995763/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727564/+attachment/4995765/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727564/+attachment/4995769/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727564/+attachment/4995770/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727564/+attachment/4995771/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727564/+attachment/4995772/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727564/+attachment/4995773/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1625281 ** 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 zenity in Ubuntu. https://bugs.launchpad.net/bugs/1727564 Title: zenity crashed with SIGABRT in g_assertion_message() Status in zenity package in Ubuntu: New Bug description: Stacer suddenly crashed on its own. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: zenity 3.24.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sun Oct 22 20:59:06 2017 ExecutablePath: /usr/bin/zenity InstallationDate: Installed on 2017-04-03 (205 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcCmdline: zenity --warning --text The\ system\ is\ running\ in\ low-graphics\ mode\\n\\nYour\ screen,\ graphics\ card,\ and\ input\ device\ settings\\ncould\ not\ be\ detected\ correctly.\ \ You\ will\ need\ to\ configure\ these\ yourself. Signal: 6 SourcePackage: zenity StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: zenity crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1727564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Changed in: gnome-software (Ubuntu Bionic) Status: New => Fix Committed -- 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 Committed Status in gnome-software source package in Artful: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Bug description: Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10 gnome-software package version: 3.26.0-0ubuntu2 Expected: To be able to use the application. What happened instead: The application crashes after several seconds. Bug replicated every time the application is opened, rending it entirely unusable. Journald shows a segfault, as per attached snippet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 21:01:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 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/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 1720442] Re: Crashes if broken snaps installed
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-artful -- 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 Committed Status in gnome-software source package in Artful: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Bug description: Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10 gnome-software package version: 3.26.0-0ubuntu2 Expected: To be able to use the application. What happened instead: The application crashes after several seconds. Bug replicated every time the application is opened, rending it entirely unusable. Journald shows a segfault, as per attached snippet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 21:01:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 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/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 1720442] Re: Crashes if broken snaps installed
** Changed in: gnome-software (Ubuntu Artful) Status: New => Fix Committed -- 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 Committed Status in gnome-software source package in Artful: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Bug description: Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10 gnome-software package version: 3.26.0-0ubuntu2 Expected: To be able to use the application. What happened instead: The application crashes after several seconds. Bug replicated every time the application is opened, rending it entirely unusable. Journald shows a segfault, as per attached snippet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 21:01:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 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/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 1720442] Re: Crashes if broken snaps installed
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu -- 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 Committed Status in gnome-software source package in Artful: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Bug description: Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10 gnome-software package version: 3.26.0-0ubuntu2 Expected: To be able to use the application. What happened instead: The application crashes after several seconds. Bug replicated every time the application is opened, rending it entirely unusable. Journald shows a segfault, as per attached snippet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 21:01:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 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/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 1720442] Re: Crashes if broken snaps installed
** Also affects: gnome-software (Ubuntu Bionic) Importance: High Status: New ** Also affects: gnome-software (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Artful) Importance: Undecided => High -- 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 Committed Status in gnome-software source package in Artful: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Bug description: Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10 gnome-software package version: 3.26.0-0ubuntu2 Expected: To be able to use the application. What happened instead: The application crashes after several seconds. Bug replicated every time the application is opened, rending it entirely unusable. Journald shows a segfault, as per attached snippet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 21:01:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 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/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 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
I do not want to add any further patches to Debian's screen package which makes it differ from upstream behaviour more than it already does. (Of course, it's a different thing if issues are caused by existing patches.) And IMHO workarounds for issues in other packages do not belong into shell startup files either. (Saying this with my Debian Zsh Team hat on.) Additionally, after the long and thorough discussion in the Debian bug report (and additional discussions on the ncurses-term topic on IRC), I'm convinced that there is no perfect solution. If you change something to make screen usable in scenario X, it will make people using screen in scenario Y unhappy and vice versa. Even moving definitions from ncurses-term to ncurses-base doesn't make things better by default: It may help to SSH from older systems with ncurses-term to newer systems with just ncurses-base installed. But it will also cause issues for people SSHing from newer systems with just ncurses-base installed to older systems with an older version of ncurses-base installed. (Not having ncurses-term at all and all definitions in ncurses-base might look like a solution, but then it will which definitions are in that package at which version...) So yes, IMHO the best thing we can do is document the issue. (And improvements for the documentation are always welcome. :-) If you really think a behavioural change is needed in screen, then please make according suggestions upstream and submit patches there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts Status in gnome-terminal package in Ubuntu: New Status in screen package in Ubuntu: Fix Committed Status in screen package in Debian: Fix Released Bug description: As of 16.04, the screen program started using a 256 colour setting. The problem is that this setting is relatively new and has not had a chance to propagate to older hosts, including something as new as the previous 15.x release. For example: -- paul@1604-host:~$ echo $TERM screen.xterm-256color paul@y1604-host:~$ ssh oldermachine Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-84-generic x86_64) * Documentation: https://help.ubuntu.com/ 0 packages can be updated. 0 updates are security updates. Last login: Mon Oct 23 15:52:17 2017 from yow-pgortmak-d1.wrs.com paul@oldermachine:~$ echo foo > foo paul@yoldermachine:~$ less foo WARNING: terminal is not fully functional foo (press RETURN) paul@oldermachine:~$ export TERM=screen paul@yoldermachine:~$ less foo foo paul@oldermachine:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" paul@oldermachine:~$ -- This makes it extremely annoying to use 16.04 in order to interact with any other linux/unix machines. The 256 color term type needs at least a couple years roll-out time before it becomes the default. Otherwise the older machines won't have it and they will complain and default to ancient crippled defaults and nag you each time they have to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Summary changed: - Software (gnome-software) crashes after several seconds. Entirely unusable. + Crashes if broken snaps installed -- 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: New Bug description: Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10 gnome-software package version: 3.26.0-0ubuntu2 Expected: To be able to use the application. What happened instead: The application crashes after several seconds. Bug replicated every time the application is opened, rending it entirely unusable. Journald shows a segfault, as per attached snippet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 21:01:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-14 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 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/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 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
** Changed in: screen (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts Status in gnome-terminal package in Ubuntu: New Status in screen package in Ubuntu: Fix Committed Status in screen package in Debian: Fix Released Bug description: As of 16.04, the screen program started using a 256 colour setting. The problem is that this setting is relatively new and has not had a chance to propagate to older hosts, including something as new as the previous 15.x release. For example: -- paul@1604-host:~$ echo $TERM screen.xterm-256color paul@y1604-host:~$ ssh oldermachine Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-84-generic x86_64) * Documentation: https://help.ubuntu.com/ 0 packages can be updated. 0 updates are security updates. Last login: Mon Oct 23 15:52:17 2017 from yow-pgortmak-d1.wrs.com paul@oldermachine:~$ echo foo > foo paul@yoldermachine:~$ less foo WARNING: terminal is not fully functional foo (press RETURN) paul@oldermachine:~$ export TERM=screen paul@yoldermachine:~$ less foo foo paul@oldermachine:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" paul@oldermachine:~$ -- This makes it extremely annoying to use 16.04 in order to interact with any other linux/unix machines. The 256 color term type needs at least a couple years roll-out time before it becomes the default. Otherwise the older machines won't have it and they will complain and default to ancient crippled defaults and nag you each time they have to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727554] Re: endless clockcounter while installing (upgrading over old ubuntu)
*** This bug is a duplicate of bug 1631434 *** https://bugs.launchpad.net/bugs/1631434 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 #1631434, 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/1727554/+attachment/4995677/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727554/+attachment/4995679/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727554/+attachment/4995682/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727554/+attachment/4995683/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727554/+attachment/4995684/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727554/+attachment/4995685/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727554/+attachment/4995686/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1631434 gnome-control-center crashed with SIGSEGV in _cogl_check_extension() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1727554 Title: endless clockcounter while installing (upgrading over old ubuntu) Status in gnome-control-center package in Ubuntu: New Bug description: After entering all data installation should start and said: "Ermitteln der Dateisysteme..." SKIP is light grey System is working, but not installing. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 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 CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 01:52:01 2017 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center network ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7bf7b3fb59:mov(%rsi),%rsi PC (0x7f7bf7b3fb59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1727554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631434] Re: gnome-control-center crashed with SIGSEGV in _cogl_check_extension()
** Tags added: bugpattern-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1631434 Title: gnome-control-center crashed with SIGSEGV in _cogl_check_extension() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I tried to open the gnome settings application in the latest version of ubuntu gnome 16.10, and the tab came up along the top window, but then no window opened and the crash report generator came up. output of lsb_release -rd: Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 version of package I'm using: apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.20.1-2ubuntu3 Candidate: 1:3.20.1-2ubuntu3 Version table: *** 1:3.20.1-2ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: I expected the settings window to open What actually happened: The window tab at the top showed up, and the mouse cursor turned into the working circle symbol, the window didn't open. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-control-center 1:3.20.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 12:28:35 2016 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-10-07 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20161006) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fab239edb59:mov(%rsi),%rsi PC (0x7fab239edb59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1631434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727555] Re: Xorg crashed with SIGABRT in xf86RandR12CreateScreenResources()
*** This bug is a duplicate of bug 1721951 *** https://bugs.launchpad.net/bugs/1721951 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 #1721951, 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/1727555/+attachment/4995691/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727555/+attachment/4995694/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727555/+attachment/4995703/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727555/+attachment/4995705/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727555/+attachment/4995706/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727555/+attachment/4995707/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727555/+attachment/4995708/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1721951 ** 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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1727555 Title: Xorg crashed with SIGABRT in xf86RandR12CreateScreenResources() Status in xorg-server package in Ubuntu: New Bug description: this happened after i uninstalled nvidia drivers ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Oct 26 01:20:04 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:39f1] InstallationDate: Installed on 2017-09-24 (31 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80TV ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/126/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=b2c63e2b-4b46-424e-b60b-d08b3be5e745 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: xf86RandR12CreateScreenResources () ?? () ?? () __libc_start_main (main=0x559ebb1caaf0, argc=12, argv=0x7ffd4af3af48, init=, fini=, rtld_fini=, stack_end=0x7ffd4af3af38) at ../csu/libc-start.c:308 _start () Title: Xorg crashed with SIGABRT in xf86RandR12CreateScreenResources() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/10/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C2 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN23WW:bd11/10/2016:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 26 02:00:55
[Desktop-packages] [Bug 1727550] [NEW] nautalis opens *.rs (i.e. rust files) in multiple gvim instances as if the gvim.desktop file used %f but it uses %F
Public bug reported: I select multiple files extension .rs and open it in gvim from the right click menu and it opens them in multiple gvim's this is the only file type showing this behaviour 1. I am using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful on a 64 bit Intel® Core™2 Duo CPU E7500 @ 2.93GHz × 2 machine 2. $ apt-cache policy nautilus nautilus: Installed: 1:3.26.0-0ubuntu1 Candidate: 1:3.26.0-0ubuntu1 Version table: *** 1:3.26.0-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to open *.rs files in one gvim like it does with every thing else 4. it opened them in one gvim per file ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:39:29 2017 InstallationDate: Installed on 2017-07-24 (93 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1727550 Title: nautalis opens *.rs (i.e. rust files) in multiple gvim instances as if the gvim.desktop file used %f but it uses %F Status in nautilus package in Ubuntu: New Bug description: I select multiple files extension .rs and open it in gvim from the right click menu and it opens them in multiple gvim's this is the only file type showing this behaviour 1. I am using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.10 Release: 17.10 Codename: artful on a 64 bit Intel® Core™2 Duo CPU E7500 @ 2.93GHz × 2 machine 2. $ apt-cache policy nautilus nautilus: Installed: 1:3.26.0-0ubuntu1 Candidate: 1:3.26.0-0ubuntu1 Version table: *** 1:3.26.0-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to open *.rs files in one gvim like it does with every thing else 4. it opened them in one gvim per file ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:39:29 2017 InstallationDate: Installed on 2017-07-24 (93 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1727550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723874] Re: First installation of a snap reports an error "Connection reset by peer"
Fix now in ppa:ubuntu-desktop/gnome-software (snapd-glib 1.24-0ubuntu1~ppa1). For me now I can install on first attempt. I tested with: 1. Remove existing core snap (removes ALL snaps on your system) $ sudo apt purge snapd $ sudo apt install snapd 2. Restart GNOME Software $ killall gnome-software 3. Install moon-buggy snap ** Changed in: snapd-glib (Ubuntu) Status: In Progress => Fix Committed ** Also affects: gnome-software (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu Artful) Status: New => Fix Committed ** Changed in: snapd-glib (Ubuntu Artful) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Zesty) Status: New => Invalid ** Changed in: snapd-glib (Ubuntu Xenial) Status: New => Invalid ** Changed in: gnome-software (Ubuntu Artful) Status: New => Invalid ** No longer affects: gnome-software (Ubuntu Artful) ** No longer affects: snapd-glib (Ubuntu Zesty) ** No longer affects: snapd-glib (Ubuntu Xenial) ** Changed in: snapd-glib (Ubuntu Artful) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu Zesty) Importance: Undecided => Medium -- 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/1723874 Title: First installation of a snap reports an error "Connection reset by peer" Status in gnome-software package in Ubuntu: Triaged Status in snapd-glib package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: New Status in gnome-software source package in Zesty: New Status in snapd-glib source package in Artful: Fix Committed Bug description: Test Case 1. On a freshly installed system when snapd has never been used or initialized before (ie core is not installed) open gnome-software 2. Select a snap 3. Install it 4. Wait until it is installed Actual result At some point gnome-software reports an error "Installation failed: connection reset by peer" It was actually installing core, restarted snapd, then the package. But gnome-software reports the error when snapd is restarted, loses the connection to the daemon and does not track the progress of the installation of the snap package Expected result It reports the installation of core then the installation of the snap package, or report everything in a single transaction but in any case does not report an error since everything is going as expected. Attached the changes that are occurring when the first snap is installed on a fresh system ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 09:26:38 2017 InstallationDate: Installed on 2013-09-03 (1503 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.1-0ubuntu1 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/ubuntu/+source/gnome-software/+bug/1723874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716009] Re: problem with the sound since the latest update
why is there not any response to this bug report?! the latest updates were released just now, including linux-firmware 1.157.13, and the problem is still there even after i installed them on my computer - there is still no effect when adjusting sound volume slider from the sound menu on the menu bar and sound settings - what is going on, i thought the problem will be resolved after the new linux- firmware update?! - i haven't been able to adjust sound volume for almost two months -- 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/1716009 Title: problem with the sound since the latest update Status in alsa-driver package in Ubuntu: New Bug description: i am with an old intel chipset motherboard having an integrated realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the latest update there has had no effect when adjusting sound volume from the sound menu on the menu bar and sound settings, and no sound in counter strike 1.6 linux version, also, there has appeared an effect of a sound interruption/break (for less than a second) when switching between applications, however, i can still adjust the sound volume from gnome alsa mixer the latest update includes: snapd-login-service:amd64 libsnapd-glib1:amd64 linux-firmware:amd64 libgd3:amd64 the previous ——: libpackagekit-glib2-16:amd64 gir1.2-packagekitglib-1.0:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703638] Re: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA
Tested 2.29~rc1 and `edge` (currently 2.28.5+git445.496e635 (3314)) and can't see the system fonts from LibreOffice, guessing the desktop interface needs to be connected? What command should I use to do that? -- 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/1703638 Title: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported here: https://forum.snapcraft.io/t/call-for- testing-libreoffice-5-3-4-snap/1205/2) The libreoffice snap doesn't seem to find custom fonts installed by the user under $HOME/.fonts/. It does find them after copying/linking them under $SNAP_USER_DATA/.fonts/ though, so ideally that link would happen automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1703638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703638] Re: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA
Actually sorry that may have been a complete red herring, I'm talking about system fonts rather than fonts in ~/.fonts ... -- 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/1703638 Title: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported here: https://forum.snapcraft.io/t/call-for- testing-libreoffice-5-3-4-snap/1205/2) The libreoffice snap doesn't seem to find custom fonts installed by the user under $HOME/.fonts/. It does find them after copying/linking them under $SNAP_USER_DATA/.fonts/ though, so ideally that link would happen automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1703638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703638] Re: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA
Should be fixed in core 2.29 with the new desktop interface according to https://forum.snapcraft.io/t/desktop-allow-access-to-host-system- fonts/1796 -- 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/1703638 Title: [snap] symlink ~/.fonts by default to $SNAP_USER_DATA Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported here: https://forum.snapcraft.io/t/call-for- testing-libreoffice-5-3-4-snap/1205/2) The libreoffice snap doesn't seem to find custom fonts installed by the user under $HOME/.fonts/. It does find them after copying/linking them under $SNAP_USER_DATA/.fonts/ though, so ideally that link would happen automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1703638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
Also affects me on Lubuntu 16.04. Installing IBus (sudo apt ibus) and using Preferences > Language Support to change the Keyboard input method system to IBus, followed by a system reboot, has fixed the issue (compose:ralt in Keyboard Layout Handler now functions as expected). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 Status in firefox package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in ibus package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: After upgrading to 16.04, entering characters using dead keys and using the Compose key stopped working in Gnome Terminal, acting like they are normal (non-dead) keys. Other applications, even those who use the same libvte (e.g. ROXTerm), don't have this issue. This happens with both the "Belgian" and "English international with AltGr dead keys" layouts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:45:33 2016 InstallationDate: Installed on 2013-12-16 (857 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711186] Re: [snap] cups-control should be auto-connected
I requested this on the snapcraft forum here: https://forum.snapcraft.io/t/request-autoconnection-of-cups-control-for- libreoffice/2517 It hasn't got enough votes to be auto-connected, it seems... -- 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/1711186 Title: [snap] cups-control should be auto-connected Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed a printer using the Printers application but LibreOffice can't see it, even after a reboot. To solve this problem so that the snap works out-of-the-box, the cups- control interface should be auto-connected. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode:false trymode: false enabled: true broken: false tracking: stable installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 18:14:41 +0100 BST channels: stable: 5.3.4.2 (21) 368MB - candidate: 5.3.2.2 (19) 375MB - beta:5.3.4.2 (21) 368MB - edge:5.3.2.2 (19) 375MB - --- 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 13:45:34 +0100 BST 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/libreoffice/+bug/1711186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719198] Re: LibreOffice Snap package doesn't list the system printers
*** This bug is a duplicate of bug 1711186 *** https://bugs.launchpad.net/bugs/1711186 Until the interface is auto-connected or there's a GUI in Ubuntu Software to connect the interface, please use the following command to get printers working: `snap connect libreoffice:cups-control :cups-control` ** This bug has been marked a duplicate of bug 1711186 [snap] cups-control should be auto-connected -- 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/1719198 Title: LibreOffice Snap package doesn't list the system printers Status in libreoffice package in Ubuntu: New Bug description: I have installed on my system Ubuntu 16.04 the following version of LibreOffice snap: libreoffice 5.3.4.2 / 21 / canonical The problem is that when I want to print a document, only a "Generic Printer" is listed. No one of the printers of my system is listed. So, I can't actually print anything. With the LibreOffice DEB package from the repositories I never had any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1719198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725062] Re: Network Manager Applet can't connect to VPN, but nmtui does
The workaround https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/comments/2 does not work for all. For me the VPN PPTP stopped work since Ubuntu 16.04 please fix this issue. The settings I received from my organization are: Typ VPN : Point to Point tunneling protocol (PPTP) VPN server: example.server.net TCP port: 1723 IP protocol: GRE (Generic Routing Encapsulation, IP protocol ID 47 PPTP Authentication: Microsoft CHAP version 2 (MS-CHAP v2) PPP Encryption: MPPE -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1725062 Title: Network Manager Applet can't connect to VPN, but nmtui does Status in network-manager-applet package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 Fresh install 2) network-manager-pptp/artful,now 1.2.4-4 amd64 VPN connection, created in network manager can't even turn on - slider goes back to off right after your click on it. Connect via "connect" does nothing too. I've tried to change option - store password/do not store password. No errors shown,except syslog: Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5923] audit: op="connection-activate" uuid="709047eb-3254-419f-a152-0a8ff0c3a04b" name="Schastye" pid=1603 uid=1000 result="success" Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5966] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Started the VPN service, PID 5992 Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6019] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Saw the service appear; activating connection Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6336] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Failed to request VPN secrets #3: No agents were available for this request. Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6347] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: VPN plugin: state changed: stopped (6) If i try to connect to VPN via nmtui - everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => High -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 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: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
** Branch linked: lp:~ubuntu-desktop/snapd-glib/ubuntu -- 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 package in Ubuntu: Triaged Status in gnome-software source package in Artful: Triaged 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/ubuntu/+source/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 1723874] Re: First installation of a snap reports an error "Connection reset by peer"
** Branch linked: lp:~ubuntu-desktop/snapd-glib/ubuntu -- 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/1723874 Title: First installation of a snap reports an error "Connection reset by peer" Status in gnome-software package in Ubuntu: Triaged Status in snapd-glib package in Ubuntu: In Progress Bug description: Test Case 1. On a freshly installed system when snapd has never been used or initialized before (ie core is not installed) open gnome-software 2. Select a snap 3. Install it 4. Wait until it is installed Actual result At some point gnome-software reports an error "Installation failed: connection reset by peer" It was actually installing core, restarted snapd, then the package. But gnome-software reports the error when snapd is restarted, loses the connection to the daemon and does not track the progress of the installation of the snap package Expected result It reports the installation of core then the installation of the snap package, or report everything in a single transaction but in any case does not report an error since everything is going as expected. Attached the changes that are occurring when the first snap is installed on a fresh system ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 09:26:38 2017 InstallationDate: Installed on 2013-09-03 (1503 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.1-0ubuntu1 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/ubuntu/+source/gnome-software/+bug/1723874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726821] Re: It takes a while for the tray notification menu to open when clicking on the time and date in the top bar
** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => Medium -- 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/1726821 Title: It takes a while for the tray notification menu to open when clicking on the time and date in the top bar Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Dear all, Once I click on the time and date entry in the top bar, it takes a couple of seconds for the menu to open [1]. Tested on Ubuntu 17.10 with the latest updates installed. Not sure if this is a bug or user error. [1] https://www.useloom.com/share/a80d02fd2f894c9fa6eac201c4fa1c7b --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.shell enabled-extensions ['clipboard-indica...@tudmotu.com', 'gnome-shell-screens...@ttll.de', 'appindicatorsupp...@rgcjonas.gmail.com', 'ubuntu-d...@ubuntu.com', 'topIcons@adel.gadl...@gmail.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com'] org.gnome.shell favorite-apps ['org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'google-chrome.desktop'] org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' org.gnome.desktop.interface clock-show-date true InstallationDate: Installed on 2017-09-30 (24 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1726821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721762] Re: Cancelled installation of snap continues
** Branch linked: lp:~ubuntu-desktop/snapd-glib/ubuntu -- 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/1721762 Title: Cancelled installation of snap continues Status in gnome-software package in Ubuntu: In Progress Status in gnome-software source package in Artful: In Progress Bug description: with core candidate: 16-2.28.1 Test Case 1. Install a snap package 2. When the installation is ongoing, press Cancel 3. Verify that installation stopped (snap changes then snap change ID) Expected result Installation is cancelled Actual result It continues in the background and gnome-software shows the wrong state 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: Fri Oct 6 13:38:01 2017 InstallationDate: Installed on 2014-07-23 (1170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: Upgraded to artful on 2017-06-13 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727539] Re: totem crashed with SIGSEGV in cogl_renderer_connect()
*** This bug is a duplicate of bug 1681210 *** https://bugs.launchpad.net/bugs/1681210 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 #1681210, 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/1727539/+attachment/4995557/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727539/+attachment/4995559/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727539/+attachment/4995565/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727539/+attachment/4995566/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727539/+attachment/4995567/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727539/+attachment/4995568/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727539/+attachment/4995569/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1681210 ** 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 totem in Ubuntu. https://bugs.launchpad.net/bugs/1727539 Title: totem crashed with SIGSEGV in cogl_renderer_connect() Status in totem package in Ubuntu: New Bug description: Video error ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 00:31:58 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-10-25 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/totem --gapplication-service SegvAnalysis: Segfault happened at: 0x7fd902dd5b59:mov(%rsi),%rsi PC (0x7fd902dd5b59) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: totem crashed with SIGSEGV in cogl_renderer_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1727539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725062] Re: Network Manager Applet can't connect to VPN, but nmtui does
I have symptoms like these as well - I think these are the relevent syslog lines: Oct 25 23:29:34 tim-573P pppd[25897]: LCP: timeout sending Config-Requests Oct 25 23:29:34 tim-573P NetworkManager[23036]: LCP: timeout sending Config-Requests Oct 25 23:29:34 tim-573P NetworkManager[23036]: Connection terminated. Oct 25 23:29:34 tim-573P pppd[25897]: Connection terminated. Oct 25 23:29:34 tim-573P NetworkManager[23036]: [1508970574.5444] vpn-connection[0x556db598a6d0,fe39617c-d214-480d-a0f1-6344e6005878,"Manifest",0]: VPN service disappeared Oct 25 23:29:34 tim-573P NetworkManager[23036]: [1508970574.5475] devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Oct 25 23:29:34 tim-573P gnome-shell[4380]: Removing a network device that was not added Oct 25 23:29:34 tim-573P gnome-shell[1815]: Removing a network device that was not added Oct 25 23:29:34 tim-573P pppd[25897]: Terminating on signal 15 Oct 25 23:29:34 tim-573P NetworkManager[23036]: Terminating on signal 15 Oct 25 23:29:34 tim-573P NetworkManager[23036]: Child process /usr/sbin/pptp 77.44.84.210 --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-25893 (pid 25900) terminated with signal 15 Oct 25 23:29:34 tim-573P NetworkManager[23036]: Modem hangup Oct 25 23:29:34 tim-573P pppd[25897]: Child process /usr/sbin/pptp 77.44.84.210 --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-25893 (pid 25900) terminated with signal 15 Oct 25 23:29:34 tim-573P pppd[25897]: Modem hangup Oct 25 23:29:34 tim-573P pppd[25897]: Exit. Oct 25 23:29:34 tim-573P zeal.desktop[14336]: "No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/NetworkManager/ActiveConnection/14" Oct 25 23:29:34 tim-573P gnome-shell[4380]: [AppIndicatorSupport-WARN] Attempting to re-register :1.74/org/ayatana/NotificationItem/multiload; resetting instead -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1725062 Title: Network Manager Applet can't connect to VPN, but nmtui does Status in network-manager-applet package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 Fresh install 2) network-manager-pptp/artful,now 1.2.4-4 amd64 VPN connection, created in network manager can't even turn on - slider goes back to off right after your click on it. Connect via "connect" does nothing too. I've tried to change option - store password/do not store password. No errors shown,except syslog: Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5923] audit: op="connection-activate" uuid="709047eb-3254-419f-a152-0a8ff0c3a04b" name="Schastye" pid=1603 uid=1000 result="success" Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.5966] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Started the VPN service, PID 5992 Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6019] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Saw the service appear; activating connection Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth gnome-shell[1603]: Invalid VPN service type (cannot find authentication binary) Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6336] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: Failed to request VPN secrets #3: No agents were available for this request. Oct 20 03:13:27 sabertooth NetworkManager[824]: [1508458407.6347] vpn-connection[0x55b89ac6b2c0,709047eb-3254-419f-a152-0a8ff0c3a04b,"Schastye",0]: VPN plugin: state changed: stopped (6) If i try to connect to VPN via nmtui - everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1725062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575077] Re: package python-tdb 1.3.8-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tdb in Ubuntu. https://bugs.launchpad.net/bugs/1575077 Title: package python-tdb 1.3.8-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tdb package in Ubuntu: Confirmed Bug description: Upgraded from 15.10 Gnome ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-tdb 1.3.8-2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 19:26:31 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-14 (347 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: tdb Title: package python-tdb 1.3.8-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tdb/+bug/1575077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716639] Re: gnome-screensaver issue when using Wayland
I see the same issue on Ubuntu 17.10 on a Dell XPS 9530. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1716639 Title: gnome-screensaver issue when using Wayland Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: When using a Wayland session instead of X11 from the standard lightdm- gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+ initialisation, causing the gnome-session-binary to exit and subsequently a greeter loop where a user is unable to log in. The following is an excerpt from the syslog: ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service name='org.gnome.ScreenSaver' Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init server: Could not connect: Connection refused Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+ S Running an identical session without Wayland produces the expected behaviour: a user can log into his desktop session and start working as usual. Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share /gnome-session/sessions/gnome.session doesn't have any effect. I'm suspecting foul play between the screensaver proxy and the screensaver binary itself, but don't have the bandwidth to analyse the source at the moment. More than happy to provide more information as required - just let me know. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-screensaver 3.6.1-7ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 11:29:30 2017 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2017-08-31 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716639] Re: gnome-screensaver issue when using Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1716639 Title: gnome-screensaver issue when using Wayland Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: When using a Wayland session instead of X11 from the standard lightdm- gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+ initialisation, causing the gnome-session-binary to exit and subsequently a greeter loop where a user is unable to log in. The following is an excerpt from the syslog: ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service name='org.gnome.ScreenSaver' Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init server: Could not connect: Connection refused Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+ S Running an identical session without Wayland produces the expected behaviour: a user can log into his desktop session and start working as usual. Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share /gnome-session/sessions/gnome.session doesn't have any effect. I'm suspecting foul play between the screensaver proxy and the screensaver binary itself, but don't have the bandwidth to analyse the source at the moment. More than happy to provide more information as required - just let me know. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-screensaver 3.6.1-7ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 11:29:30 2017 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2017-08-31 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727529] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 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 #1706097, 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/1727529/+attachment/4995501/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727529/+attachment/4995503/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727529/+attachment/4995506/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727529/+attachment/4995507/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727529/+attachment/4995508/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727529/+attachment/4995509/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727529/+attachment/4995510/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** 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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1727529 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: samba connection on a raspberry pi3 with lakka install. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 21:45:04 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2015-05-25 (884 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/10 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f73c440f5a9:mov0x18(%rax),%rax PC (0x7f73c440f5a9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-16 (9 days ago) UserGroups: adm cdrom daemon dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1727529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Description changed: Note to SRU Team - The first proposed fix (1.0.27-1~experimental2ubuntu2) simply added 'Provides: libsane' but I believe that didn't work because of versioned dependencies. - - This second proposal (1.0.27-1~experimental2ubuntu3) adds a transitional - package libsane and will therefore need NEW processing. + 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. - 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. - 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) -- 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 Committed Status in sane-backends source package in Artful: Fix Committed 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
[Desktop-packages] [Bug 1727518] [NEW] Presentation mode broken with HighDPI and 200% scale
Public bug reported: When using a presentation mode with a HighDPI screen and 200% scaling the slides are rendered only partially and a large part is clipped. Probably this upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1369216 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 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 25 22:33:18 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1727518 Title: Presentation mode broken with HighDPI and 200% scale Status in evince package in Ubuntu: New Bug description: When using a presentation mode with a HighDPI screen and 200% scaling the slides are rendered only partially and a large part is clipped. Probably this upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1369216 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 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 25 22:33:18 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1727518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
I _guess_ it shouldn't be that hard to patch screen to make an exception to the "prepend 'screen.'" rule, and convert an implicitly created "screen.xterm-256color" into "screen-256color". (I haven't checked screen's source to see how easy it would be.) This would go against its current documentation, so the documentation should be updated and probably a similar README.Debian entry should also be created. Also, before doing this, it should be examined and understood what's the difference between these two terminal descriptions (at least the file themselves are not exactly byte-by-byte the same). Alternatively, a similar workaround could go into shell startup files (probably /etc/bash.bashrc and /etc/zsh/zshrc) instead. If we're saying documenting the issue in screen's README.Debian is enough (as it might easily be, presumably there'll be tons of forums out there pointing to this file), the current addition really nicely summarizes the available workarounds, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts Status in gnome-terminal package in Ubuntu: New Status in screen package in Ubuntu: Fix Committed Status in screen package in Debian: Confirmed Bug description: As of 16.04, the screen program started using a 256 colour setting. The problem is that this setting is relatively new and has not had a chance to propagate to older hosts, including something as new as the previous 15.x release. For example: -- paul@1604-host:~$ echo $TERM screen.xterm-256color paul@y1604-host:~$ ssh oldermachine Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-84-generic x86_64) * Documentation: https://help.ubuntu.com/ 0 packages can be updated. 0 updates are security updates. Last login: Mon Oct 23 15:52:17 2017 from yow-pgortmak-d1.wrs.com paul@oldermachine:~$ echo foo > foo paul@yoldermachine:~$ less foo WARNING: terminal is not fully functional foo (press RETURN) paul@oldermachine:~$ export TERM=screen paul@yoldermachine:~$ less foo foo paul@oldermachine:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" paul@oldermachine:~$ -- This makes it extremely annoying to use 16.04 in order to interact with any other linux/unix machines. The 256 color term type needs at least a couple years roll-out time before it becomes the default. Otherwise the older machines won't have it and they will complain and default to ancient crippled defaults and nag you each time they have to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar
The attachment "bz_unity_headerbar.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1719322 Title: Remove patch to remove headerbar Status in eog package in Ubuntu: Triaged Status in epiphany-browser package in Ubuntu: Fix Released Status in evince package in Ubuntu: Triaged Status in file-roller package in Ubuntu: Triaged Status in gnome-contacts package in Ubuntu: Fix Released Bug description: As of Artful, it seems that there are still patches against various apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar. Now that GNOME Shell is default in Ubuntu and there is better support for client-side decorations, these patches can probably go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1719322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar
Khurshid, are you aware that there are apps in the default Ubuntu install that never got these headerbar patches, like gnome-calendar and gnome-sudoku? And there are a rather large number of GNOME apps that aren't in the default install. Even Firefox is switching to headerbars, maybe by early next year. It feels like a huge undertaking if you really want to not have headerbars in Unity, and I'm not sure it's worth all that work. -- 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/1719322 Title: Remove patch to remove headerbar Status in eog package in Ubuntu: Triaged Status in epiphany-browser package in Ubuntu: Fix Released Status in evince package in Ubuntu: Triaged Status in file-roller package in Ubuntu: Triaged Status in gnome-contacts package in Ubuntu: Fix Released Bug description: As of Artful, it seems that there are still patches against various apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar. Now that GNOME Shell is default in Ubuntu and there is better support for client-side decorations, these patches can probably go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1719322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725388] Re: hpcups assert failure: *** Error in `HP-LaserJet-Professional-M1136-MFP': free(): invalid pointer: 0x0000561e356cc784 ***
** Information type changed from Private to Public ** Also affects: hplip Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1725388 Title: hpcups assert failure: *** Error in `HP-LaserJet- Professional-M1136-MFP': free(): invalid pointer: 0x561e356cc784 *** Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: I am using Ubuntu 17.10 Artful ... The problem is that when I add my HP laserjet printer in the Devices section under the settings menu...the jobs are put in queue...but they are not printing...then i have to cancel all of them .. if download the plugin using hp-plugin -i ...will it resolve the problem ?? ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: printer-driver-hpcups 3.17.7+repack0-3 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 AssertionMessage: *** Error in `HP-LaserJet-Professional-M1136-MFP': free(): invalid pointer: 0x561e356cc784 *** Date: Fri Oct 20 22:50:54 2017 ExecutablePath: /usr/lib/cups/filter/hpcups InstallationDate: Installed on 2017-09-20 (30 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lpstat: device for HP-LaserJet-Professional-M1136-MFP: hp:/usb/HP_LaserJet_Professional_M1136_MFP?serial=0QH99AF9PR1a MachineType: Dell Inc. Inspiron N5110 Papersize: a4 PpdFiles: HP-LaserJet-Professional-M1136-MFP: HP LaserJet Professional m1136 MFP, hpcups 3.17.7, requires proprietary plugin ProcCmdline: HP-LaserJet-Professional-M1136-MFP 1 apollo Test\ Page 1 job-uuid=urn:uuid:d4bf3387-00e2-3b68-7aa4-4b8b43ca99d0\ job-originating-host-name=localhost\ date-time-at-creation=\ date-time-at-processing=\ time-at-creation=1508520051\ time-at-processing=1508520051 ProcEnviron: PATH=(custom, no user) LANG=en_IN.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ae860a21-2187-4b4c-8d28-f1bc8621961a ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: hplip StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f99d0f124e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7f99d0f0ee6e "free(): invalid pointer", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7f99d1144c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () Title: hpcups assert failure: *** Error in `HP-LaserJet-Professional-M1136-MFP': free(): invalid pointer: 0x561e356cc784 *** UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 02J65Y dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn02J65Y:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1725388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727505] Re: gvfsd-smb-browse crashed with SIGABRT
*** This bug is a duplicate of bug 1546463 *** https://bugs.launchpad.net/bugs/1546463 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 #1546463, 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/1727505/+attachment/4995358/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727505/+attachment/4995360/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727505/+attachment/4995364/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727505/+attachment/4995365/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727505/+attachment/4995366/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727505/+attachment/4995367/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727505/+attachment/4995368/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1546463 ** 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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1727505 Title: gvfsd-smb-browse crashed with SIGABRT Status in gvfs package in Ubuntu: New Bug description: Ubuntu 17.10 System report the crash. No more information... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Wed Oct 25 21:54:07 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse InstallationDate: Installed on 2016-03-04 (600 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.22 /org/gtk/gvfs/exec_spaw/81 Signal: 6 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 _talloc_free () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 smbc_free_context () at /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 () g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gvfsd-smb-browse crashed with SIGABRT UpgradeStatus: Upgraded to artful on 2017-10-21 (4 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1727505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1708994 Title: package xserver-xorg-video-ast-hwe-16.04 missing Status in evince package in Ubuntu: Confirmed Bug description: There is no xserver-xorg-video-ast-hwe-16.04 package. So i can not use the ASpeed graphics for output anymore. I needed the hwe for the GTX 1060 nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 7 06:51:11 2017 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1708994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726192] Re: 17.10 Login To Wayland Fails Unless User Logs Into Unity First
Good catch. The description of the behavior is very similar. Following a review of that thread, I did some more testing. Below are the findings: Reboot the system Attempt to log into 'Ubuntu' session Screen goes black for 2-3 seconds and returns me to login screen Attempt to log into 'Ubuntu on Xorg' session Login succeeds and session starts normally Log out Attempt to log into 'Ubuntu' session Screen goes black for 2-3 seconds and returns me to login screen Attempt to log into 'Unity' session Login succeeds and Unity session starts normally Log out Attempt to log into 'Ubuntu' session Login succeeds and session starts normally So, it appears that I can log into either Unity or Ubuntu on Xorg after a clean reboot without issue. However, I can only log into a Ubuntu session if I have first logged into a Unity session, then logged out. Logging in to Xorg doesn't help. Attached is a new debug syslog that should capture the entire sequence. The login attempts should start at the 'Oct 25 15:32:39' timestamp. ** Attachment added: "syslog_Xorg_Ubuntu_Unity_Ubuntu.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1726192/+attachment/4995347/+files/syslog_Xorg_Ubuntu_Unity_Ubuntu.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1726192 Title: 17.10 Login To Wayland Fails Unless User Logs Into Unity First Status in gnome-desktop package in Ubuntu: New Bug description: After upgrading from 17.04 to 17.10, it's not possible to log into the default 'Ubuntu' session unless I log into Unity first. If I log into Unity, immediately log out, then log into Ubuntu, it logs in without issue. If I don't log into Unity first, the login attempt to Ubuntu briefly shows a black screen, then returns immediately to the login prompt. From suspend or hibernate, I can continue using the Wayland session without issue through poweroff. If I reboot or shutdown, the first login needs to be Unity, then I can log out and back to the Ubuntu session normally. Attached is some output from syslog showing gnome-session related errors. I'm not sure if they show the specific error, but they do appear at the time a first Ubuntu login is attempted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1726192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
