[Desktop-packages] [Bug 1120457] Re: [soundnua]: gnome-control-center crashed with SIGSEGV in g_param_spec_pool_lookup()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1120457 Title: [soundnua]: gnome-control-center crashed with SIGSEGV in g_param_spec_pool_lookup() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Crash happened when trying to change the route of the audio input, using the GUI for sound settings. I'm using an Edirol UA-25, USB audio interface. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Sat Feb 9 16:51:58 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-02-09 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130209) MarkForUpload: True ProcCmdline: gnome-control-center sound-nua ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fb3c4840dd2 : callq 0x7fb3c482f230 PC (0x7fb3c4840dd2) ok source "0x7fb3c482f230" (0x7fb3c482f230) ok destination "(%rsp)" (0x7fffdcb67fc0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_param_spec_pool_lookup () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_get_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: [soundnua]: gnome-control-center crashed with SIGSEGV in g_param_spec_pool_lookup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: gnome-session[1294]: WARNING: Failed to start app: Unable to start application: Failed to execute child process "/usr/bin/tomboy" (No such file or directory) gnome-session[1294]: WARNING: Failed to start app: Unable to start application: Failed to execute child process "dropbox" (No such file or directory) (process:2127): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1120457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703668] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()
** Changed in: mutter Status: Unknown => Confirmed ** Changed in: mutter 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/1703668 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor() Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/bfdb8ffc57978ae7c23f78fdf44266fa56985fe9 --- The only thing i recognize from the crash is the crash report. everything works as expected ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.12.0-6.7-generic 4.12.0 Uname: Linux 4.12.0-6-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Jul 9 21:56:54 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-07 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170630) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fd10dc9e103 : jmpq *0x88(%rax) PC (0x7fd10dc9e103) ok source "*0x88(%rax)" ok SP (0x7ffe42d50508) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_main_output () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1703668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725137] Re: gnome-shell crashed with signal 5 when using two monitors
*** This bug is a duplicate of bug 1724334 *** https://bugs.launchpad.net/bugs/1724334 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 #1724334, 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/1725137/+attachment/4977800/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725137/+attachment/4977802/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725137/+attachment/4977806/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725137/+attachment/4977807/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725137/+attachment/4977808/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725137/+attachment/4977809/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725137/+attachment/4977810/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1724334 gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from st_widget_allocate() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725137 Title: gnome-shell crashed with signal 5 when using two monitors Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with signal 5 when using two monitors 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 14:48:17 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'arc-m...@linxgem33.com', 'multi-monitors-add-on@spin83', 'netsp...@hedayaty.gmail.com']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'gtk-theme' b"'Arc'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so Title: gnome-shell crashed with signal 5 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/1725137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724334] Re: gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from st_widget_allocate()
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/1724334 Title: gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from st_widget_allocate() Status in gnome-shell package in Ubuntu: Confirmed Bug description: I was trying to unlock my screen which took a while and then I received this crash report. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 17 11:18:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2013-01-16 (1735 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) ProcCmdline: gnome-shell --sm-client-id 10aeea5677451824be150033639041251008268 ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
desktop-packages@lists.launchpad.net
** Summary changed: - gnome-shell assert failure: gnome-shell: libinput.c:2157: libinput_device_destroy: list_empty(&device->event_listeners) + gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(&device->event_listeners) -- 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/1724886 Title: gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed: libinput_device_destroy: list_empty(&device->event_listeners) Status in gnome-shell package in Ubuntu: New Bug description: Sequence of events before this occurred: I started a rebuild of VirtualBox without disabling the "dangerous parts" while running a virtual machine, which brought my machine to its knees with swapping. After I had managed to kill the build and the machine over ssh and turn off the swap, the desktop was no longer responsive. Switching to a VT and back brought it back at a low resolution. I opened the configuration panel, wanted to select the monitor settings and the desktop crashed. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AssertionMessage: gnome-shell: libinput.c:2157: libinput_device_destroy: Проверочное утверждение «list_empty(&device->event_listeners)» не выполнено. CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 17:07:03 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' 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 (506 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f6d70c7e6b0 "list_empty(&device->event_listeners)", file=file@entry=0x7f6d70c7e56d "libinput.c", line=line@entry=2157, function=function@entry=0x7f6d70c7ee30 "libinput_device_destroy") at assert.c:92 __GI___assert_fail (assertion=0x7f6d70c7e6b0 "list_empty(&device->event_listeners)", file=0x7f6d70c7e56d "libinput.c", line=2157, function=0x7f6d70c7ee30 "libinput_device_destroy") at assert.c:101 () at /usr/lib/x86_64-linux-gnu/libinput.so.10 libinput_device_unref () at /usr/lib/x86_64-linux-gnu/libinput.so.10 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so Title: gnome-shell assert failure: gnome-shell: libinput.c:2157: libinput_device_destroy: Проверочное утверждение «list_empty(&device->event_listeners)» не выполнено. UpgradeStatus: Upgraded to artful on 2017-10-05 (14 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725146] 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/1725146/+attachment/4977895/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725146/+attachment/4977897/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725146/+attachment/4977900/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725146/+attachment/4977901/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725146/+attachment/4977902/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725146/+attachment/4977903/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725146/+attachment/4977904/+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/1725146 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: I noticed this report on Fri October 20th at 0300am. 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 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 06:35:57 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2017-10-02 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/44 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fd7e971d5a9:mov0x18(%rax),%rax PC (0x7fd7e971d5a9) 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: ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV 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/gvfs/+bug/1725146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725153] Re: Reintroduce headless mode in GNOME Shell
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1725153 Title: Reintroduce headless mode in GNOME Shell Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Impact] * I day before the 17.10 release, we had to revert some commits in GNOME Shell due to https://bugs.launchpad.net/gnome-shell/+bug/1723577 which was a release blocker (GNOME Shell not displaying anything on multiple config). * Pinging upstream, they debugged it and found the real issue in mutter, and so fixed it, which will enable us to align again with upstream's repo. * This should mostly be a no visible-effect for previously impacted users, but GNOME Shell shouldn't crash anymore in GDM (reverting then to Xorg), triggering apport on logging, and the users can then use Wayland instead of Xorg. [Test Case] * Install both mutter and gnome-shell to their latest version in -proposed * Reboot * Ensure you have an UI in GDM * Log in into your session, check that you have an UI and everything is showing up as expected [Regression Potential] * Impact is a regression in GNOME Shell (showing up your entire UI) and not being able to log in. However, some of us (not impated by the bug) are already running latest version and don't see any issue. I have also asked 3 people being impacted by the bug and fixed by the revert to test upstream commits (prepared a package for them in a PPA), and they are running on it since yesterday, confirming Wayland is available. * The regressions are quite straightfoward to see: either you have an UI in GDM or none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723772] Re: Shell crashes when left unattended
Please have a look in /var/crash for .crash files. For each crash FILENAME run: ubuntu-bug /var/crash/FILENAME.crash And then add a comment here linking to the newly created bugs. ** Summary changed: - Hibernation + Shell crashes when left unattended ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** No longer affects: linux (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/1723772 Title: Shell crashes when left unattended Status in gnome-shell package in Ubuntu: Incomplete Bug description: When the monitor in the modus hibernation gets, it works until then ok, even if I'm listenig to music, the music plays further. When I try to come back to use the computer the music stops and when I insert my password all the programs are closed, as if I had started the OS. Every windows are closed and you need to open eveything again. Just to inform: I use a Monitor Samsung 4K 28" through DisplayPort. On a desktop, not a laptop. If you need some more information that I may forgot, I try to answer as soon as possible. Thank you very much, Thiago Benites PS: I use the german version of Artful Aardvark --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: thiago 1032 F...m pulseaudio /dev/snd/controlC0: thiago 1032 F pulseaudio /dev/snd/controlC1: thiago 1032 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-02 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 32272R4 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful wayland-session 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 dmi.bios.date: 04/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT67AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT67AUS:bd04/27/2013:svnLENOVO:pn32272R4:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrWin8STDDPKTPG:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 32272R4 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: thiago 6664 F...m pulseaudio /dev/snd/controlC0: thiago 6664 F pulseaudio /dev/snd/controlC1: thiago 6664 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-02 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 32272R4 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful wayland-session 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 dmi.bios.date: 04/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT67AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.ch
[Desktop-packages] [Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)
For me it's very annoying. I migrated from Ubuntu 17.04 to 17.10 several days before, and just cant use nautilus. I'm using this type-ahead feature for navigate. At the beginning i tried to switch off recursive search in nautilus to speedup it. But when i want to use recursive search i should go to the setting and switching it on again. I even tried to replace nautilus with another file manager, but gnome can't showing desktop items without nautilus. Why type-ahead can't exists as optional setting? Type-ahead still works in open/save dialogs, why it can't be in nautilus? -- 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/181 Title: Drop interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
I wonder how many people's DNS leaked over the year this bug hasn't been addressed. Oh well..it's just your users' security. Canonical is a joke. Please stop endangering your users with your incompetence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725163] [NEW] gnome-shell freezes when logout/shutdown
Public bug reported: Problem: When I click on logout/shutdown option in gnome-shell topbar menu DE freezes for 25sec before providing correct overlay (logout/shutdown window) Gnome: 3.26 Ubuntu: 17.10 gnome-settings-daemon: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 part of log: Oct 20 09:35:42 MegaHulk systemd[2225]: Started GNOME Terminal Server. Oct 20 09:35:59 MegaHulk at-spi2-registr[11456]: Failed to send session response Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client22' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client9' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client8' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client7' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client6' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client3' faile Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client22' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client9' failed to reply before time Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client8' failed to reply before time Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client7' failed to reply before time Oct
[Desktop-packages] [Bug 1707828] Re: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later
** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1707828 Title: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later. I thought this was a once-off problem but it seems to be happening on a couple of artful machines. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:18:51 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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-settings-daemon/+bug/1707828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707828] Re: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1707828 Title: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later. I thought this was a once-off problem but it seems to be happening on a couple of artful machines. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:18:51 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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-settings-daemon/+bug/1707828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724982] Re: gnome-shell freezes on selecting shut down
*** This bug is a duplicate of bug 1725163 *** https://bugs.launchpad.net/bugs/1725163 ** This bug has been marked a duplicate of bug 1725163 gnome-shell freezes when logout/shutdown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1724982 Title: gnome-shell freezes on selecting shut down Status in xorg package in Ubuntu: New Bug description: When I click on Shutdown icon from top bar drop down gnome shell freezes for 10 seconds before prompting me with shutdown overlay. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .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: ubuntu:GNOME Date: Thu Oct 19 23:00:43 2017 DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] [1682:c580] InstallationDate: Installed on 2017-08-25 (55 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.84+git1710191830.ba68d7~gd~a version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721783] Re: snap is listed twice as installed but is not installed
Now I've the opposite problem where not all the snaps installed are listed in 'installed packages' ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Confirmed -- 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/1721783 Title: snap is listed twice as installed but is not installed Status in gnome-software package in Ubuntu: Confirmed Bug description: I've been playing with G-S and snaps for a while and now it's in a situation where a snap is displayed twice in the list of installed applications but is actually not installed on the system (cf screenshot) 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 15:44: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=xterm-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/1721783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719105] Re: Ctrl+Alt+T does not open a terminal anymore
*** This bug is a duplicate of bug 1707828 *** https://bugs.launchpad.net/bugs/1707828 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 1707828, 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 1707828 Ctrl+Alt+T to open a terminal appears to do nothing, then the terminal window opens 25 seconds later -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1719105 Title: Ctrl+Alt+T does not open a terminal anymore Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Ctrl+Alt+T does not open a terminal anymore. It was working before the latest updates. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 17:46:50 2017 ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard InstallationDate: Installed on 2017-09-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1719105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725156] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725156/+attachment/4977916/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725156/+attachment/4977918/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725156/+attachment/4977921/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725156/+attachment/4977922/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725156/+attachment/4977923/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725156/+attachment/4977924/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725156/+attachment/4977925/+files/ThreadStacktrace.txt ** 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"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725156 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: Bug crashes several applications. 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: Fri Oct 20 09:29:47 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (0 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=pl_PL.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/1725156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725163] Re: gnome-shell freezes when logout/shutdown
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1725163 Title: gnome-shell freezes when logout/shutdown Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Problem: When I click on logout/shutdown option in gnome-shell topbar menu DE freezes for 25sec before providing correct overlay (logout/shutdown window) Gnome: 3.26 Ubuntu: 17.10 gnome-settings-daemon: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 part of log: Oct 20 09:35:42 MegaHulk systemd[2225]: Started GNOME Terminal Server. Oct 20 09:35:59 MegaHulk at-spi2-registr[11456]: Failed to send session response Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client22' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client9' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client8' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client7' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client6' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client3' faile Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binar
[Desktop-packages] [Bug 137606] Re: an icon view for the fileselectors would be useful
** Changed in: gtk Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/137606 Title: an icon view for the fileselectors would be useful Status in GTK+: In Progress Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Binary package hint: nautilus When using nautilus in lookup mode, i.e. browse for a file for opening or selecting, the list of files is always in list mode. It would be very handy when one can change to icon mode, because then there's automatically a preview. This has especially much value when browsing for an image, say for adding an attachmant in a gmail message within firefox. Note. special lookup screens for example eog already have a preview, but this is a special mode, this should be generic. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/137606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725162] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1715330 *** https://bugs.launchpad.net/bugs/1715330 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 #1715330, 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/1725162/+attachment/4977940/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725162/+attachment/4977942/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725162/+attachment/4977945/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725162/+attachment/4977946/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725162/+attachment/4977947/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725162/+attachment/4977948/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725162/+attachment/4977949/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1715330 gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725162 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Crach happened while I was inserting password for updating packages. Computer froze for 30 second and after that I got it back with the error window and crash 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 Date: Fri Oct 20 09:32:11 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'enable-hot-corners' b'false' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'telegramdesktop.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2017-06-06 (135 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb3e6ce14af:mov0x8(%rdi),%eax PC (0x7fb3e6ce14af) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725169] [NEW] Black Screen after Upgrade from Kubuntu 17.04 to 17.10
Public bug reported: I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the same Result: After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'. This kernel does not work with the nvidia-grafic-card and lead to a black screen. After purging this kernel in a tty-session it booted up smothely. I think this can help many others. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Oct 20 09:57:26 2017 DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] [1458:362d] InstallationDate: Installed on 2016-12-23 (300 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a:4102 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22d dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful kubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725169 Title: Black Screen after Upgrade from Kubuntu 17.04 to 17.10 Status in xorg package in Ubuntu: New Bug description: I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the same Result: After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'. This kernel does not work with the nvidia-grafic-card and lead to a black screen. After purging this kernel in a tty-session it booted up smothely. I think this can help many others. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.
[Desktop-packages] [Bug 1725163] Re: gnome-shell freezes when logout/shutdown
Tried unplugging camera, problems are gone. Cheese is starting instantly (with camera plugged in 33 seconds), shutdown/logout are instant (with camera 25- 30 sec, didn't measure exact time). Camera make and model: Logitech c525 lsusb: Bus 003 Device 009: ID 046d:0826 Logitech, Inc. HD Webcam C525 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x046d Logitech, Inc. idProduct 0x0826 HD Webcam C525 bcdDevice0.10 iManufacturer 0 iProduct2 HD Webcam C525 iSerial 1 AF850BA0 bNumConfigurations 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1725163 Title: gnome-shell freezes when logout/shutdown Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Problem: When I click on logout/shutdown option in gnome-shell topbar menu DE freezes for 25sec before providing correct overlay (logout/shutdown window) Gnome: 3.26 Ubuntu: 17.10 gnome-settings-daemon: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 part of log: Oct 20 09:35:42 MegaHulk systemd[2225]: Started GNOME Terminal Server. Oct 20 09:35:59 MegaHulk at-spi2-registr[11456]: Failed to send session response Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client22' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client9' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client8' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client7' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client6' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client3' faile Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before tim
[Desktop-packages] [Bug 1725163] Re: gnome-shell freezes when logout/shutdown
I think that this might be related to: https://bugzilla.gnome.org/show_bug.cgi?id=783789 https://bugzilla.gnome.org/show_bug.cgi?id=782627 ** Bug watch added: GNOME Bug Tracker #783789 https://bugzilla.gnome.org/show_bug.cgi?id=783789 ** Bug watch added: GNOME Bug Tracker #782627 https://bugzilla.gnome.org/show_bug.cgi?id=782627 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1725163 Title: gnome-shell freezes when logout/shutdown Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Problem: When I click on logout/shutdown option in gnome-shell topbar menu DE freezes for 25sec before providing correct overlay (logout/shutdown window) Gnome: 3.26 Ubuntu: 17.10 gnome-settings-daemon: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 part of log: Oct 20 09:35:42 MegaHulk systemd[2225]: Started GNOME Terminal Server. Oct 20 09:35:59 MegaHulk at-spi2-registr[11456]: Failed to send session response Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client22' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client9' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client8' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client7' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client6' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client3' faile Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNI
[Desktop-packages] [Bug 1725160] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode()
Many/most laptops with hybrid graphics don't have the discrete GPU wired to the internal screen. If that includes you then discrete-only mode might only work with an external monitor attached. Because typically the Nvidia GPU is wired to at least one HDMI/DisplayPort, but not usually the laptop panel. Usually only the Intel GPU is attached to the laptop LCD. ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode() + gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() -- 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/1725160 Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: New Bug description: Having an NVidia Optimus type laptop graphics card, this happened after installing nvidia drivers (from the software update/additional drivers screen) and rebooting in discrete mode (so NVidia only) 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-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Oct 20 08:49:10 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-04-29 (173 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fdd1a378a6f : mov0x8(%rax),%rcx PC (0x7fdd1a378a6f) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_manager_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_kms_apply_crtc_mode() UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724805] Re: wpa_supplicant fails to shutdown
Know problem with Kernel 4.13. 4.13.8 works for me. ** Description changed: Ubuntu 17.10 wpasupplicant 2.4-0ubuntu10 System shutdown hangs because wpa_supplicant is not stopping itself. Test with: $ sudo systemctl stop wpa_supplicant Journal shows: 11:37:32 systemd[1]: Stopping WPA supplicant... 11:37:32 wpa_supplicant[941]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 11:37:32 wpa_supplicant[941]: p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING 11:37:32 kernel: wlp2s0: deauthenticating from by local choice (Reason: 3=DEAUTH_LEAVING) 11:39:02 systemd[1]: wpa_supplicant.service: State 'stop-sigterm' timed out. Killing. 11:39:02 systemd[1]: wpa_supplicant.service: Killing process 941 (wpa_supplicant) with signal SIGKILL. 11:40:33 systemd[1]: wpa_supplicant.service: Processes still around after SIGKILL. Ignoring. 11:42:03 systemd[1]: wpa_supplicant.service: State 'stop-final-sigterm' timed out. Killing. 11:42:03 systemd[1]: wpa_supplicant.service: Killing process 941 (wpa_supplicant) with signal SIGKILL. 11:43:33 systemd[1]: wpa_supplicant.service: Processes still around after final SIGKILL. Entering failed mode. 11:43:33 systemd[1]: Stopped WPA supplicant. 11:43:33 systemd[1]: wpa_supplicant.service: Unit entered failed state. 11:43:33 systemd[1]: wpa_supplicant.service: Failed with result 'timeout'. - - System is a Lenovo Yoga 510-14ISK - lspci output: - 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) - 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) - 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) - 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) - 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) - 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) - 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) - 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) - 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) - 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) - 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) - 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) - 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) - 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) - 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) - 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 30) - 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) - P.S. also shows this bug, but reporting much more frequently then 2 minutes: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1724805 Title: wpa_supplicant fails to shutdown Status in wpa package in Ubuntu: New Bug description: Ubuntu 17.10 wpasupplicant 2.4-0ubuntu10 System shutdown hangs because wpa_supplicant is not stopping itself. Test with: $ sudo systemctl stop wpa_supplicant Journal shows: 11:37:32 systemd[1]: Stopping WPA supplicant... 11:37:32 wpa_supplicant[941]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 11:37:32 wpa_supplicant[941]: p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING 11:37:32 kernel: wlp2s0: deauthenticating from by local choice (Reason: 3=DEAUTH_LEAVING) 11:39:02 systemd[1]: wpa_supplicant.service: State 'stop-sigterm' timed out. Killing. 11:39:02 systemd[1]: wpa_supplicant.service: Killing process 941 (wpa_supplicant) with signal SIGKILL. 11:40:33 systemd[1]: wpa_supplicant.service: Processes still around after SIGKILL. Ignoring. 11:42:03 systemd[1]: wpa_supplicant.service: State 'stop-final-sigterm' timed out. Killing. 11:42:03 systemd[1]: wpa_supplicant.service: Killing process 941 (wpa_supplicant) with signal SIGKILL. 11:43:33 systemd[1]: wpa_supplicant.service: Processes still around after final SIGKILL. Entering failed mode. 11:43:33 systemd[1]: Stopped WPA supplicant. 11:43:33 systemd[1]: wpa_supplicant.service: Unit entered failed state. 11:43:33 systemd[1]: wpa_supplicant.service: Failed with result 'timeout'. lspci output: 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 3
[Desktop-packages] [Bug 1725180] [NEW] xwayland animations are not smooth
Public bug reported: +++UBUNTU RELEASE+++ Description:Ubuntu 17.10 Release:17.10 +++PACKAGE VERSION+++ xwayland: Installed: 2:1.19.5-0ubuntu2 Candidate: 2:1.19.5-0ubuntu2 Version table: *** 2:1.19.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050. Currently using Intel HD Graphics 630. The window/dock/launcher animations are lagging/shaky (not smooth). Still yet to try switching to Nvidia GTX 1050 prime profile and see if the problem persists. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 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: ubuntu:GNOME Date: Fri Oct 20 19:09:27 2017 DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-05-24 (149 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful possible-manual-nvidia-install ubuntu wayland-session -- 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/1725180 Title: xwayland animations are not smooth Status in xorg-server package in Ubuntu: New Bug description: +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ xwayland: Installed: 2:1.19.5-0ubuntu2 Candidate: 2:1.19.5-0ubuntu2 Version table: *** 2:1.19.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050. Currently using Intel HD Graphics 630. The window/dock/launcher animations are lagging/shaky (not smooth). Still yet to try switching to Nvidia GTX 1050 prime profile and see if the problem persists. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 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: ubuntu:GNOME Date: Fri
[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
Hi, just adding part of syslog. Time stamps: 9:50 - monitor switch off, 10:22 - switch on. ** Attachment added: "crash_syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/+attachment/4978078/+files/crash_syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)
I'm seeing this now myself. Maybe because I recently added a user picture to my account? ** Tags added: visual-quality -- 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/1724098 Title: Panel menu icons are briefly way too big (when opened the first time) Status in gnome-shell package in Ubuntu: New Bug description: On every fresh boot, the first time when you click the drop down menu for SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY THE FIRST TIME WHEN YOU RESTART the machine!! --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com'] org.gnome.shell app-picker-view uint32 1 org.gnome.shell favorite-apps ['chromium-browser.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop'] org.gnome.desktop.interface enable-animations false org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' InstallationDate: Installed on 2017-08-31 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful 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/ubuntu/+source/gnome-shell/+bug/1724098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 263637] Re: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab
This is still a problem in Ubuntu 17.10, if your shell doesn't use OSC 7 to inform gnome-terminal about the current working directory. In theory /etc/profile.d/vte-2.91.sh should set it up automatically, but for some reason that doesn't happen for me. I think that reason is because in Ubuntu gnome-terminal doesn't launch login shells by default, and thus /etc/profile is ignored. I don't know why the commits from 2012 that are supposed to check $PWD do not work any more. Perhaps a newer version removed them, when the OSC 7 was deemed to be the correct solution? -- 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/263637 Title: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Bug description: Binary package hint: gnome-terminal 1) cd /tmp 2) mkdir -p A/AA 3) mkdir B 4) cd B 5) ln -s ../A/AA 6) cd AA The current directory is /tmp/B/AA. Open a new tab, you're now in /tmp/A/AA. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/263637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] [NEW] Please update modemmanager in xenial to the 1.6 series
Public bug reported: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems. These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Description changed: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems. These are the packages that would need to be updated: - xenialin snap - libmbim 1.12.2-2ubuntu1 1.14.0 - libqmi 1.12.6-1 1.16.2 - modemmanager 1.4.12-1ubuntu1 1.6.2 + libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap + libqmi: 1.12.6-1 in xenial, 1.16.2 in snap + modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in modemmanager package in Ubuntu: New Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems. These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725153] Re: Reintroduce headless mode in GNOME Shell
** Bug watch added: GNOME Bug Tracker #789153 https://bugzilla.gnome.org/show_bug.cgi?id=789153 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=789153 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/1725153 Title: Reintroduce headless mode in GNOME Shell Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Impact] * I day before the 17.10 release, we had to revert some commits in GNOME Shell due to https://bugs.launchpad.net/gnome-shell/+bug/1723577 which was a release blocker (GNOME Shell not displaying anything on multiple config). * Pinging upstream, they debugged it and found the real issue in mutter, and so fixed it, which will enable us to align again with upstream's repo. * This should mostly be a no visible-effect for previously impacted users, but GNOME Shell shouldn't crash anymore in GDM (reverting then to Xorg), triggering apport on logging, and the users can then use Wayland instead of Xorg. [Test Case] * Install both mutter and gnome-shell to their latest version in -proposed * Reboot * Ensure you have an UI in GDM * Log in into your session, check that you have an UI and everything is showing up as expected [Regression Potential] * Impact is a regression in GNOME Shell (showing up your entire UI) and not being able to log in. However, some of us (not impated by the bug) are already running latest version and don't see any issue. I have also asked 3 people being impacted by the bug and fixed by the revert to test upstream commits (prepared a package for them in a PPA), and they are running on it since yesterday, confirming Wayland is available. * The regressions are quite straightfoward to see: either you have an UI in GDM or none. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1725153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725180] Re: xwayland animations are not smooth
** Description changed: +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ xwayland: - Installed: 2:1.19.5-0ubuntu2 - Candidate: 2:1.19.5-0ubuntu2 - Version table: - *** 2:1.19.5-0ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages - 100 /var/lib/dpkg/status - + Installed: 2:1.19.5-0ubuntu2 + Candidate: 2:1.19.5-0ubuntu2 + Version table: + *** 2:1.19.5-0ubuntu2 500 + 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages + 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050. Currently using Intel HD Graphics 630. The window/dock/launcher animations are lagging/shaky (not smooth). - Still yet to try switching to Nvidia GTX 1050 prime profile and see if - the problem persists. + Animations are smooth and working as intended when using Nvidia GTX1050. + + __ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 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: ubuntu:GNOME Date: Fri Oct 20 19:09:27 2017 DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: - bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed - bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed - nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed - v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed - v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed + bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed + bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed + nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed + v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed + v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:07be] -Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] + Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:07be] + Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-05-24 (149 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. - Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. - Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. + Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. + Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: - LANGUAGE=en_AU:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A -- You receiv
[Desktop-packages] [Bug 1725189] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725189/+attachment/4978139/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725189/+attachment/4978141/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725189/+attachment/4978144/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725189/+attachment/4978145/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725189/+attachment/4978146/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725189/+attachment/4978147/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725189/+attachment/4978148/+files/ThreadStacktrace.txt ** 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"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725189 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: i'm running gnome-shell with xorg 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: Thu Oct 19 20:55:32 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (0 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=en_US.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/1725189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725153] Re: Reintroduce headless mode in GNOME Shell
** Changed in: gnome-shell Status: Unknown => Fix Released ** 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/1725153 Title: Reintroduce headless mode in GNOME Shell Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Impact] * I day before the 17.10 release, we had to revert some commits in GNOME Shell due to https://bugs.launchpad.net/gnome-shell/+bug/1723577 which was a release blocker (GNOME Shell not displaying anything on multiple config). * Pinging upstream, they debugged it and found the real issue in mutter, and so fixed it, which will enable us to align again with upstream's repo. * This should mostly be a no visible-effect for previously impacted users, but GNOME Shell shouldn't crash anymore in GDM (reverting then to Xorg), triggering apport on logging, and the users can then use Wayland instead of Xorg. [Test Case] * Install both mutter and gnome-shell to their latest version in -proposed * Reboot * Ensure you have an UI in GDM * Log in into your session, check that you have an UI and everything is showing up as expected [Regression Potential] * Impact is a regression in GNOME Shell (showing up your entire UI) and not being able to log in. However, some of us (not impated by the bug) are already running latest version and don't see any issue. I have also asked 3 people being impacted by the bug and fixed by the revert to test upstream commits (prepared a package for them in a PPA), and they are running on it since yesterday, confirming Wayland is available. * The regressions are quite straightfoward to see: either you have an UI in GDM or none. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1725153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
After chatting with sil2100, he said that potentially we could backport artful 1.6.8 modemmanager to xenial, which would be great. I have created bug #1725190 to track that and start in a clean state from there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in modemmanager package in Ubuntu: Confirmed Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725077] Re: configuration crahses when signing into online accounts
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 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 1720400, 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 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1725077 Title: configuration crahses when signing into online accounts Status in gnome-control-center package in Ubuntu: New Bug description: happened when loggin in into my facebook account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 282688] Re: patch adds ubuntu specific pref in global namespace
2017 update: - there's no gconf - there's no alternate_screel_scroll preference added by ubuntu patches - but there are some new transparency-related preferences added to the gsettings schema The current patch at https://patches.ubuntu.com/g/gnome-terminal/gnome- terminal_3.24.2-0ubuntu4.patch adds these preferences - use-transparent-background - use-theme-transparency - background-transparency-percent However I believe the same transparency patch is also shipped by Debian and Fedora, so an ubuntu prefix would not be appropriate. Perhaps this bug ought to be closed? -- 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/282688 Title: patch adds ubuntu specific pref in global namespace Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-terminal This patch in ubuntu's gnome-terminal package http://patches.ubuntu.com/g/gnome- terminal/extracted/20_add_alt_screen_toggle_ui.patch adds a gconf pref, but the pref name is not namespaced in any way to ubuntu. Please add namespacing (e.g. name it ubuntu_alternate_screen_scroll) as to not constrain upstream should it accept this patch in a modified form with a different meaning to the pref. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/282688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
** Description changed: We would like to upgrade xenial to 1.6 series so it supports the same - modems as the modem-manager snap, specifically some new Sierra modems. - These are the packages that would need to be updated: + modems as the modem-manager snap, specifically some new Sierra modems + (HL8548 and others from HL series, popular in IoT devices). These are + the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724431] Re: gnome-control-center crashed with SIGSEGV after reducing items retrieved via google account
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 ** This bug is no longer a duplicate of bug 1724011 gnome-control-center crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1724431 Title: gnome-control-center crashed with SIGSEGV after reducing items retrieved via google account Status in gnome-control-center package in Ubuntu: New Bug description: I had added a google account which then adds all subfunctions. Through the calendar app I adjusted the account settings to a subset. This completed but then resulted in a crash. 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 20:20:51 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: /usr/bin/gnome-control-center ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff33d18ab3b:mov0x8(%rax),%rax PC (0x7ff33d18ab3b) 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/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so Title: gnome-control-center crashed with SIGSEGV 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/1724431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724011] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 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 1720400, 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 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1724011 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: Confirmed Bug description: added google account, then switched to new tab in settings. 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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 19:35:17 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f087bd3fb3b:mov0x8(%rax),%rax PC (0x7f087bd3fb3b) 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/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so Title: gnome-control-center crashed with SIGSEGV 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/1724011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724908] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 ** This bug is no longer a duplicate of bug 1724011 gnome-control-center crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1724908 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: was adding web accounts to the system, got this error. 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 10:26:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-11-13 (339 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feba72aeb3b:mov0x8(%rax),%rax PC (0x7feba72aeb3b) 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/vmwgfx_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725199] Re: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
*** This bug is a duplicate of bug 1680984 *** https://bugs.launchpad.net/bugs/1680984 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 #1680984, 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/1725199/+attachment/4978168/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725199/+attachment/4978170/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725199/+attachment/4978173/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725199/+attachment/4978174/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725199/+attachment/4978175/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725199/+attachment/4978176/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725199/+attachment/4978177/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1680984 ** 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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1725199 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() Status in gnome-terminal package in Ubuntu: New Bug description: backspace button make the terminal crash. And When i try to delete shortcut terminal in profile with backspace, it make crash Terminal as well. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-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: Fri Oct 20 10:55:43 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-11 (9 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fb569b2a77e : testb $0x4,0x16(%rdx) PC (0x7fb569b2a77e) ok source "$0x4" ok destination "0x16(%rdx)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/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 1724579] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 ** This bug is no longer a duplicate of bug 1724011 gnome-control-center crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1724579 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Crash when trying to remove/add a google account under "Online Accounts" 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 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 18 08:34:23 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-04-21 (179 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f69a0027b3b:mov0x8(%rax),%rax PC (0x7f69a0027b3b) 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: () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-17 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724993] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 ** This bug is no longer a duplicate of bug 1724011 gnome-control-center crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1724993 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: Description: Ubuntu 17.10 Release: 17.10 The error occurred when I was setting up online accounts. apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.26.1-0ubuntu4 Candidate: 1:3.26.1-0ubuntu4 Version table: *** 1:3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 16:21:54 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9ce9ab0b3b:mov0x8(%rax),%rax PC (0x7f9ce9ab0b3b) 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/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so Title: gnome-control-center crashed with SIGSEGV 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/1724993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 792341] Re: gnome-terminal is sometimes not adding trailing slash when [Tab] used
Tab-completion is implemented by your shell (bash, most likely), not by
gnome-terminal.
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed => Invalid
** Also affects: bash (Ubuntu)
Importance: Undecided
Status: New
--
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/792341
Title:
gnome-terminal is sometimes not adding trailing slash when [Tab] used
Status in bash package in Ubuntu:
New
Status in gnome-terminal package in Ubuntu:
Invalid
Bug description:
Binary package hint: gnome-terminal
Steps to reproduce :
$ mkdir test && cd test
$ mkdir target
$ ln -s target backup
$ ls -l
lrwxrwxrwx 1 tomasz tomasz6 2011-06-03 14:22 backup -> target/
drwxr-xr-x 2 tomasz tomasz 4096 2011-06-03 14:22 target/
Now try:
$ cd ta
$ cd ba
Pressing [Tab] expands "ta" to "target/", while "ba" is only expanded
to "backup" (notice no trailing slash). Although it's consistent with
ls output, it is a bit counterintuitive, as logically both "target"
and "backup" are accessible directories.
What's even more interesting, pressing [Tab] again when "ba" is
already expanded to "backup" will add the trailing slash ("backup/").
Also I noticed xterm behaves exactly the same, so the reason must be
somewhere deeper.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gnome-terminal 2.32.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Jun 3 14:17:01 2011
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
LANGUAGE=pl_PL:en
PATH=(custom, user)
LANG=pl_PL.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/bash/+bug/792341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902679] Re: Alt 1, 2, etc does not change terminal page
** Summary changed: - Alt 1,2,etc does to change terminal page + Alt 1,2,etc does not change terminal page -- 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/902679 Title: Alt 1,2,etc does not change terminal page Status in gnome-terminal package in Ubuntu: New Bug description: In Gnome Terminal used to be able to move between tabs by using Alt-1 for first tab etc. In Keyboard Shortcuts it lists Alt+1 etc for moving between tabs. Alt brings up menu at top, but does not move between tabs when 1-9 is pressed. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Dec 11 08:55:13 2011 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) 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/902679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 263637] Re: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab
I've just noticed that Debian carries a patch for reading the working directory from /proc if OSC 7 was not in use. This patch doesn't have the "let's look for $PWD in the environment" logic that was supposed to fix this bug. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712628 ** Bug watch added: Debian Bug tracker #712628 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712628 -- 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/263637 Title: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Bug description: Binary package hint: gnome-terminal 1) cd /tmp 2) mkdir -p A/AA 3) mkdir B 4) cd B 5) ln -s ../A/AA 6) cd AA The current directory is /tmp/B/AA. Open a new tab, you're now in /tmp/A/AA. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/263637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885148] Re: Spurious blank lines in gnome-terminal
I've seen this kind of problem when my disk was full. Since gnome- terminal stores the scrollback buffer in a (deleted) file in /tmp, when the disk fills up, scrollback gets lost. -- 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/885148 Title: Spurious blank lines in gnome-terminal Status in gnome-terminal package in Ubuntu: New Bug description: Easiest way to see this is to list directories using 'ls' with more than 30 files. Using gnome-terminal, the last 29 lines of stdout are correctly printed. The first lines are replaced entirely by whitespace. Using Xterm does not show this problem - all files are listed. Unity is in use as my desktop under Ubuntu 11.10. I have also seen this problem with 'diff'. If too many lines are output, the first few are replaced by whitespace. I made a slight change to the default gnome-terminal profile, to set the scroll back lines to 5120. I do not know whether this problem occurred before altering the profile. I have however since set this back to the default 512. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Nov 2 10:43:16 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.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/885148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724078] Re: Multiple applications crash on 17.10 with "Not a JPEG file: starts with 0xff 0xff"
I have the trouble with a samsung scannner # sane-find-scanner found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x3430 [SCX-5635 Series]) at libusb:001:002 I have installed the samsung driver coming from samsung website but sane continue to use the xerox driver # scanimage -L device `xerox_mfp:libusb:001:002' is a Samsung Samsung SCX-5635 Series multi-function peripheral When I try another output format, I have the same error # scanimage --format pnm > /tmp/out.pnm Not a JPEG file: starts with 0xff 0xff -- 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/1724078 Title: Multiple applications crash on 17.10 with "Not a JPEG file: starts with 0xff 0xff" Status in sane-backends package in Ubuntu: Confirmed Bug description: Each time I try to use simple-scan on 17.10, I have got a crash. $ simple-scan Not a JPEG file: starts with 0xff 0xff same error (crash) with gscan2pdf $ gscan2pdf /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Not a JPEG file: starts with 0xff 0xff and same error with xscanimage $ xscanimage /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Not a JPEG file: starts with 0xff 0xff ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 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: Mon Oct 16 22:55:43 2017 InstallationDate: Installed on 2017-10-05 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1724078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
@Kai-Heng: the problem is fixed here using your 4.4.0-99 version on my Dell Latitude E7470 with Skylake. Well it's buggy like on 4.4.0-72, after loggin both screens go black, but I have my workaround works again. If I switch to text mode (Ctrl+Alt+F1) and back (Alt+F7) both screens work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
upgrade to 1.6.8 look good to me. AlexTu: can you also comment ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in modemmanager package in Ubuntu: Confirmed Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored
The bug is still present in 17.10. -- 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/1288655 Title: terminal gets smaller when maximized and then restored Status in gnome-terminal package in Ubuntu: Confirmed Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 932940] Re: gnome-terminal intercepts ctrl-f1 making it unusable for applications running within
This seems fixed? I can open gnome-terminal, run cat, hit Ctrl+F1 and see ^[[1;5P ** Changed in: gnome-terminal (Ubuntu) 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/932940 Title: gnome-terminal intercepts ctrl-f1 making it unusable for applications running within Status in gnome-terminal package in Ubuntu: Fix Released Bug description: I can get F2-F4 to work in emacs by using the escape sequences echoed in gnome-terminal when pressing them together with a modifier but CTRL-F1 does nothing at all. It seems it is a shortcut for something but I can't find a place to unbind it or see what is supposed to happen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Feb 15 18:49:23 2012 EcryptfsInUse: Yes SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2009-09-11 (887 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/932940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 978173] Re: $PATH not being honored
** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- 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/978173 Title: $PATH not being honored Status in gnome-terminal package in Ubuntu: Invalid Bug description: Deimos ~/bin> ls -l -rwxrwxr-x 1 doug doug 25 2012-04-10 10:10 firefox -rwx--x--x 1 doug doug 7236 2011-11-01 11:30 Firefox.pl -rwx--x--x 1 doug doug220 2011-11-01 11:30 Run_in_tcsh -rwx--x--x 1 doug doug 384456 2011-11-01 11:30 tcsh -rwx--x--x 1 doug doug 3197 2011-11-01 11:30 xorit A few have been snipped. Deimos ~/bin> cat firefox /usr/bin/firefox -P default $1 & Deimos ~/bin> echo $PATH /home/doug/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games Deimos ~/bin> which firefox /usr/bin/firefox I want my personal versions to be executed when they come first in my path. They always used to but that was in real UNIX or before this version of ubuntu. /home/doug/bin/firefox works just the way I want it. Yes, I use tcsh but I get the same performance in bash. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-18.31-generic 3.0.26 Uname: Linux 3.0.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Apr 10 10:22:30 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) 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/978173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 989611] Re: terminal not working properly problem inside usr/bin
** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Incomplete -- 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/989611 Title: terminal not working properly problem inside usr/bin Status in gnome-terminal package in Ubuntu: Incomplete Bug description: terminal is empty.No user or root at all ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Apr 27 16:36:39 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN 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/989611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1341667] Re: Ctrl+Backspace should send ^W instead of doing the same thing as Backspace
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion -- 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/1341667 Title: Ctrl+Backspace should send ^W instead of doing the same thing as Backspace Status in gnome-terminal package in Ubuntu: Opinion Bug description: I'm using Linux Mint 17. In the Gnome Terminal when hitting Ctrl+Backspace just one character is being deleted (^H). In normal Gtk+ applications this key combination deletes the previous word (Ctrl+W) in Bash. There's also no way for Bash to distinguish between Ctrl+Backspace and Backspace. Therefore I think there should be an option to send ^W on Ctrl+Backspace or Ctrl+Backspace should be distinguishable for Bash so that I can bind it myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1341667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406980] Re: /etc/profile does not get sourced when logging into a terminal window
Ubuntu's default ~/.bashrc (copied over from /etc/skel/.bashrc when you
create new user accounts) overrides PS1 when $TERM is xterm*. When you
open new terminal windows or tabs, bash sources /etc/bash.bashrc and
then ~/.bashrc, and thus your global PS1 setting is overwritten.
Do the change in ~/.bashrc instead of in /etc and you'll be fine.
** Changed in: gnome-terminal (Ubuntu)
Status: New => Invalid
--
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/1406980
Title:
/etc/profile does not get sourced when logging into a terminal window
Status in gnome-terminal package in Ubuntu:
Invalid
Bug description:
I wanted to change the command prompt and so made the following change
within /etc/bash.bashrc:
#PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
PS1='${debian_chroot:+($debian_chroot)}\h:\w\$ '
When a terminal window is opened, the prompt is unchanged from the
original. If I reboot, login and again open a terminal window the
prompt is still unchanged. However, manually executing the following
from the terminal window changes the prompt as desired:
source /etc/profile
It seems that /etc/profile is not automatically run when the terminal
window is first opened.
From the documentation I've seen
(https://help.ubuntu.com/community/EnvironmentVariables,
http://bencane.com/2013/09/16/understanding-a-little-more-about-
etcprofile-and-etcbashrc/ and other posts), /etc/bash.bashrc should be
executed from /etc/profile during a terminal login.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.6
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Jan 1 14:36:48 2015
InstallationDate: Installed on 2014-09-12 (111 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
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/1406980/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1356433] Re: detached tabs can not be reattached
Current versions of gnome-terminal (3.24 in Ubuntu 17.10) no longer allow you to detach and reattach tabs via drag and drop. Instead there's a context menu option that lets you detach tabs, but AFAICS there's no way to reattach them back. -- 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/1356433 Title: detached tabs can not be reattached Status in gnome-terminal package in Ubuntu: Confirmed Bug description: If you detach a tab in Gnome-terminal (exen accidentally while trying to reorder tabs) it will never reattach to the tabbed window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 13 10:28:50 2014 InstallationDate: Installed on 2014-02-19 (174 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218) 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/1356433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1429584] Re: gnome-terminal doesn't set $COLORTERM from 3.14 onwards
** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Opinion -- 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/1429584 Title: gnome-terminal doesn't set $COLORTERM from 3.14 onwards Status in gnome-terminal package in Ubuntu: Opinion Bug description: Gnome terminal has dropped the $COLORTERM workaround for invalid terminfo/termcap. References: https://github.com/GNOME/gnome-terminal/commit/1d5c1b6ca6373c1301494edbc9e43c3e6a9c9aaf https://bugzilla.redhat.com/show_bug.cgi?id=1165439 https://bugzilla.redhat.com/show_bug.cgi?id=1173688 https://bugzilla.redhat.com/show_bug.cgi?id=1166428 This affects release: Vivid Vervet Workaround I currently use is `.bashrc`: if [ -z "$COLORTERM" ] && cat /proc/$PPID/exe 2> /dev/null | grep -q gnome-terminal; then export COLORTERM=gnome-terminal fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1429584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406980] Re: /etc/profile does not get sourced when logging into a terminal window
(Although TBH you're right when you say /etc/profile isn't sourced on
Ubuntu -- that's because the default gnome-terminal profile doesn't run
the shell as a login shell. There's a checkbox in the profile
preferences dialog you can toggle to enable that.)
--
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/1406980
Title:
/etc/profile does not get sourced when logging into a terminal window
Status in gnome-terminal package in Ubuntu:
Invalid
Bug description:
I wanted to change the command prompt and so made the following change
within /etc/bash.bashrc:
#PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
PS1='${debian_chroot:+($debian_chroot)}\h:\w\$ '
When a terminal window is opened, the prompt is unchanged from the
original. If I reboot, login and again open a terminal window the
prompt is still unchanged. However, manually executing the following
from the terminal window changes the prompt as desired:
source /etc/profile
It seems that /etc/profile is not automatically run when the terminal
window is first opened.
From the documentation I've seen
(https://help.ubuntu.com/community/EnvironmentVariables,
http://bencane.com/2013/09/16/understanding-a-little-more-about-
etcprofile-and-etcbashrc/ and other posts), /etc/bash.bashrc should be
executed from /etc/profile during a terminal login.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.6
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Jan 1 14:36:48 2015
InstallationDate: Installed on 2014-09-12 (111 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
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/1406980/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored
Bug 1233205 was a bug in Unity and/or Compiz. Ubuntu 17.10 uses gnome- shell. -- 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/1288655 Title: terminal gets smaller when maximized and then restored Status in gnome-terminal package in Ubuntu: Confirmed Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724078] Re: Multiple applications crash on 17.10 with "Not a JPEG file: starts with 0xff 0xff"
Possible dupe of lp:1723422 -- 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/1724078 Title: Multiple applications crash on 17.10 with "Not a JPEG file: starts with 0xff 0xff" Status in sane-backends package in Ubuntu: Confirmed Bug description: Each time I try to use simple-scan on 17.10, I have got a crash. $ simple-scan Not a JPEG file: starts with 0xff 0xff same error (crash) with gscan2pdf $ gscan2pdf /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Not a JPEG file: starts with 0xff 0xff and same error with xscanimage $ xscanimage /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Not a JPEG file: starts with 0xff 0xff ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 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: Mon Oct 16 22:55:43 2017 InstallationDate: Installed on 2017-10-05 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1724078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723313] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:dri_image_drawable_get_buffers:dri2_allocate_textures:dri_st_framebuffer_validate
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 @seb128 This should be the same as bug #1720400. It shows a slightly different stacktrace but the cause it the same. Marking as duplicate. ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1723313 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:dri_image_drawable_get_buffers:dri2_allocate_textures:dri_st_framebuffer_validate Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/4cbf7bbc2c23ee6e7c095d5d4c45db1390e30c3f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1723313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
sounds good, if we just use latest modemmanager, it will be easier to apply further fix in the future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in modemmanager package in Ubuntu: Confirmed Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
Thanks for your testing. The blank screen issue was always there, right? I think use modesetting driver instead of intel DDX should fix the issue. You can either use xorg.config or "apt purge xserver-xorg-video-intel" to switch to modesetting driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694089] Re: /usr/bin/gnome-control-center:11:_cogl_check_extension:_cogl_feature_check:update_base_winsys_features:_cogl_winsys_renderer_connect:cogl_renderer_connect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1694089 Title: /usr/bin/gnome-control- center:11:_cogl_check_extension:_cogl_feature_check:update_base_winsys_features:_cogl_winsys_renderer_connect:cogl_renderer_connect Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.24.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b719206160e0f35c9a5aecf2332cc3c9375b2a82 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-control-center/+bug/1694089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723671] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 ** This bug is no longer a duplicate of bug 1723313 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:dri_image_drawable_get_buffers:dri2_allocate_textures:dri_st_framebuffer_validate ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1723671 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: After setting a google online account gnome-control-center accidentally froze and crashed. 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 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 01:23:52 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f62e7e25b3b:mov0x8(%rax),%rax PC (0x7f62e7e25b3b) 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: 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/1723671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1496829] Re: when the set command is passed without any parameters it throws some sort of source code on the screen
`set` is a bash builtin command that displays the names values of all shell variables when invoked without any arguments. Shell functions are implemented as variables, technically (although you cannot see the body of the function with echo $functionname). This is working as designed and has noting to do with gnome-terminal. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- 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/1496829 Title: when the set command is passed without any parameters it throws some sort of source code on the screen Status in gnome-terminal package in Ubuntu: Invalid Bug description: when ever I type in the set command with out any parameters it throws unexpected behaviour . Though I am not yet any expert in Computer world but I am sure it is not supposed to reveal any sort of code . ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 17 17:39:26 2015 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2015-08-07 (40 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=en_IN LANGUAGE=en_IN:en XDG_RUNTIME_DIR= 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/1496829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1525579] Re: terminal freezes when I use : run-mozilla.sh
** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- 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/1525579 Title: terminal freezes when I use : run-mozilla.sh Status in gnome-terminal package in Ubuntu: Incomplete Bug description: i cannot update firefox-3.0 to firefox-42.0. ProblemType: Bug Architecture: i386 DistroRelease: LinuxMint 7 ExecutablePath: /usr/bin/gnome-terminal Package: gnome-terminal 2.26.0-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal Uname: Linux 2.6.28-11-generic i686 UnreportableReason: This is not a genuine LinuxMint package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1525579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637688] Re: Terminal and file manager scrolls inverted
The old way of mouse wheel scrolling was mice would emit discrete button 4 and 5 events, and scrolling was jumpy. The new way of mouse wheel scrolling is via XInput2, you get two additional axes (vertical and horizontal scroll events) that give you more fine-grained positions. This way you can get smooth scrolling with a touchpad. When you remap mouse buttons, this can only affect older applications that do not support smooth mouse wheel scrolling. -- 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/1637688 Title: Terminal and file manager scrolls inverted Status in gnome-terminal package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I'm having this issue, all other programs are scrolling as "Natural Scrolling", just like Mac does, however only Terminal and File browser have "Reversed Scrolling", they should be consistent across apps and programs, maybe it's nautilus the one that inverts the scrolling? Only could find this issue in Terminal and File Browser, attaching bug info from terminal. Release version: Description: Ubuntu 16.10 Release: 16.10 Terminal version: Not sure, it should be the latest one that comes with this Ubuntu version. Expected behavior: I expected to scroll in the same direction as all other apps in my OS. Current Behavior: I scrolled up with mouse wheel, with "Natural Scrolling" all apps scroll down, but terminal and file manager scrolls up, it is indeed inverted. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.20.2-1ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 22:04:54 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-02-20 (251 days ago) InstallationMedia: SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-16 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535169] Re: specify error
What are the steps to reproduce this? When I run gnome-terminal in a
terminal window in 17.10 all I get is
Warning: DESKTOP_STARTUP_ID not set and no fallback available.
This doesn't change if I export PYTHONWARNINGS=all beforehand.
--
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/1535169
Title:
specify error
Status in gnome-terminal package in Ubuntu:
New
Bug description:
sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use
gi.require_version('Wnck', '3.0') before import to ensure that the right
version gets loaded.
sys:1: PyGIWarning: GdkX11 was imported without specifying a version first.
Use gi.require_version('GdkX11', '3.0') before import to ensure that the right
version gets loaded.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
sand@sand-pc:~$
[13548:13548:0117/212355:ERROR:background_mode_manager_aura.cc(14)] Not
implemented reached in virtual void
BackgroundModeManager::EnableLaunchOnStartup(bool)
[13548:13779:0117/212403:ERROR:cert_verify_proc_nss.cc(922)]
CERT_PKIXVerifyCert for 192.168.1.9 failed err=-8179
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 17 21:22:04 2016
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2015-11-23 (55 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
XDG_RUNTIME_DIR=
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to xenial on 2015-11-25 (53 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1535169/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion ** Changed in: vte2.91 (Ubuntu) Status: New => Opinion ** Changed in: ubuntu-gnome Status: New => Opinion -- 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/1609009 Title: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead) Status in Ubuntu GNOME: Opinion Status in Gnome Virtual Terminal Emulator: Won't Fix Status in gnome-terminal package in Ubuntu: Opinion Status in vte2.91 package in Ubuntu: Opinion Bug description: I would find it rather useful, especially with certain types of outputs, if gnome-terminal would allow me to disable text wrapping, that is so that there would be a horizontal scroll bar that would allow me to see the rest of the text. I don't know if this should/would include the commands you type it, but maybe there could be a separate option for the wrapping of that. There are other Terminals which support this, and I think it would be really nice if gnome-terminal would too so that one doesn't have to put all of the output into another program like 'less' or similar in order to disable the wrapping. I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a very useful feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1609009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1605397] Re: gnome-terminal doesn't return to its original size when unsnapping from the side of the screen
I'm unable to reproduce on 17.10 with gnome-shell. -- 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/1605397 Title: gnome-terminal doesn't return to its original size when unsnapping from the side of the screen Status in gnome-terminal package in Ubuntu: New Bug description: If you snap a Terminal window to the side of the screen, and then drag it away with the mouse, it changes back to its original width, but its height remains as that of the screen, so that you end up with an unusually tall window. This happens if you drag it away, or click the, er, "maximize" button, but not if you unsnap it with Ctrl-Super-Left/Right. This is on an up-to-date version of Ubuntu 16.04 LTS. (A similar problem occurred on a fresh 16.04.0 install or LiveCD, where the window would retain the full screen dimensions on un- maximizing. That has been fixed now, but this one is still a problem.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 21 21:57:18 2016 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/1605397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725219] [NEW] /usr/bin/gnome-control-center:11:g_type_check_instance_cast:ext_ubuntu_dock_placement_changed_callback:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_vali
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.1-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/fb911c401b7ebdc71c10484ecc74c37345e34f97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- 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/1725219 Title: /usr/bin/gnome-control- center:11:g_type_check_instance_cast:ext_ubuntu_dock_placement_changed_callback:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.1-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/fb911c401b7ebdc71c10484ecc74c37345e34f97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725216] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1725216/+attachment/4978261/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725216/+attachment/4978263/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725216/+attachment/4978266/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725216/+attachment/4978267/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725216/+attachment/4978268/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725216/+attachment/4978269/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725216/+attachment/4978270/+files/ThreadStacktrace.txt ** 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"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725216 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: Had problems installing synaptic package manager, after reboot it worked fine . 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: Fri Oct 20 10:53:02 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.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/1725216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725163] Re: gnome-shell freezes when logout/shutdown
More strangeness. Open the users panel in control center with a webcam takes > 20 seconds. If I rmmod uvcvideo then it opens immediately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1725163 Title: gnome-shell freezes when logout/shutdown Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Problem: When I click on logout/shutdown option in gnome-shell topbar menu DE freezes for 25sec before providing correct overlay (logout/shutdown window) Gnome: 3.26 Ubuntu: 17.10 gnome-settings-daemon: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 part of log: Oct 20 09:35:42 MegaHulk systemd[2225]: Started GNOME Terminal Server. Oct 20 09:35:59 MegaHulk at-spi2-registr[11456]: Failed to send session response Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gsd-power[11521]: Failed to acquire idle monitor proxy: Timeout was reached Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client21' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client18' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client17' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' fail Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client16' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client22' fail Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client9' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client8' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client7' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client6' faile Oct 20 09:36:23 MegaHulk gnome-session[11389]: gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client3' faile Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client15' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client13' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client12' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client11' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client10' failed to reply before tim Oct 20 09:36:23 MegaHulk gnome-session-binary[11389]: WARNING: Client '/org/gnome/SessionManager/Client24' failed to reply
[Desktop-packages] [Bug 1637688] Re: Terminal and file manager scrolls inverted
Marius, thanks for this info! gnome-terminal relies on smooth scrolling events at least since vte-0.38 (which appeared in Vivid 15.04), see https://git.gnome.org/browse/vte/commit/?id=7efb04f. At this moment I'm puzzled what can go wrong on the reporter's computer. Carlos, can you reproduce the issue on Artful? (By the way, we have an even nastier bug at https://bugzilla.gnome.org/show_bug.cgi?id=774430 – any help resolving that would be highly appreciated!) ** Bug watch added: GNOME Bug Tracker #774430 https://bugzilla.gnome.org/show_bug.cgi?id=774430 -- 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/1637688 Title: Terminal and file manager scrolls inverted Status in gnome-terminal package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I'm having this issue, all other programs are scrolling as "Natural Scrolling", just like Mac does, however only Terminal and File browser have "Reversed Scrolling", they should be consistent across apps and programs, maybe it's nautilus the one that inverts the scrolling? Only could find this issue in Terminal and File Browser, attaching bug info from terminal. Release version: Description: Ubuntu 16.10 Release: 16.10 Terminal version: Not sure, it should be the latest one that comes with this Ubuntu version. Expected behavior: I expected to scroll in the same direction as all other apps in my OS. Current Behavior: I scrolled up with mouse wheel, with "Natural Scrolling" all apps scroll down, but terminal and file manager scrolls up, it is indeed inverted. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.20.2-1ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 22:04:54 2016 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2016-02-20 (251 days ago) InstallationMedia: SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-16 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Snapd side changes: https://github.com/snapcore/snapd/pull/4061 It looks like snapd-glib might need a change too, since it looks like this will still be mapped to SNAPD_ERROR_FAILED in parse_result() (I think falling back to treating 401 as SNAPD_AUTH_DATA_REQUIRED will do). -- 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/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix Status in snapd: New Status in gnome-software package in Ubuntu: Confirmed Bug description: When I open this application, I see a message near the top that says "Sorry, something went wrong cannot authenticate to snap store: Provided email/password is not correct." I can close this message dialog, but there appears to be no way to remedy the problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-software 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 13:08:16 2017 EcryptfsInUse: Yes InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
I've tried all solutions, nothing work for me... I can't disable my Intel GPU on bios (Motherboard: MSI Z270-A PRO). Maybe i need to downgrade to ubuntu 17.04 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725238] [NEW] Clicking snap:// urls doesn't work
Public bug reported: I am unable to trigger GNOME Software to install snaps. Steps to reproduce: 1. Visit http://snapcraft.io/zzt 2. Click green Install button 3. Browser is taken to snap://zzt Outcome:- "The address wasn't understood" error page in Firefox Expected outcome:- GNOME Software launches directly on the ZZT snap app page. Here's a video showing it:- https://www.youtube.com/watch?v=rOaGt8W2zrY ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 2350 F pulseaudio /dev/snd/controlC1: alan 2350 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:06:27 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-02 (78 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Confirmed ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1725238 Title: Clicking snap:// urls doesn't work Status in firefox package in Ubuntu: Confirmed Bug description: I am unable to trigger GNOME Software to install snaps. Steps to reproduce: 1. Visit http://snapcraft.io/zzt 2. Click green Install button 3. Browser is taken to snap://zzt Outcome:- "The address wasn't understood" error page in Firefox Expected outcome:- GNOME Software launches directly on the ZZT snap app page. Here's a video showing it:- https://www.youtube.com/watch?v=rOaGt8W2zrY ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 2350 F pulseaudio /dev/snd/controlC1: alan 2350 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:06:27 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-02 (78 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001B
[Desktop-packages] [Bug 1725236] [NEW] vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10
Public bug reported: I'm using a Dell XPS 9560 with a Geforce 1050. Back on 17.04 (libvulkan-dev-1.0.42.0, nvidia-375) I could run vulkaninfo and my own Vulkan applications without a problem but, after switching to 17.10 (libvulkan-dev-1.0.61.1, nvidia-384), running vulkaninfo now results in the error attached. In other words, I cannot run any Vulkan-based application anymore. I have tried using Vulkan's SDK 1.0.42.2 from LunarG's website without success. I have been tempted to try rolling back to nvidia-375 but not being so familiar with Linux, I am a bit worried that things might go wrong. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: nvidia vulkan ** Attachment added: "vulkaninfo error" https://bugs.launchpad.net/bugs/1725236/+attachment/4978405/+files/vulkaninfo-error.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1725236 Title: vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10 Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: I'm using a Dell XPS 9560 with a Geforce 1050. Back on 17.04 (libvulkan-dev-1.0.42.0, nvidia-375) I could run vulkaninfo and my own Vulkan applications without a problem but, after switching to 17.10 (libvulkan-dev-1.0.61.1, nvidia-384), running vulkaninfo now results in the error attached. In other words, I cannot run any Vulkan-based application anymore. I have tried using Vulkan's SDK 1.0.42.2 from LunarG's website without success. I have been tempted to try rolling back to nvidia-375 but not being so familiar with Linux, I am a bit worried that things might go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1725236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725234] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1714989 *** https://bugs.launchpad.net/bugs/1714989 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 #1714989, 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/1725234/+attachment/4978390/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725234/+attachment/4978392/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725234/+attachment/4978397/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725234/+attachment/4978398/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725234/+attachment/4978399/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725234/+attachment/4978400/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725234/+attachment/4978401/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714989 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1725234 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-shell package in Ubuntu: New Bug description: apport showed up after gnome shell restarted by itself ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 Uname: Linux 4.13.8-041308-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Fri Oct 20 12:49:47 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-10-02 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fd802fdfe0d : movzbl 0x16(%rax),%edx PC (0x7fd802fdfe0d) ok source "0x16(%rax)" (0x40016) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725238] Re: Clicking snap:// urls doesn't work
Olivier - could you have a look at this one? I've asked Chris C for some pointers and will let you know what I find out. ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1725238 Title: Clicking snap:// urls doesn't work Status in firefox package in Ubuntu: Confirmed Bug description: I am unable to trigger GNOME Software to install snaps. Steps to reproduce: 1. Visit http://snapcraft.io/zzt 2. Click green Install button 3. Browser is taken to snap://zzt Outcome:- "The address wasn't understood" error page in Firefox Expected outcome:- GNOME Software launches directly on the ZZT snap app page. Here's a video showing it:- https://www.youtube.com/watch?v=rOaGt8W2zrY ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 2350 F pulseaudio /dev/snd/controlC1: alan 2350 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:06:27 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-02 (78 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1725238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879199 ** Bug watch added: Debian Bug tracker #879199 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879199 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hunspell-en-us in Ubuntu. https://bugs.launchpad.net/bugs/1718869 Title: Migrate to hunspell-en-us in libreoffice-dictionaries Status in hunspell-en-us package in Ubuntu: New Status in libreoffice-dictionaries package in Ubuntu: New Status in hunspell-en-us package in Debian: New Status in libreoffice-dictionaries package in Debian: Won't Fix Bug description: libreoffice-dictionaries upstream ships hunspell-en-us, which is properly maintained and is newer than the one currently in Debian and Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in libreoffice-dictionaries. The other English variants (British, Australian and others) are already provided by libreoffice- dictionaries and are more up-to-date than the US variant. Debian bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159 Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff and en_US.dic but there is not a built package for them. https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/ See this README from the Libreoffice/dictionaries git, https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt It seems that this is now dead, https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hunspell-en-us 20070829-6ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 09:43:32 2017 InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: hunspell-en-us UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725251] [NEW] package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I ran sudo apt --fix-broken install because my fuse wasn't working and when Restarted i got these errors with cups ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cups-daemon 2.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: E [20/Oct/2017:11:49:33 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [20/Oct/2017:12:20:03 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-Gray..\' already exists W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-RGB..\' already exists E [20/Oct/2017:12:30:56 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Wed Oct 18 17:15:12 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-01-04 (1384 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lpstat: device for Canon-MP220-series: usb://Canon/MP220%20series?serial=B0CF72&interface=1 device for Dell-MFP-Laser-3115cn: usb://Dell/MFP%20Laser%203115cn?serial=0927165472&interface=1 device for HP-Officejet-6700: hp:/net/Officejet_6700?zc=HP10604B4F9713 MachineType: Dell Inc. Studio 1555 Papersize: a4 PpdFiles: Dell-MFP-Laser-3115cn: Generic PostScript Printer HP-Officejet-6700: HP Officejet 6700, hpcups 3.16.3 Canon-MP220-series: Canon MP220 series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: cups Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to zesty on 2017-08-09 (72 days ago) dmi.bios.date: 04/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0C234M dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/23/2009:svnDellInc.:pnStudio1555:pvrA06:rvnDellInc.:rn0C234M:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Studio 1555 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-08-14T15:22:10.720387 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1725251 Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I ran sudo apt --fix-broken install because my fuse wasn't working and when Restarted i got these errors with cups ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cups-daemon 2.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: E [20/Oct/2017:11:49:33 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [20/Oct/2017:12:20:03 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-Gray..\' already exists W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-RGB..\' already exists E [20/Oct/2017:12:30:56 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Wed Oct 18 17:15:12 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-01-04 (1384 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lpstat: device for Canon-MP220-series: usb://Canon/MP220%20series?serial=B0CF72&interface=
[Desktop-packages] [Bug 1725249] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a duplicate of bug 1713581 *** https://bugs.launchpad.net/bugs/1713581 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 #1713581, 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/1725249/+attachment/4978505/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725249/+attachment/4978507/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725249/+attachment/4978512/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725249/+attachment/4978513/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725249/+attachment/4978514/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725249/+attachment/4978515/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725249/+attachment/4978516/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1713581 ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1725249 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: New Bug description: I was trying to extract a file from an archive by dragging & dropping to Nautilus. 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 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:33:25 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-11-26 (693 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f1cdad4dcd7 : mov(%rdi),%rdx PC (0x7f1cdad4dcd7) ok source "(%rdi)" (0x0001) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725241] Re: totem crashed with SIGSEGV in cogl_pixel_buffer_new()
*** This bug is a duplicate of bug 1724255 *** https://bugs.launchpad.net/bugs/1724255 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 #1724255, 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/1725241/+attachment/4978430/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725241/+attachment/4978432/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725241/+attachment/4978438/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725241/+attachment/4978439/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725241/+attachment/4978440/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725241/+attachment/4978441/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725241/+attachment/4978442/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724255 ** 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/1725241 Title: totem crashed with SIGSEGV in cogl_pixel_buffer_new() Status in totem package in Ubuntu: New Bug description: $ totem movie.mkv (totem:19054): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. (totem:19054): Totem-WARNING **: gtk-clutter failed to initialise, expect problems from here on. (totem:19054): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. (totem:19054): Clutter-WARNING **: Missing Cogl context: was Clutter correctly initialized? Segmentation fault (core dumped) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:11:32 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-09-01 (413 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160111) ProcCmdline: /usr/bin/totem --gapplication-service SegvAnalysis: Segfault happened at: 0x7febc7858c60:testb $0x10,0xc0(%rsi) PC (0x7febc7858c60) ok source "$0x10" ok destination "0xc0(%rsi)" (0x00c0) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_pixel_buffer_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_bitmap_new_with_size () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_content_invalidate () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 Title: totem crashed with SIGSEGV in cogl_pixel_buffer_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1725241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725257] [NEW] do not search and not index files from dropbox ubuntu 17.10
Public bug reported: Gnome-Shell of ubuntu 17.10 do not search and not index files from Dropbox folders. Shell of ubuntu 17.10 only search files from all folders except files that are in dropbox folders, this files only can located in nautilus but not in shell. Please solve this bug to can search the files of diferentes clouds providers as dropbox in the shell, now do not search files in shell. Thanks. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: dropbox gnome-17.10 ** Summary changed: - do not search files from dropbox ubuntu 17.10 + do not search and not index files from dropbox ubuntu 17.10 ** Description changed: - Gnome-Shell of ubuntu 17.10 do not search files from Dropbox folders. - Shell of ubuntu 17.10 only search files from all folders except files - that are in dropbox folders, this files only can located in nautilus but - not in shell. Please solve this bug to can search the files of - diferentes clouds providers as dropbox in the shell, now do not search - files in shell. Thanks. + Gnome-Shell of ubuntu 17.10 do not search and not index files from + Dropbox folders. Shell of ubuntu 17.10 only search files from all + folders except files that are in dropbox folders, this files only can + located in nautilus but not in shell. Please solve this bug to can + search the files of diferentes clouds providers as dropbox in the shell, + now do not search files in shell. Thanks. -- 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/1725257 Title: do not search and not index files from dropbox ubuntu 17.10 Status in gnome-shell package in Ubuntu: New Bug description: Gnome-Shell of ubuntu 17.10 do not search and not index files from Dropbox folders. Shell of ubuntu 17.10 only search files from all folders except files that are in dropbox folders, this files only can located in nautilus but not in shell. Please solve this bug to can search the files of diferentes clouds providers as dropbox in the shell, now do not search files in shell. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713931] Re: Shell ignores all search results if not all metadata available
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/1713931 Title: Shell ignores all search results if not all metadata available Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using current artful, g-s 3.25.91 and snapd-glib 1.18, looking for "vlc" or "gimp" in the gnome-shell overview returns a "no result", after deleting the snapd plugin and restarting g-s it lists them fine bug #1713929 is about the fact that there are no snap listed, this bug about the fact that one plugin can/do block others from returning results To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1713931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725251] Re: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1725251 Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I ran sudo apt --fix-broken install because my fuse wasn't working and when Restarted i got these errors with cups ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cups-daemon 2.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: E [20/Oct/2017:11:49:33 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [20/Oct/2017:12:20:03 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-Gray..\' already exists W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-RGB..\' already exists E [20/Oct/2017:12:30:56 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Wed Oct 18 17:15:12 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-01-04 (1384 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lpstat: device for Canon-MP220-series: usb://Canon/MP220%20series?serial=B0CF72&interface=1 device for Dell-MFP-Laser-3115cn: usb://Dell/MFP%20Laser%203115cn?serial=0927165472&interface=1 device for HP-Officejet-6700: hp:/net/Officejet_6700?zc=HP10604B4F9713 MachineType: Dell Inc. Studio 1555 Papersize: a4 PpdFiles: Dell-MFP-Laser-3115cn: Generic PostScript Printer HP-Officejet-6700: HP Officejet 6700, hpcups 3.16.3 Canon-MP220-series: Canon MP220 series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: cups Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to zesty on 2017-08-09 (72 days ago) dmi.bios.date: 04/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0C234M dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/23/2009:svnDellInc.:pnStudio1555:pvrA06:rvnDellInc.:rn0C234M:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Studio 1555 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-08-14T15:22:10.720387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1725251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725116] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725116 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: Update to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 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 Date: Thu Oct 19 21:36:09 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2012-04-02 (2026 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725263] [NEW] screen freezing
Public bug reported: my screen is freezing after some minutes. I have no idea what the problem could be. This Problem does also exist at other BS like windows. So I guess this is a HW problem, but what hardware could cause this problem? Any idea? with kind regards, Gustav ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 20 13:58:37 2017 DistUpgraded: 2017-01-01 17:43:39,218 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] [1019:9a18] InstallationDate: Installed on 2016-06-22 (484 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MEDION D3F3-EM ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=3ec08b5b-6ced-472a-91eb-d3df3b1cfe0b ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-01-01 (291 days ago) dmi.bios.date: 06/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: D3EMW08.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D3F3-EM dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.106:bd06/09/2014:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr: dmi.product.name: D3F3-EM dmi.product.version: 1.0 dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Oct 20 15:57:27 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputDell Dell USB Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725263 Title: screen freezing Status in xorg package in Ubuntu: New Bug description: my screen is freezing after some minutes. I have no idea what the problem could be. This Problem does also exist at other BS like windows. So I guess this is a HW problem, but what hardware could cause this problem? Any idea? with kind regards, Gustav ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 20 13:58:37 2017 DistUpgraded: 2017-01-01 17:43:39,218 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] [1019:9a18] InstallationDate: Installed on 2016-06-22 (484 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MEDION D3F3-EM ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) LA
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in gnome-shell package in Ubuntu: Confirmed 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/ubuntu/+source/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 1725252] Re: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()
*** This bug is a duplicate of bug 1724699 *** https://bugs.launchpad.net/bugs/1724699 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 #1724699, 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/1725252/+attachment/4978536/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725252/+attachment/4978538/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725252/+attachment/4978543/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725252/+attachment/4978544/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725252/+attachment/4978545/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725252/+attachment/4978546/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725252/+attachment/4978547/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724699 ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1725252 Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet() Status in nautilus package in Ubuntu: New Bug description: I had done a search for files with the name SqMatrix. Saw them and then hit the esc key. Nautilus crashed 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 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 18:30:52 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2016-10-19 (366 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x55c03e877660 : mov0x18(%rdi),%rax PC (0x55c03e877660) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_file_get_search_fts_snippet () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet() UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688391] Re: Highlight of links in terminal is not very smart
** Summary changed: - Highlight of links in terminal is retarded + Highlight of links in terminal is not very smart -- 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/1688391 Title: Highlight of links in terminal is not very smart Status in gnome-terminal package in Ubuntu: New Bug description: Steps to reproduce: - In a terminal, type this command: ls /srv/www/example.com/htdocs - hit Enter - move the mouse cursor over "www" or over "example.com" Expected: - nothing should happen Observed: - The substring "www/example.com/htdocs" is underlined and right-clickable as if it was an URL, which it obviously isn't. It is questionable in the first place that you try to parse urls that don't start with a schema. But in any case, you need to fix your regular expression I guess. I see now that even wwwXexampleYcom gets recognized as an URL. Looks like somebody forgot to escape a "." in a regular expression. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 4 21:40:58 2017 InstallationDate: Installed on 2013-10-11 (1301 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2016-12-11 (143 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1688391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725262] Re: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset()
*** This bug is a duplicate of bug 1718477 *** https://bugs.launchpad.net/bugs/1718477 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 #1718477, 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/1725262/+attachment/4978618/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725262/+attachment/4978620/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725262/+attachment/4978623/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725262/+attachment/4978624/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725262/+attachment/4978625/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725262/+attachment/4978626/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725262/+attachment/4978627/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1718477 ** 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/1725262 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() Status in gnome-control-center package in Ubuntu: New Bug description: Just downloaded 17.10 and something went wrong shortly after first boot up. now appears normal. 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 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 20:55:33 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () 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_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_markup_parse_context_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() 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/1725262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Also affects: gnome-terminal via
https://bugzilla.gnome.org/show_bug.cgi?id=780622
Importance: Unknown
Status: Unknown
--
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/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in GNOME Terminal:
Unknown
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698987] Re: package cracklib-runtime 2.9.2-1build2 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1698987 Title: package cracklib-runtime 2.9.2-1build2 failed to install/upgrade: problemas com dependências - a deixar triggers por processar Status in cracklib2 package in Ubuntu: Confirmed Bug description: Im a adventurer in linux ProblemType: Package DistroRelease: Ubuntu 16.10 Package: cracklib-runtime 2.9.2-1build2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Mon Jun 19 22:26:54 2017 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2017-06-17 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.2.20 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-1build2 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1698987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
