[Desktop-packages] [Bug 1715582] Re: deja-dup fails to backup
today the update of deja-dup came in (35.6-0ubuntu1 -> 36.0-0ubuntu1) There is no directory /var/cache/samba which the application searches for. creating it, does not help -> Backup failed Operation not supported by backend $ deja-dup (org.gnome.DejaDup:5945): Gtk-WARNING **: Allocating size to AssistantBackup 0x55b7940d0d70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? ** (org.gnome.DejaDup:5945): WARNING **: BackendRemote.vala:83: Could not find enclosing mount ** (org.gnome.DejaDup:5945): WARNING **: BackendRemote.vala:83: Could not find enclosing mount starting deja-dup with sudo rights -> Backup failed volume doesn’t implement mount on the console deja-dup complains that it cannot find /var/cache/smb: $ sudo deja-dup ** (org.gnome.DejaDup:5846): CRITICAL **: string_contains: assertion 'self != NULL' failed (org.gnome.DejaDup:5846): Gtk-WARNING **: Allocating size to AssistantBackup 0x5609b7db2070 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? gpg: WARNING: unsafe ownership on homedir '/home/wolf/.gnupg' ** (org.gnome.DejaDup:5846): WARNING **: BackendRemote.vala:83: Containing mount for file /var/cache/smb:/s4 not found mounting the backup volume -> Backup failed volume doesn’t implement mount $ sudo deja-dup ** (org.gnome.DejaDup:5987): CRITICAL **: string_contains: assertion 'self != NULL' failed (org.gnome.DejaDup:5987): Gtk-WARNING **: Allocating size to AssistantBackup 0x55f188b7f450 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? gpg: WARNING: unsafe ownership on homedir '/home/wolf/.gnupg' ** (org.gnome.DejaDup:5987): WARNING **: BackendRemote.vala:83: Containing mount for file /var/cache/smb:/s4 not found creating /var/cache/smb -> Backup failed volume doesn’t implement mount $ sudo mkdir smb wolf@mbpr13b:/var/cache$ sudo deja-dup ** (org.gnome.DejaDup:6045): CRITICAL **: string_contains: assertion 'self != NULL' failed (org.gnome.DejaDup:6045): Gtk-WARNING **: Allocating size to AssistantBackup 0x558b0333f3a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? gpg: WARNING: unsafe ownership on homedir '/home/wolf/.gnupg' ** (org.gnome.DejaDup:6045): WARNING **: BackendRemote.vala:83: Containing mount for file /var/cache/smb:/s4 not found Even giving o+w does not help This can be tested on a plain 17.10 installation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1715582 Title: deja-dup fails to backup Status in deja-dup package in Ubuntu: Fix Committed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
Just to clarify, I've only tested 16.04 on armhf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" Status in chromium-browser package in Ubuntu: Confirmed Bug description: crashes on startup with [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process Segmentation fault System ODROID XU3 armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716601] [NEW] video decoders don't work correctly
Public bug reported: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716600] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1714745 *** https://bugs.launchpad.net/bugs/1714745 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 #1714745, 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/1716600/+attachment/4948542/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716600/+attachment/4948544/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716600/+attachment/4948548/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716600/+attachment/4948549/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716600/+attachment/4948550/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716600/+attachment/4948551/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716600/+attachment/4948552/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714745 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() ** 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/1716600 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-shell package in Ubuntu: New Bug description: Crashed shortly after receiving a notification from Nextcloud. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Sep 12 09:52:18 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-02 (162 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/usr/bin/zsh SegvAnalysis: Segfault happened at: 0x7f19fa20ae26 : mov(%rdi),%rdi PC (0x7f19fa20ae26) ok source "(%rdi)" (0x00c00ba6) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-08-10 (32 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716602] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1716602 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: I Don't know :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Sep 11 15:50:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1716602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716602] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I Don't know :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Sep 11 15:50:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1716602 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: I Don't know :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Sep 11 15:50:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1716602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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)
As of the latest updates to gdm3, I still can't boot with my laptop when it's in discrete mode (nvidia graphics only). Does not get to the greeter. syslog is full of countless repetitions of "Stopping NVIDIA persistence Daemon". CPU must be high because the fan comes on. I've reported this but it's going to be better if someone who knows what they are doing can reproduce it. (In hybrid mode, it boots, but no external displays are detected, which implies that nvidia isn't working properly) I have the latest 375 Nvidia driver. nvidia Modesetting is enabled. Still works fine with lightdm as the display manager. -- 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 1697646] Re: Long-running ping command leads to 100% CPU usage
Probably related: https://github.com/iputils/iputils/issues/85 ** Bug watch added: github.com/iputils/iputils/issues #85 https://github.com/iputils/iputils/issues/85 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1697646 Title: Long-running ping command leads to 100% CPU usage Status in iputils package in Ubuntu: Confirmed Bug description: Since I've updated my laptop to Ubuntu MATE 17.04, I notice ping sometimes gets into a runaway mode. I'm on a shaky Wi-Fi so to monitor connectivity I usually have a long running ping command against google's DNS server: > ping -s16 8.8.4.4 Often, after leaving it for a while, I notice screaming vents and htop then shows the ping process consuming 100% of one CPU. It will stay like that until ping is killed. I'm not sure how to troubleshoot this issue, can someone recommend a protocol? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: iputils-ping 3:20161105-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Tue Jun 13 11:11:26 2017 InstallationDate: Installed on 2017-04-05 (69 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1) SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1697646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716633] [NEW] /usr/bin/gnome-software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular
Public bug reported: Potentially a regression introduced by gnome-software 3.20.5-0ubuntu0.16.04.6 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.22.7-0ubuntu3.17.04.7, the problem page at https://errors.ubuntu.com/problem/b8d914cec850474446873c5a60feba99b1d498d9 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-software (Ubuntu) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Confirmed ** Tags: xenial zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1716633 Title: /usr/bin/gnome- software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular Status in gnome-software package in Ubuntu: Confirmed Bug description: Potentially a regression introduced by gnome-software 3.20.5-0ubuntu0.16.04.6 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.22.7-0ubuntu3.17.04.7, the problem page at https://errors.ubuntu.com/problem/b8d914cec850474446873c5a60feba99b1d498d9 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-software/+bug/1716633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716633] Re: /usr/bin/gnome-software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular
** Description changed: + Potentially a regression introduced by gnome-software + 3.20.5-0ubuntu0.16.04.6 + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.22.7-0ubuntu3.17.04.7, the problem page at https://errors.ubuntu.com/problem/b8d914cec850474446873c5a60feba99b1d498d9 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/. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1716633 Title: /usr/bin/gnome- software:11:g_str_equal:g_hash_table_lookup_node:g_hash_table_insert_internal:find_snaps:gs_plugin_add_popular Status in gnome-software package in Ubuntu: Confirmed Bug description: Potentially a regression introduced by gnome-software 3.20.5-0ubuntu0.16.04.6 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.22.7-0ubuntu3.17.04.7, the problem page at https://errors.ubuntu.com/problem/b8d914cec850474446873c5a60feba99b1d498d9 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-software/+bug/1716633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb
According to errors.u.c there is no occurrence of this crash for gnome- software 3.20.5-0ubuntu0.16.04.6 in xenial-proposed. https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=gnome- software&period=month&version=3.20.5-0ubuntu0.16.04.6 However, this version introduced a new crash which may potentially be a regression (https://errors.ubuntu.com/problem/b8d914cec850474446873c5a60feba99b1d498d9 and bug 1716633) Marking as verification-failed until it is investigated by the maintainer of the package. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1708140 Title: /usr/bin/gnome- software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Released Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection and testing of this code doesn't show any reason why this code path can occur. [Test Case] 1. Check errors.ubuntu.com for crash reports in the icon cache code Expected result: Errors do not occur. Observed result: Errors occur. [Regression Potential] Some risk of introducing new bugs in the icon handling code. The code is similar to what has been released into Artful, but needed to be modified to work with the older version of gnome-software in Xenial (the Zesty change is the same as Artful). [1] https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1708140/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 123997] Re: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal]
*** This bug is a duplicate of bug 89090 *** https://bugs.launchpad.net/bugs/89090 ** Attachment removed: "D25D12DE3B20BAAF0393B3A85CDA932A.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123997/+attachment/4884798/+files/D25D12DE3B20BAAF0393B3A85CDA932A.jpg ** Attachment removed: "B26F3B4D8141253B87F1F011CE8AFEA2.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123997/+attachment/4904303/+files/B26F3B4D8141253B87F1F011CE8AFEA2.jpg ** Attachment removed: "C36FBB9FB243833C.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123997/+attachment/4927278/+files/C36FBB9FB243833C.jpg ** Attachment removed: "2D5A2F764C6835E5.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123997/+attachment/4925310/+files/2D5A2F764C6835E5.jpg -- 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/123997 Title: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal] Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox ... Firefox crashed following a link It happend again! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 120971] Re: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal]
*** This bug is a duplicate of bug 89090 *** https://bugs.launchpad.net/bugs/89090 ** Attachment removed: "BCBE9E4CC2241B08.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120971/+attachment/4927281/+files/BCBE9E4CC2241B08.jpg ** Attachment removed: "BA433C8841D484D7.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120971/+attachment/4925286/+files/BA433C8841D484D7.jpg ** Attachment removed: "EA2D554865A5363F14A09F39B913E6C9.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120971/+attachment/4904308/+files/EA2D554865A5363F14A09F39B913E6C9.jpg ** Attachment removed: "9F49CDBC610D33032E48398BCC142754.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120971/+attachment/4885243/+files/9F49CDBC610D33032E48398BCC142754.jpg ** Attachment removed: "BCCE224F2739715C1F71741A769C3838.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120971/+attachment/4884804/+files/BCCE224F2739715C1F71741A769C3838.jpg -- 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/120971 Title: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal] Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox ... Crash during firefox use Following a link firefox crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 123795] Re: [FEISTY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal]
*** This bug is a duplicate of bug 89090 *** https://bugs.launchpad.net/bugs/89090 ** Attachment removed: "C2D69301BC2189A243046014DE43DC71.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123795/+attachment/4884799/+files/C2D69301BC2189A243046014DE43DC71.jpg ** Attachment removed: "CCE0D3E9738DCD088A27BA1BD7474532.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123795/+attachment/4885242/+files/CCE0D3E9738DCD088A27BA1BD7474532.jpg ** Attachment removed: "AF547353706AE899.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123795/+attachment/4925291/+files/AF547353706AE899.jpg ** Attachment removed: "FE03B4D1573C2B2F.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123795/+attachment/4927282/+files/FE03B4D1573C2B2F.jpg ** Attachment removed: "D577A38A569A7B78.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123795/+attachment/4928831/+files/D577A38A569A7B78.jpg -- 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/123795 Title: [FEISTY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal] Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox ... firefox crashed ... Firefox crashes when clicking image link When I go to the page http://hd.se/inrikes/2007/07/03/algblomning-paa-gaang-i/ and very quickly press several times on the image which also is a link, firefox crashes. No information popup of any kind, it just disappears. I have Firefox/2.0.0.4 (Ubuntu-feisty) + flashplugin-nonfree 9.0.31.0.2ubuntu1 + mplayerplug-in-xx. Is it possible for me to get some kind of crash dump? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 120548] Re: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal]
*** This bug is a duplicate of bug 89090 *** https://bugs.launchpad.net/bugs/89090 ** Attachment removed: "C67D75E8BF639B8EBD44ED2D4AE3DBE6.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120548/+attachment/4885238/+files/C67D75E8BF639B8EBD44ED2D4AE3DBE6.jpg ** Attachment removed: "6D919512174A0509DB04302E6DA99DE9.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120548/+attachment/4904309/+files/6D919512174A0509DB04302E6DA99DE9.jpg ** Attachment removed: "09D102F0EDE56A0C.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120548/+attachment/4925282/+files/09D102F0EDE56A0C.jpg ** Attachment removed: "EA38457EEC7D039A.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120548/+attachment/4927280/+files/EA38457EEC7D039A.jpg ** Attachment removed: "C20B398C4C2E28CF.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120548/+attachment/4946853/+files/C20B398C4C2E28CF.jpg -- 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/120548 Title: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal] Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox ... Crash durign firefox use Firefox crashed when following a link with a pop-up launched by javascritp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/120548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 121290] Re: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal]
*** This bug is a duplicate of bug 89090 *** https://bugs.launchpad.net/bugs/89090 ** Attachment removed: "8BDBE660E7162B49560C18A931F3D0DE.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+attachment/4884801/+files/8BDBE660E7162B49560C18A931F3D0DE.jpg ** Attachment removed: "929CC3E4AB2A315F8338A980FF37EA2B.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+attachment/4885241/+files/929CC3E4AB2A315F8338A980FF37EA2B.jpg ** Attachment removed: "C778D5764AEB8F55F95AB76D2535A290.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+attachment/4904307/+files/C778D5764AEB8F55F95AB76D2535A290.jpg ** Attachment removed: "433BB235B5415578.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+attachment/4925287/+files/433BB235B5415578.jpg ** Attachment removed: "2C5571D3DF276313.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+attachment/4927277/+files/2C5571D3DF276313.jpg ** Attachment removed: "E5ADEA195D66C897.jpg" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+attachment/4946854/+files/E5ADEA195D66C897.jpg -- 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/121290 Title: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal] Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox ... Firefow Crash Firefox crashed when opening a pop up cuncurrently following a link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1008539] Re: Wrong volume binding when connecting bluetooth speakers
This is a very useful information for the users. Please providing me more information related to this particular topic. https://bluetoothgears.com/";> https://bluetoothgears.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1008539 Title: Wrong volume binding when connecting bluetooth speakers Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a 2.1 speaker system and a Logitech bluetooth adapter for them that connects to my Asus UL50AG notebook for sound. In Sound Settings, I then have 2 entries: Built-in Audio Card and Logitech Adapter. The problem is that when I connect/reconnect to the bluetooth adapter, the sound volume knob is not bound to the Logitech Adapter. Instead, in Sound Settings, the Built-in Audio Card is selected instead of the Logitech Adapter. And when I use the multimedia keys on my notebook (Volume Up, Down, Mute), they have effect on the sound coming out of the notebook, not the external speakers. The expected result would be that, when I connect/reconnect the bluetooth adapter, the volume multimedia keys should bound to the new bluetooth setup, not the internal audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1008539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716639] [NEW] gnome-screensaver issue when using Wayland
Public bug reported: When using a Wayland session instead of X11 from the standard lightdm- gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+ initialisation, causing the gnome-session-binary to exit and subsequently a greeter loop where a user is unable to log in. The following is an excerpt from the syslog: ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service name='org.gnome.ScreenSaver' Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init server: Could not connect: Connection refused Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+ S Running an identical session without Wayland produces the expected behaviour: a user can log into his desktop session and start working as usual. Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share /gnome-session/sessions/gnome.session doesn't have any effect. I'm suspecting foul play between the screensaver proxy and the screensaver binary itself, but don't have the bandwidth to analyse the source at the moment. More than happy to provide more information as required - just let me know. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-screensaver 3.6.1-7ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 11:29:30 2017 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2017-08-31 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1716639 Title: gnome-screensaver issue when using Wayland Status in gnome-screensaver package in Ubuntu: New Bug description: When using a Wayland session instead of X11 from the standard lightdm- gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+ initialisation, causing the gnome-session-binary to exit and subsequently a greeter loop where a user is unable to log in. The following is an excerpt from the syslog: ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service name='org.gnome.ScreenSaver' Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init server: Could not connect: Connection refused Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+ S Running an identical session without Wayland produces the expected behaviour: a user can log into his desktop session and start working as usual. Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share /gnome-session/sessions/gnome.session doesn't have any effect. I'm suspecting foul play between the screensaver proxy and the screensaver binary itself, but don't have the bandwidth to analyse the source at the moment. More than happy to provide more information as required - just let me know. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-screensaver 3.6.1-7ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 11:29:30 2017 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2017-08-31 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716579] Re: gnome-software uses a very high cpu amount
It's not really useful assigning the bug to Robert without knowing what went wrong, because there's no information to go on for fixing it. HOWEVER! As it happens this just happened on my laptop, and I have a backtrace. It looks like our old friend GMainContext. Hopefully this is enough to go on. ** Attachment added: "1716579-bt.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716579/+attachment/4948607/+files/1716579-bt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1716579 Title: gnome-software uses a very high cpu amount Status in gnome-software package in Ubuntu: Confirmed Bug description: The room was silent, when the fan of my laptop suddenly started making noise. I checked it and it was because of the intense amount of CPU in use because of gnome software. Gnome Software CPU use was over 60%. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 08:29:01 2017 InstallationDate: Installed on 2017-08-21 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override
This bug was fixed in the package glib2.0 - 2.53.6-1ubuntu2
---
glib2.0 (2.53.6-1ubuntu2) artful; urgency=medium
* exp_git_default_per_desktop3.patch:
- refresh patch from Alberts Muktupāvels to fix double free issue
(LP: #1713391)
-- Didier Roche Thu, 31 Aug 2017 18:30:00 +0200
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1713391
Title:
glib-compile-schemas invalid free in per session override
Status in glib2.0 package in Ubuntu:
Fix Released
Bug description:
reinstall nautilus error with package sogoupinyin
# sudo nautilus
sys:1: PyGIWarning: Nautilus was imported without specifying a version
first. Use gi.require_version('Nautilus', '3.0') before import to
ensure that the right version gets loaded.
** Message: Init Stock Icons
(nautilus:10235): GLib-GIO-ERROR **: Settings schema
'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'
#sudo apt-get install --reinstall nautilus nautilus-share nautilus-data
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
需要下载 0 B/3,298 kB 的归档。
解压缩后会消耗 0 B 的额外空间。
您希望继续执行吗？ [Y/n] y
(正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb ...
正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb ...
正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb ...
正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb ...
正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb ...
正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb ...
正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb ...
正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
*** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double
free or corruption (fasttop): 0x58242808 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
/lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
/lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
=== Memory map:
5659b000-565a5000 r-xp 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a6000-565a7000 r--p a000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a7000-565a8000 rw-p b000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
58113000-5829 rw-p 00:00 0
[heap]
f6e0-f6e21000 rw-p 00:00 0
f6e21000-f6f0 ---p 00:00 0
f6f75000-f712b000 r--p 002da000 08:01 25170585
/usr/lib/locale/locale-archive
f712b000-f732b000 r--p 08:01 25170585
/usr/lib/locale/locale-archive
f732b000-f732d000 rw-p 00:00 0
f732d000-f7346000 r-xp 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7346000-f7347000 r--p 00018000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7347000-f7348000 rw-p 00019000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7348000-f734a000 rw-p 00:00 0
f734a000-f73c1000 r-xp 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c1000-f73c2000 r--p 00076000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c2000-f73c3000 rw-p 00077000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c3000-f7576000 r-xp 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7576000-f7577000 ---p 001b3000 08:01 5085
[Desktop-packages] [Bug 1716579] Re: gnome-software uses a very high cpu amount
** Tags added: rls-aa-incoming -- 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/1716579 Title: gnome-software uses a very high cpu amount Status in gnome-software package in Ubuntu: Confirmed Bug description: The room was silent, when the fan of my laptop suddenly started making noise. I checked it and it was because of the intense amount of CPU in use because of gnome software. Gnome Software CPU use was over 60%. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 08:29:01 2017 InstallationDate: Installed on 2017-08-21 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716639] Re: gnome-screensaver issue when using Wayland
Using gdm instead of lightdm produces a similar issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1716639 Title: gnome-screensaver issue when using Wayland Status in gnome-screensaver package in Ubuntu: New Bug description: When using a Wayland session instead of X11 from the standard lightdm- gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+ initialisation, causing the gnome-session-binary to exit and subsequently a greeter loop where a user is unable to log in. The following is an excerpt from the syslog: ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service name='org.gnome.ScreenSaver' Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init server: Could not connect: Connection refused Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+ S Running an identical session without Wayland produces the expected behaviour: a user can log into his desktop session and start working as usual. Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share /gnome-session/sessions/gnome.session doesn't have any effect. I'm suspecting foul play between the screensaver proxy and the screensaver binary itself, but don't have the bandwidth to analyse the source at the moment. More than happy to provide more information as required - just let me know. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-screensaver 3.6.1-7ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 11:29:30 2017 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2017-08-31 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002985] Re: [Upstream] Saving to .doc decouples endnote number from text
** Changed in: df-libreoffice Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1002985 Title: [Upstream] Saving to .doc decouples endnote number from text Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.3-0ubuntu1 Candidate: 1:3.5.3-0ubuntu1 Version table: *** 1:3.5.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 3) What is expected to happen in Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1002985/+attachment/3158838/+files/example.odt && lowriter --nologo example.odt save the attached document in .doc format (97/2000/XP/2003), close, reopen and the endnote looks the same as it did in .odt. 4) What happens instead is the the endnote number is decoupled from the endnote text. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 22 11:57:38 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111222) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1002985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716643] Re: gnome-shell crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1714330 *** https://bugs.launchpad.net/bugs/1714330 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 #1714330, 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/1716643/+attachment/4948627/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716643/+attachment/4948629/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716643/+attachment/4948632/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716643/+attachment/4948633/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716643/+attachment/4948634/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716643/+attachment/4948635/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716643/+attachment/4948636/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714330 gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() ** 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/1716643 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() Status in gnome-shell package in Ubuntu: New Bug description: I am not sure, this comes up every time the system restarts on login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Sep 12 09:26:37 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-05-16 (849 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f512bc39836:mov0x1a0(%rax),%rax PC (0x7f512bc39836) ok source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2 meta_monitor_manager_kms_wait_for_flip () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to artful on 2017-08-29 (14 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Example audio created with "arecord -f cd". >From participants on various chat programs, the distortion is worse than it sounds here, so I'm trying to figure out if I can get a second test recorded via pulseaudio and not ALSA directly (I understand that is what arecord does). ** Attachment added: "created_with_arecord_dash_f_cd.wav" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+attachment/4948650/+files/created_with_arecord_dash_f_cd.wav -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716654] [NEW] [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Public bug reported: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+
[Desktop-packages] [Bug 1712571] Re: xwayland does not support wacom tablets
The implementation looks promising but still seems incomplete. For instance, Xournal still works much better in a real X11 session than under XWayland. In the latter setting, the cursor does not display as the stylus hovers over the tablet so it's not possible to see where one is drawing until one actually applies pressure and and starts inking. -- 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/1712571 Title: xwayland does not support wacom tablets Status in xorg-server package in Ubuntu: Fix Released Bug description: When running a session under Wayland, my Wacom tablet does not work properly in applications using xwayland (the cursor moves, but clicking does not work). This is a known issue that apparently has been fixed in xorg-server 1.20 branch - see the upstream bug at https://bugs.freedesktop.org/show_bug.cgi?id=99411 and also https://bugzilla.redhat.com/show_bug.cgi?id=1397898. Is xorg-server 1.20 likely to be released in time for Artful or can the wacom patches be backported for xwayland? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.3-1ubuntu3 Uname: Linux 4.13.0-041300rc6-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 20:59:41 2017 DistUpgraded: 2017-08-17 08:53:31,141 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.12.0-11-generic, x86_64: installed bbswitch, 0.8, 4.13.0-041300rc6-generic, x86_64: installed nvidia-384, 384.59, 4.12.0-11-generic, x86_64: installed nvidia-384, 384.59, 4.13.0-041300rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-08-16 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-041300rc6-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7 Renderer: Software SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-08-17 (6 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 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.3.4:bd06/08/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.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Aug 17 08:57:12 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1712571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699731] [NEW] Icons appear corrupted when dragged on the Desktop or in Nautilus
You have been subscribed to a public bug: After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop or from a Nautilus window now looks quite strange. In both cases the image under cursor, which represents the icon being dragged, has no transparency and includes a piece of the background, on which the original icon is located, and the dragged icon itself appears to be somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue. When searching for the solution for this issue, I found the following question on askubuntu, which seems to describe the same problem: https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus- when-dragging-icons . Unfortunately, the question is unanswered and there are no mentions of a bug report, so I decided to go ahead and submit one myself. I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia driver v.375.66 is installed. The problem reproduces regardless of which graphics card is selected via nvidia-prime. Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) Subsystem: Dell Haswell-ULT Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 -- 08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) Subsystem: Dell GeForce 820M Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375 ** Affects: ayatana-design Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: drag nautilus unity -- Icons appear corrupted when dragged on the Desktop or in Nautilus https://bugs.launchpad.net/bugs/1699731 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699731] Re: Icons appear corrupted when dragged on the Desktop or in Nautilus
Thanks for helping making Ubuntu better! In the future, please use "ubuntu-bug package-name" to file Ubuntu bugs. https://help.ubuntu.com/community/ReportingBugs#How_to_report_bugs ** Package changed: ubuntu => nautilus (Ubuntu) -- 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/1699731 Title: Icons appear corrupted when dragged on the Desktop or in Nautilus Status in Ayatana Design: New Status in nautilus package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop or from a Nautilus window now looks quite strange. In both cases the image under cursor, which represents the icon being dragged, has no transparency and includes a piece of the background, on which the original icon is located, and the dragged icon itself appears to be somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue. When searching for the solution for this issue, I found the following question on askubuntu, which seems to describe the same problem: https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus- when-dragging-icons . Unfortunately, the question is unanswered and there are no mentions of a bug report, so I decided to go ahead and submit one myself. I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia driver v.375.66 is installed. The problem reproduces regardless of which graphics card is selected via nvidia-prime. Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) Subsystem: Dell Haswell-ULT Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 -- 08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) Subsystem: Dell GeForce 820M Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1699731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715601] Re: ubiquity-dm / install ubuntu - Network and VPN settings are missing
** Tags added: rls-aa-incoming -- 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/1715601 Title: ubiquity-dm / install ubuntu - Network and VPN settings are missing Status in gnome-shell package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: Ubuntu Artful Desktop 20170907 In ubiquity-dm and 'Install Ubuntu' in the top right menu, the network settings menu is missing and clicking on the VPN entry does nothing (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.6 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 11:49:01 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170907) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704618] Re: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()
** Tags added: rls-aa-incoming -- 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/1704618 Title: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Test Case: 1. Open the 'Users' panel in gnome-control-center 2. Select a user then click on 'Unlock' (top right button in the title bar) Expected result The panel is unlocked Actual Result This crash. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 16 10:09:12 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-06-26 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7ff4ea6fe6e9:cmpq $0x0,0x58(%rax) PC (0x7ff4ea6fe6e9) ok source "$0x0" ok destination "0x58(%rax)" (0x0058) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64() 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/1704618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)
** Tags added: rls-aa-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1705157 Title: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg) Status in gnome-session: Confirmed Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Invalid Bug description: Test case: Do a fresh install of current image (july 19 here Boot up, check selected session at the greeter - it will say "ubuntu" Log in, ck. env., it will actually be ubuntu-wayland Ex. $ env | grep -i wayland DESKTOP_SESSION=ubuntu-wayland WAYLAND_DISPLAY=wayland-0 XDG_SESSION_TYPE=wayland XDG_SESSION_DESKTOP=ubuntu-wayland GDMSESSION=ubuntu-wayland Test 2: From above log out, switch session in greeter to wayland on ubuntu,, switch back to ubuntu, login. Now you'll be in an ubuntu session Test 3: log out from above ubuntu session, log into ubuntu-wayland session, reboot. At greeter notice it says "ubuntu" selected. Login, ck. session. You'll actually be in an ubuntu-wayland session ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 21:48:10 2017 InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1705157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713912] Re: Cannot authenticate to the snap store - Fails with dbus error: Message recipient disconnected from message bus without replying
** Tags added: rls-aa-incoming -- 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/1713912 Title: Cannot authenticate to the snap store - Fails with dbus error: Message recipient disconnected from message bus without replying Status in gnome-software package in Ubuntu: Confirmed Bug description: Test Case: 1. On a fresh installation start gnome-software 2. Install a snap 3. Enter your credentials when asked and proceed with the authentication Expected result Authentication is successful and the user can install the desired snap package. Actual result dbus error: Message recipient disconnected from message bus without replying From the journal: août 30 08:01:57 ubuntu gnome-software[1385]: can't reliably fixup error from domain g-dbus-error-quark août 30 08:01:57 ubuntu gnome-software[1385]: failed to authenticate: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 07:54:25 2017 InstallationDate: Installed on 2017-08-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1713912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712571] Re: xwayland does not support wacom tablets
file a new bug then, and bonus points for filing one upstream too -- 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/1712571 Title: xwayland does not support wacom tablets Status in xorg-server package in Ubuntu: Fix Released Bug description: When running a session under Wayland, my Wacom tablet does not work properly in applications using xwayland (the cursor moves, but clicking does not work). This is a known issue that apparently has been fixed in xorg-server 1.20 branch - see the upstream bug at https://bugs.freedesktop.org/show_bug.cgi?id=99411 and also https://bugzilla.redhat.com/show_bug.cgi?id=1397898. Is xorg-server 1.20 likely to be released in time for Artful or can the wacom patches be backported for xwayland? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.3-1ubuntu3 Uname: Linux 4.13.0-041300rc6-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 20:59:41 2017 DistUpgraded: 2017-08-17 08:53:31,141 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.12.0-11-generic, x86_64: installed bbswitch, 0.8, 4.13.0-041300rc6-generic, x86_64: installed nvidia-384, 384.59, 4.12.0-11-generic, x86_64: installed nvidia-384, 384.59, 4.13.0-041300rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-08-16 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-041300rc6-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7 Renderer: Software SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-08-17 (6 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 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.3.4:bd06/08/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.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Aug 17 08:57:12 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1712571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)
No. I suck. It's because we free the GSequence, but the string is referenced in self->priv->fallback_session_name. strdup it when it goes in there. Then we have DESKTOP_SESSION=ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1705157 Title: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg) Status in gnome-session: Confirmed Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Invalid Bug description: Test case: Do a fresh install of current image (july 19 here Boot up, check selected session at the greeter - it will say "ubuntu" Log in, ck. env., it will actually be ubuntu-wayland Ex. $ env | grep -i wayland DESKTOP_SESSION=ubuntu-wayland WAYLAND_DISPLAY=wayland-0 XDG_SESSION_TYPE=wayland XDG_SESSION_DESKTOP=ubuntu-wayland GDMSESSION=ubuntu-wayland Test 2: From above log out, switch session in greeter to wayland on ubuntu,, switch back to ubuntu, login. Now you'll be in an ubuntu session Test 3: log out from above ubuntu session, log into ubuntu-wayland session, reboot. At greeter notice it says "ubuntu" selected. Login, ck. session. You'll actually be in an ubuntu-wayland session ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 21:48:10 2017 InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1705157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715717] Re: Cheese does not use built-in webcam
This is due to missing facetimehd driver. I built one according to https://github.com/patjak/bcwc_pcie/wiki/Get-Started and it works. However, the image lacks the green channel (thus it is magenta). Taking pictures works fine (all color channels are captured) ** Changed in: cheese (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1715717 Title: Cheese does not use built-in webcam Status in cheese package in Ubuntu: Invalid Bug description: In Ubuntu 17.10 beta, Cheese does not provide an image from the camera nor does it offer to attach to it in the prefs settings. Machine: Macbook Pro Retina 13" with a Facetime HD (Broadcom 1570) PCIe camera. Hardware works under macOS -> Seems software or driver issue. On a similar Macbook the image comes up immediately (with a Facetime HD camera attached to USB) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: cheese 3.25.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 20:12:57 2017 InstallationDate: Installed on 2017-09-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 RelatedPackageVersions: cheese3.25.90-0ubuntu1 cheese-common 3.25.90-0ubuntu1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1715717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1583182] Re: error on 01ifupdown script
The first error message I'm getting is ``` Sep 12 14:28:41 foobar nm-dispatcher[27267]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " ``` (Followed by the error messages in the original post.) -- 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/1583182 Title: error on 01ifupdown script Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: When bring the interface up or down I see this message on the logs May 18 10:03:36 count0 nm-dispatcher[8608]: req:1 'up' [enp2s0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. May 18 10:03:36 count0 NetworkManager[791]: [1463576616.8466] dispatcher: (29) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Tracing the problem I see that the call to /usr/sbin/fanctl is done with incorrect parameters. If I execute /etc/NetworkManager/dispatcher.d/01ifupdown enp2s0 down I get this error run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 1 ubuntu-fan is doing the call in following way /usr/sbin/fanctl net "$MODE" "$IFACE" and the parameters passed by ubuntu-fan are $MODE=stop $IFACE=enp2s0 but fanctl expect other parameters as showed on the script's header -- details lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.1.93-0ubuntu4 Version table: *** 1.1.93-0ubuntu4 500 500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 18 10:50:24 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-76f79dfb13e0 proto kernel scope link src 172.18.0.1 linkdown 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.8 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH br-76f79dfb13e0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 br-76f79dfb13e0 0a9f5c9b-cd67-4fb8-a72d-1811ca6fbb68 /org/freedesktop/NetworkManager/ActiveConnection/1 docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 e5f99f7d-532f-4c52-8749-c78afa9271dd /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 ee3ec6ee-7242-4956-9d19-20ccb19c5fe5 /org/freedesktop/NetworkManager/ActiveConnection/8 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1583182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716601] Re: video decoders don't work correctly
This issue occurs as well if cheese is started. (the camera had to be installed first via https://github.com/patjak/bcwc_pcie/wiki/Get-Started - refer to bug #1715717). The image is tinted magenta (the green channel is not captured). However taking a still works fine (all channels are captured giving correct imaging). Thus I presume the issue has something to do with video en- and decoding. (I tried the camera under macOS and it works fine). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716556] Re: Bug from day one
there is nothing alarming in the logs, reopen when you can describe what's wrong ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers (Ubuntu) ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Invalid -- 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/1716556 Title: Bug from day one Status in nvidia-graphics-drivers package in Ubuntu: Invalid Bug description: not much to say. feel free to ask for info as nec. PC-SUmmery: HP-Z800 with dual Xeon -=- 96Ram Boot SSD - Samsung evo 256 HD2 - SSD - Samsung evo 512 HD3-6 - WD Black 6tb each ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.82 Wed Jul 19 21:16:49 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 11 23:15:51 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-33-generic, x86_64: installed bbswitch, 0.8, 4.8.0-36-generic, x86_64: installed nvidia-375, 375.82, 4.10.0-33-generic, x86_64: installed nvidia-375, 375.82, 4.4.0-93-generic, x86_64: installed nvidia-375, 375.82, 4.8.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:85d4] InstallationDate: Installed on 2017-08-30 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Z800 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=3e736d4b-16c5-4b55-9918-6d85e4464703 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G5 v03.10 dmi.board.asset.tag: 2UA0250433 dmi.board.name: 0AECh dmi.board.vendor: Hewlett-Packard dmi.board.version: D dmi.chassis.asset.tag: 2UA0250433 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G5v03.10:bd07/09/2010:svnHewlett-Packard:pnHPZ800Workstation:pvr:rvnHewlett-Packard:rn0AECh:rvrD:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z800 Workstation dmi.sys.vendor: Hewlett-Packard 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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 11 22:40:42 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1716556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716674] [NEW] virtualbox crush guest or freeze host screen
Public bug reported: Virtualbox: 5.1.26 (ubuntu package) + VirtualBox 5.1.26 Oracle VM VirtualBox Extension Pack Host: ubuntu 17.10 (default gnomelibgnome-desktop-3-12 3.25.91.1-0ubuntu2) 4.12.0-12-generic AMD Ryzen5 1600 Guest: ubuntu 16.04 + guest addition The application window of the running guest will crash. Or the host OS screen is not updated. (The mouse pointer responds.) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: artful ** Attachment added: "virtualbox crushed guest log" https://bugs.launchpad.net/bugs/1716674/+attachment/4948702/+files/virtualbox_crush_guest.log ** Attachment removed: "virtualbox crushed guest log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716674/+attachment/4948702/+files/virtualbox_crush_guest.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1716674 Title: virtualbox crush guest or freeze host screen Status in gnome-shell package in Ubuntu: New Bug description: Virtualbox: 5.1.26 (ubuntu package) + VirtualBox 5.1.26 Oracle VM VirtualBox Extension Pack Host: ubuntu 17.10 (default gnomelibgnome-desktop-3-12 3.25.91.1-0ubuntu2) 4.12.0-12-generic AMD Ryzen5 1600 Guest: ubuntu 16.04 + guest addition The application window of the running guest will crash. Or the host OS screen is not updated. (The mouse pointer responds.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716674] Re: virtualbox crush guest or freeze host screen
** Attachment added: "crush guest log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716674/+attachment/4948703/+files/virtualbox_crush_guest.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1716674 Title: virtualbox crush guest or freeze host screen Status in gnome-shell package in Ubuntu: New Bug description: Virtualbox: 5.1.26 (ubuntu package) + VirtualBox 5.1.26 Oracle VM VirtualBox Extension Pack Host: ubuntu 17.10 (default gnomelibgnome-desktop-3-12 3.25.91.1-0ubuntu2) 4.12.0-12-generic AMD Ryzen5 1600 Guest: ubuntu 16.04 + guest addition The application window of the running guest will crash. Or the host OS screen is not updated. (The mouse pointer responds.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716672] [NEW] Deja-dup can't be unistallled
Public bug reported: I find this utility to be too buggy and its implementation a total hazard so I wanted to uninstall it but I have to uninstall the Mate desktop sudo apt-get purge deja-dup [sudo] password for ccheco: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: deja-dup* deja-dup-backend-cloudfiles* deja-dup-backend-gvfs* deja-dup-backend-s3* deja-dup-caja* ubuntu-mate-desktop* 0 upgraded, 0 newly installed, 6 to remove and 22 not upgraded. After this operation, 3,148 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Tue Sep 12 09:07:58 2017 InstallationDate: Installed on 2017-08-11 (31 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1716672 Title: Deja-dup can't be unistallled Status in deja-dup package in Ubuntu: New Bug description: I find this utility to be too buggy and its implementation a total hazard so I wanted to uninstall it but I have to uninstall the Mate desktop sudo apt-get purge deja-dup [sudo] password for ccheco: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: deja-dup* deja-dup-backend-cloudfiles* deja-dup-backend-gvfs* deja-dup-backend-s3* deja-dup-caja* ubuntu-mate-desktop* 0 upgraded, 0 newly installed, 6 to remove and 22 not upgraded. After this operation, 3,148 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Tue Sep 12 09:07:58 2017 InstallationDate: Installed on 2017-08-11 (31 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1716672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716250] Re: totem and cheese show bright pink/purple video
waiting for 17.2.1 ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1716250 Title: totem and cheese show bright pink/purple video Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: after last updates totem shows wrong colors playing some video, the screenshot from the same video shows correct colors. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 18:33:25 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-09-04 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170903) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1716250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716677] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
*** This bug is a duplicate of bug 1714790 *** https://bugs.launchpad.net/bugs/1714790 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 #1714790, 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/1716677/+attachment/4948705/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716677/+attachment/4948707/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716677/+attachment/4948710/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716677/+attachment/4948711/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716677/+attachment/4948712/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716677/+attachment/4948713/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716677/+attachment/4948714/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1714790 ** 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-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1716677 Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface() Status in gnome-disk-utility package in Ubuntu: New Bug description: Inserted a Sandisk microsd card in a USB adapter into my machine and then launched Gnome disks to find out whether it was formatted as it didn't show up automatically. There was nothing listed, but Gnome disks promptly vanished and this error report appeared shortly afterwards. The adapter is working fine, but at this stage I can't be sure about the card as another identical one is working fine so it may be a faulty card that triggered the error, or the card contents (which I have yet to see, it is either brand new and unused, has been in an Android tablet but not been recognised or is from a Raspberry Pi and has Raspbian on there). Beyond that I can't say at this stage, so will update if I can gather further information. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-disk-utility 3.25.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Tue Sep 12 14:11:26 2017 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2017-06-16 (87 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-disks --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fc2b4826e2f : mov(%rbx),%rdi PC (0x7fc2b4826e2f) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-disk-utility StacktraceTop: g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 udisks_object_get_partition_table () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0 gdu_utils_get_all_contained_objects () gdu_application_has_running_job () ?? () Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface() UpgradeStatus: Upgraded to artful on 2017-09-01 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1716677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716679] Re: gnome-shell crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1714330 *** https://bugs.launchpad.net/bugs/1714330 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 #1714330, 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/1716679/+attachment/4948716/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716679/+attachment/4948718/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716679/+attachment/4948722/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716679/+attachment/4948723/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716679/+attachment/4948724/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716679/+attachment/4948725/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716679/+attachment/4948726/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714330 gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() ** 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/1716679 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() Status in gnome-shell package in Ubuntu: New Bug description: I do not have additional information. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 [modified: usr/share/applications/gnome-shell-extension-prefs.desktop] ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Sep 12 10:10:35 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-06-08 (95 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fae239f5836:mov0x1a0(%rax),%rax PC (0x7fae239f5836) ok source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2 meta_monitor_manager_kms_wait_for_flip () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in g_closure_invoke() 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/1716679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716672] Re: Deja-dup can't be unistallled
Looks like ubuntu-mate-meta should make deja-dup a Recommends, not a Depends, so that users can uninstall it. ** Package changed: deja-dup (Ubuntu) => ubuntu-mate-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1716672 Title: Deja-dup can't be unistallled Status in ubuntu-mate-meta package in Ubuntu: New Bug description: I find this utility to be too buggy and its implementation a total hazard so I wanted to uninstall it but I have to uninstall the Mate desktop sudo apt-get purge deja-dup [sudo] password for ccheco: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: deja-dup* deja-dup-backend-cloudfiles* deja-dup-backend-gvfs* deja-dup-backend-s3* deja-dup-caja* ubuntu-mate-desktop* 0 upgraded, 0 newly installed, 6 to remove and 22 not upgraded. After this operation, 3,148 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Tue Sep 12 09:07:58 2017 InstallationDate: Installed on 2017-08-11 (31 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1716672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716686] [NEW] Black screen
Public bug reported: black screen when starting linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 12 10:40:20 2017 DistUpgraded: 2016-08-11 16:50:28,751 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 945GSE Express Integrated Graphics Controller [17aa:3870] Subsystem: Lenovo Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [17aa:3870] InstallationDate: Installed on 2016-02-03 (586 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1450): WARNING **: Failed to load user image: Falha ao abrir o arquivo "/home/net/.face": Arquivo ou diretório não encontrado g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: LENOVO ideapad S10 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=689cdd2d-3ab0-49ab-8165-f8dc9fc86f2d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-08-11 (396 days ago) dmi.bios.date: 04/13/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 14CN66WW dmi.board.name: Mariana dmi.board.vendor: Lenovo dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr14CN66WW:bd04/13/2009:svnLENOVO:pnideapadS10:pvrLenovo:rvnLenovo:rnMariana:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: ideapad S10 dmi.product.version: Lenovo dmi.sys.vendor: LENOVO version.compiz: compiz 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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 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 Sep 12 10:11:25 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 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/1716686 Title: Black screen Status in xorg package in Ubuntu: New Bug description: black screen when starting linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 12 10:40:20 2017 DistUpgraded: 2016-08-11 16:50:28,751 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 945GSE Express Integrated Graphics Controller [17aa:3870] Subsystem: Lenovo Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [17aa:3870] InstallationDate: Installed on 2016-02-03 (586 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1450): WARNING **: Failed to load user image: Falha ao abrir o arquivo "/home/net/.face": Arquivo ou diretório não encontrado g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: LENOVO ideapad S10 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=689cdd2d-3ab0-49ab-8165-f8dc9fc86f2d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-08-11 (396 days ago) dmi.bios.d
[Desktop-packages] [Bug 1715582] Re: deja-dup fails to backup
Thanks for the update, Wolf! The first error you reported is the real one [1]: "Operation not supported by backend." Samba has a history of being a bit flaky over gvfs. I'll try to reproduce here and see if I know why this is happening for ya. [1] Don't bother running deja-dup with sudo, it's not surprising that it doesn't work. Root doesn't have the same access to the user's DBus session that the user does. So a lot of stuff (including all gvfs file operations) fails. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1715582 Title: deja-dup fails to backup Status in deja-dup package in Ubuntu: Fix Committed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 284427] Re: Evince jumps to other screen in dual monitor setup after file is loaded
It still exists in 17.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/284427 Title: Evince jumps to other screen in dual monitor setup after file is loaded Status in Evince: Fix Released Status in evince package in Ubuntu: Triaged Bug description: Binary package hint: evince Steps to reproduce this behavior in Ubuntu 8.04 (Hardy Heron) using Evince Document Viewer 2.22.2: 1) Launch Evince from Nautilus 2) Maximize Evince on secondary monitor 3) Close Evince 4) Launch Evince from Nautilus on secondary monitor 5) Evince opens maximized on secondary monitor 6) When the file is completely loaded it jumps maximized to the primary monitor The problem doesn't occur if Evince is maximized on the primary monitor or if it is left unmaximized in step 2. To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/284427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716687] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1562639 *** https://bugs.launchpad.net/bugs/1562639 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 #1562639, 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/1716687/+attachment/4948755/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716687/+attachment/4948758/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716687/+attachment/4948768/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716687/+attachment/4948770/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716687/+attachment/4948771/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716687/+attachment/4948772/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716687/+attachment/4948773/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1562639 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1716687 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: resume boot ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Tue Sep 12 20:04:01 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1179:ff80] InstallationDate: Installed on 2017-08-19 (24 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) MachineType: TOSHIBA Satellite Pro L500 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-10-generic root=UUID=3c79e174-6e29-4d4c-8372-729295a33de1 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/06/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.10 dmi.board.name: KSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.10:bd05/06/2010:svnTOSHIBA:pnSatelliteProL500:pvrPSLS4A-00500L:rvnTOSHIBA:rnKSWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite Pro L500 dmi.product.version: PSLS4A-00500L dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Sep 12 20:12:18 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1716687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://laun
[Desktop-packages] [Bug 1716300] Re: Home, Pg Up down keys and arrow keys not funtioning in LibreOffice
I did some more research and found the following which might help the developers to look for the bug. Previously xev command at the terminal did not give response to Delete, Home, PgUp, PgDn,End, Left Arrow or Right Arrow keys. All the other keys functioned as normally they should. I did mapping of the problematic keys (barring PgUp and PgDn) to Function Keys F06, F08, F09, F11 and F12 and managed it for my purposes successfully. I had to perform a hardware check of the keyboard to be sure it was not a case of defective keyboard (and the bug exists in Ubuntu 16.04.3). The hardware man is expected to come tomorrow. Meanwhile I did some major changes in Language Support from English US to English United Kingdom and lo and behold the keys began to respond. I have yet to confirm Left and Right Arrow keys though. SO IT SHOWS THAT IT IS NOT A HARDWARE ISSUE. The xev command also identified the keys. This, I hope, helps the developers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1716300 Title: Home, Pg Up down keys and arrow keys not funtioning in LibreOffice Status in libreoffice package in Ubuntu: New Bug description: File Bug is attached because the description is long. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CurrentDesktop: Unity Date: Mon Sep 11 06:02:17 2017 InstallationDate: Installed on 2017-09-10 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1716300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716415] Re: Alt + Tab then Alt + Right / Left arrow logs me out
After a reboot of my desktop, the key stroke no longer causes the tty switching. I'll keep an eye for any changes / updates that cause it again. -- 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/1716415 Title: Alt + Tab then Alt + Right / Left arrow logs me out Status in gnome-shell package in Ubuntu: New Bug description: One of my systems if I use Alt + Tab to launch the window switcher and then use Alt + Right or Left arrow to switch windows I either receive a tty or get the gdm lock screen. Neither behavior is what I'd expect - the key stroke moving through the window list. This seems to work on another system of mine and certainly did work on this system (otherwise I wouldn't be using the key stroke) so perhaps a package was updated and I haven't rebooted yet? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 11 07:32:15 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1698 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1716456] Re: crash on click Activities when app is running
Ok... Unfortunately I could not find /var/log/Xorg.0.log . There is no file named Xorg.0.log in my /var/log... nor in any of its subfolders. $ lspci -k 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04) Subsystem: Dell Device 0798 Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 05) Subsystem: Dell Skylake Processor Thermal Subsystem Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) Subsystem: Dell Sunrise Point-H USB 3.0 xHCI Controller Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) Subsystem: Dell Sunrise Point-H Thermal subsystem Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31) Subsystem: Dell Sunrise Point-H Serial IO I2C Controller Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31) Subsystem: Dell Sunrise Point-H Serial IO I2C Controller Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) Subsystem: Dell Sunrise Point-H CSME HECI Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 31) Subsystem: Dell 82801 Mobile SATA Controller [RAID mode] Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) Subsystem: Dell Sunrise Point-H LPC Controller 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) Subsystem: Dell Sunrise Point-H PMC 00:1f.3 Audio device: Intel Corporation Device a171 (rev 31) Subsystem: Dell Device 0798 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) Subsystem: Dell Sunrise Point-H SMBus Kernel modules: i2c_i801 01:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) Subsystem: Dell GP107GL High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Dell QCA6174 802.11ac Wireless Network Adapter Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci $ xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 eDP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.05*+ 59.9348.04 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm 1920x1080 60.00*+ 50.0059.94 1920x1080i60.0050.0059.94 1680x1050 59.88 1400x1050 59.95 1600x900
[Desktop-packages] [Bug 1716456] Re: crash on click Activities when app is running
Today I performed a new dist-upgrade on my computer ... I noticed that version 4.13.10 of the kernel was installed. After that I renamed my home folder and created a new one to delete all the old settings. The crash keeps happening anyway. -- 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/1716456 Title: crash on click Activities when app is running Status in gnome-shell package in Ubuntu: Incomplete Bug description: I believe this bug is related to the video driver but I'm not sure ... Anyway there goes the report: This is a crash that happens every time I open two different applications (for example: Chromium and Nautilus), one of them in workspace 1 and the other in workspace 2. When I change the focus between them for some time (from 3 to 5 times), there is a crash that causes, first, the window manager (or gnome shell, I'm not sure) to reboot, then, if I insist on trying to switch between the applications for some more times, the crash seems to be more severe and ubuntu returns to the login screen (gdm3). I'm using a dell inspiron 15 series 7000 (gaming), notebook with 2 displays (one is the display of the notebook itself and the other is an LG 23EA53, connected via HDMI and configured as a primary) To make the focus change I use the mouse, I click on "Activities" and, with the mouse, I click on the application that appears in the workspaces pile to the right of the display, below and above, successively until the crach occurs. Using Alt-TAB it seems at first that the crash does not occur ... or it takes longer to occur :-) This crash occurs when both applications are in the same workspace as well ... And if one of the applications is a virtual machine session of Virtualbox, crash occurs more quickly (with less focus shifts). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 14:46:38 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-12 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716300] Re: Home, Pg Up down keys and arrow keys not funtioning in LibreOffice
I find that the disputed keys again stopped functioning. xev command also does not identify the key-press event. All in a matter of a few minutes. It leaves me in the wilderness. I will check the keyboard hardware and get back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1716300 Title: Home, Pg Up down keys and arrow keys not funtioning in LibreOffice Status in libreoffice package in Ubuntu: New Bug description: File Bug is attached because the description is long. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.6~rc2-0ubuntu1~xenial2 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CurrentDesktop: Unity Date: Mon Sep 11 06:02:17 2017 InstallationDate: Installed on 2017-09-10 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1716300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1602458] Re: /usr/bin/gnome-software:11:g_type_check_instance_cast:GS_APP:transaction_property_changed_cb:emit_signal_instance_in_idle_cb:g_main_dispatch
Try to understand me as yr collaborator and FIX this DAMNED BUG, AT LAST (*once for all*) PLEASE. -- 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/1602458 Title: /usr/bin/gnome- software:11:g_type_check_instance_cast:GS_APP:transaction_property_changed_cb:emit_signal_instance_in_idle_cb:g_main_dispatch Status in gnome-software package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with version 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1, the problem page at https://errors.ubuntu.com/problem/77807d3502a3e74469d5b5dca0a34e9197c647d6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1602458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716700] [NEW] "Please sync pulseaudio from debian Buster" where pulseaudio (11.0-1)
Public bug reported: PulseAudio 11.0 release notes Changes at a glance Support for newer AirPlay hardware USB and bluetooth devices preferred over internal sound cards The default sink and source configuration is remembered better Bluetooth HSP headset role implemented Bluetooth HFP audio gateway role implemented (requires oFono) Bluetooth HSP audio gateway and HFP hands-free unit roles can be enabled simultaneously Upmixing can now be disabled without bad side effects Avoid having unavailable sinks or sources as the default Option to avoid resampling more often Option to automatically switch bluetooth profile to HSP more often Better latency regulation in module-loopback Changed module argument names in module-ladspa-sink and module-virtual-surround-sink Fixed input device handling on Windows Improved bluetooth MTU configuration (warning! this causes some hardware to not work any more, see the details below for how to fix it) GNU Hurd support Applications can request LADSPA or virtual surround filtering for their streams Support for 32-bit applications on 64-bit systems in padsp https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful pulseaudio upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1716700 Title: "Please sync pulseaudio from debian Buster" where pulseaudio (11.0-1) Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio 11.0 release notes Changes at a glance Support for newer AirPlay hardware USB and bluetooth devices preferred over internal sound cards The default sink and source configuration is remembered better Bluetooth HSP headset role implemented Bluetooth HFP audio gateway role implemented (requires oFono) Bluetooth HSP audio gateway and HFP hands-free unit roles can be enabled simultaneously Upmixing can now be disabled without bad side effects Avoid having unavailable sinks or sources as the default Option to avoid resampling more often Option to automatically switch bluetooth profile to HSP more often Better latency regulation in module-loopback Changed module argument names in module-ladspa-sink and module-virtual-surround-sink Fixed input device handling on Windows Improved bluetooth MTU configuration (warning! this causes some hardware to not work any more, see the details below for how to fix it) GNU Hurd support Applications can request LADSPA or virtual surround filtering for their streams Support for 32-bit applications on 64-bit systems in padsp https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1716700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715582] Re: deja-dup fails to backup
Does this work if you open your samba server in Nautilus ("Files")?
Deja-dup just uses the same gvfs operations nautilus does. If it works
there, it should work in deja-dup.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1715582
Title:
deja-dup fails to backup
Status in deja-dup package in Ubuntu:
Fix Committed
Bug description:
OS: Ubuntu 17.10 beta
setting up deja-dup to backup to smb/ssh server fails
With ssh: Permission denied
syslog:
Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How
does the code know the size to allocate?
Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from
uid 1000 finished with success after 414ms
with smb: Backup failed
InvalidBackendURL: missing // - relative paths not supported for scheme
gio+invalid: gio+invalid://
syslog:
Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How
does the code know the size to allocate?
Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from
uid 1000 finished with success after 402ms
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 35.6-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 7 10:30:37 2017
InstallationDate: Installed on 2017-09-05 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716707] [NEW] libreoffice writer crashes on start
Public bug reported: 1) lsb_release -rd Description:Ubuntu 17.04 Release:17.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:5.3.1-0ubuntu2 Candidate: 1:5.3.1-0ubuntu2 Version table: *** 1:5.3.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages 100 /var/lib/dpkg/status apt-show-versions -r libreoffice* libreoffice:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-avmedia-backend-gstreamer:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base-core:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base-drivers:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-calc:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-common:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-core:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-draw:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-gnome:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-gtk3:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-impress:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-java-common:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-librelogo:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-math:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-nlpsolver:all/zesty 0.9+LibO5.3.1-0ubuntu2 uptodate libreoffice-ogltrans:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-pdfimport:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-report-builder:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-report-builder-bin:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-script-provider-bsh:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-script-provider-js:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-script-provider-python:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-sdbc-firebird:i386 not installed libreoffice-sdbc-hsqldb:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-sdbc-postgresql:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-style-breeze:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-style-galaxy:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-style-tango:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-wiki-publisher:all/zesty 1.2.0+LibO5.3.1-0ubuntu2 uptodate libreoffice-writer:i386/zesty 1:5.3.1-0ubuntu2 uptodate 3) What is expected to happen in Writer is . Start libreoffice writer from: - Desktop menu: Office => Libre Office Writer - Filetype association: /.../anyfile.odf or /.../anyfile.doc - from Libre suite => Libre Office Writer The libreoffice writer initial dialog is displayed. After the dialog indicates "100% complete", the dialog closes. Then, the writer application opens a blank document or the selected document. 4) What happened instead is... (All in step 3 above until: After the dialog indicates "100% complete", the dialog closes). But, the writer crashes or fails to start. The writer does not open. There are no error messages or dialogs displayed. The problem does not occur with the other libreoffice applications (suite, base, calc, impress, math). -Version- Kernel : Linux 4.10.0-33-generic (i686) Compiled: #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 C Library : GNU C Library version (Ubuntu GLIBC 2.24-9ubuntu2.2) 2.24 (unstable) Default C Compiler : GNU C Compiler version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) Distribution: Ubuntu 17.04 -Current Session- Desktop Environment : LXDE (Lubuntu) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libreoffice-writer 1:5.3.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 CurrentDesktop: LXDE Date: Tue Sep 12 11:02:21 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (339 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1716707 Title: libreoffice writer crashes on start Status in libreoffice package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:5.3.1-0ubuntu2 Candidate: 1:5.3.1-0ubuntu2 Version table: *** 1:5.3.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages 100 /var/lib/dpkg/status apt-show-versions -r libreoffice* libreoffice:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-avmedia-backend-gstreamer:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base-core:i386/zesty 1:5.3.
[Desktop-packages] [Bug 1640171] Re: Molecules are not rendered, black screen
Any chance the maintainer the use the fix from the debian package? I have the same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to avogadro in Ubuntu. https://bugs.launchpad.net/bugs/1640171 Title: Molecules are not rendered, black screen Status in avogadro package in Ubuntu: Confirmed Bug description: Description: Recent version of avogadro package is not working properly. It is not possible to draw molecule or to display molecule from the pdb/gro file. Ubuntu version: Description: Ubuntu 16.10 Release: 16.10 Here is the console log: @jakubkrajniak ~ $ avogadro "Avogadro version:1.1.1 Git: LibAvogadro version: 1.1.1 Git:" Locale: "en_US" Libavogadro translations not found. System has OpenGL support. About to test OpenGL capabilities. OpenGL capabilities found: Double Buffering. Direct Rendering. Antialiasing. Loading plugins: "/usr/bin/../lib/avogadro/1_1" Searching for plugins in "/usr/lib/avogadro/1_1" Searching for plugins in "/usr/lib/avogadro/1_1/colors" Searching for plugins in "/usr/lib/avogadro/1_1/engines" Searching for plugins in "/usr/lib/avogadro/1_1/extensions" Searching for plugins in "/usr/lib/avogadro/1_1/tools" Loading plugins: "/home/teodor/.avogadro/1_1/plugins" Settings are missing for the next engines: () QStackedLayout::setCurrentWidget: Widget 0x55f9c0f637b0 not contained in stack dev warning: Extension "GAMESS" is using a deprecated DockWidget loading method. See Extension::dockWidgets() documentation. dev warning: Extension "Orbitals" is using a deprecated DockWidget loading method. See Extension::dockWidgets() documentation. Could not find python module... dev warning: Extension "Python Terminal" is using a deprecated DockWidget loading method. See Extension::dockWidgets() documentation. dev warning: Extension "Vibration" is using a deprecated DockWidget loading method. See Extension::dockWidgets() documentation. GLWidget initialisation... GLSL support enabled, OpenGL 2.0 support confirmed. GLWidget initialised... createObjects() libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: cHRM: invalid chromaticities Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avogadro/+bug/1640171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716708] [NEW] Network settings missing DNS searchlist entry
Public bug reported: Description:Ubuntu Artful Aardvark (development branch) Release:17.10 There is no way to enter a DNS searchlist in the network settings dialog for a static IP Configuration. Regards Reiner ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1716708 Title: Network settings missing DNS searchlist entry Status in gnome-software package in Ubuntu: New Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 There is no way to enter a DNS searchlist in the network settings dialog for a static IP Configuration. Regards Reiner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
This can also happen while the screen is locked, hence revealing any possibly sensitive information on the screen, if running in X (in Wayland it probably just crashes completely). Hence upgrading to importance to High. ** Changed in: gnome-shell (Ubuntu) Importance: Medium => 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7accb2ea7fd305736eb23cca5905e4b690a16cae --- gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Sep 3 02:41:44 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (562 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7feb5dff7e26 : mov(%rdi),%rdi PC (0x7feb5dff7e26) ok source "(%rdi)" (0x3fe0) not located in a known VMA region (needed readable region)! destination "%rdi" 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 () at /usr/lib/gnome-shell/libgnome-shell.so g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin mock plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 468288] new message
*** This bug is a duplicate of bug 460039 *** https://bugs.launchpad.net/bugs/460039 Please have a löök at söme nice things I've picked för yöu, I just löve them) Here, check this öut http://forenadebolag.se/wp- content/plugins/alert_list/uploads/audio/refuse.php?UE80NjgyODhAYnVncy5sYXVuY2hwYWQubmV0 Looking forward, Barbara Burgos From: Bug 468288 [mailto:468...@bugs.launchpad.net] Sent: Tuesday, September 12, 2017 12:14 PM To: rol...@javalia.se Subject: coming on :D Early 20th century nationalism was so strong in many European countries that they used it to justify conquering countries all around the world. It's a very different kind of nationalism than today where people might just insult each other at a football match or have some fights when they have drank too much. Completely different scale. Sent from Mail for Windows 10 ** Attachment added: "320F02842E610570.jpg" https://bugs.launchpad.net/bugs/468288/+attachment/4948874/+files/320F02842E610570.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-butterfly in Ubuntu. https://bugs.launchpad.net/bugs/468288 Title: telepathy-butterfly crashed with TypeError in __common_callback() Status in telepathy-butterfly package in Ubuntu: New Bug description: Binary package hint: telepathy-butterfly I don't know what to write here... ProblemType: Crash Architecture: amd64 Date: Sun Nov 1 11:56:09 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/telepathy/telepathy-butterfly InterpreterPath: /usr/bin/python2.6 Package: telepathy-butterfly 0.5.2-0ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly ProcEnviron: SHELL=/bin/bash LANG=sv_SE.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly'] SourcePackage: telepathy-butterfly Title: telepathy-butterfly crashed with TypeError in __common_callback() Uname: Linux 2.6.31-14-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (gnome-settings-daemon:1813): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1813): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1941): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1914): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-butterfly/+bug/468288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 460039] ☢yöu have tö nöte that
I've just seen söme amazing stuff, yöu'll definitely like it töö, please take a löök http://bramberinc.com/survival.php?UE80NjAwMzlAYnVncy5sYXVuY2hwYWQubmV0 Sincerely yours, Deborah Kilgore From: Bug 460039 [mailto:460...@bugs.launchpad.net] Sent: Tuesday, September 12, 2017 12:14 PM To: rol...@javalia.se Subject: cash in hand There's no need for England to have the "land" on it. We're just gonna call you Eng from now on. Seeing the "land" irks me beyond belief for no real good reason. No countries from *my* continent have "land" at the end of their country name so therefore it's wrong. I think the thing that annoys me most about it, is there is zero need for the "land", that sentence would make perfect sense with only the Eng bit. Sent from Mail for Windows 10 ** Attachment added: "9AA820FB9E57B434.jpg" https://bugs.launchpad.net/bugs/460039/+attachment/4948873/+files/9AA820FB9E57B434.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-butterfly in Ubuntu. https://bugs.launchpad.net/bugs/460039 Title: telepathy-butterfly crashed with TypeError in __common_callback() Status in telepathy-butterfly: Fix Released Status in telepathy-butterfly package in Ubuntu: Fix Released Bug description: Binary package hint: telepathy-butterfly I was going to the list of Empathy notifications (Mail Icon in Top panel) and I refused all contact requests as I did not know those contacts. One entry appeared 2 times: "Ajinkya X0m". When clicking in the lower entry the telepathy-butterfly crashed and apport came up. ProblemType: Crash Architecture: i386 Date: Sat Oct 24 23:09:15 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/lib/telepathy/telepathy-butterfly InterpreterPath: /usr/bin/python2.6 Package: telepathy-butterfly 0.5.2-0ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic PythonArgs: ['/usr/lib/telepathy/telepathy-butterfly'] SourcePackage: telepathy-butterfly Title: telepathy-butterfly crashed with TypeError in __common_callback() Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-butterfly/+bug/460039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716741] [NEW] [artful] After killing Google Chrome, X.org crashes
Public bug reported: Sometimes (quite often recently) Google Chrome gets stuck on my computer - its not responding at all and when resizing the window there is no repaint. If I then kill the process (it seems to happen both for TERM and KILL), the Google Chrome windows close and everything seems to work for a some short time (less than a minute) and then I get kicked out of the session. Looking at the Xorg.0.log.old, I see this: [ 7529.780] (EE) [ 7529.780] (EE) Backtrace: [ 7529.781] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55ad1ae6541d] [ 7529.781] (EE) 1: /usr/lib/xorg/Xorg (0x55ad1acad000+0x1bc1a9) [0x55ad1ae691a9] [ 7529.781] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f6038c5e000+0x11670) [0x7f6038c6f670] [ 7529.781] (EE) 3: /usr/lib/xorg/Xorg (present_event_notify+0x2f) [0x55ad1ade58ff] [ 7529.781] (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (0x7f60349c5000+0xec3f) [0x7f60349d3c3f] [ 7529.781] (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (0x7f60349c5000+0xf93b) [0x7f60349d493b] [ 7529.781] (EE) 6: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmHandleEvent+0xc7) [0x7f603a333627] [ 7529.781] (EE) 7: /usr/lib/xorg/Xorg (0x55ad1acad000+0x1bcc81) [0x55ad1ae69c81] [ 7529.781] (EE) 8: /usr/lib/xorg/Xorg (WaitForSomething+0x1fb) [0x55ad1ae62c7b] [ 7529.781] (EE) 9: /usr/lib/xorg/Xorg (0x55ad1acad000+0x52bc3) [0x55ad1acffbc3] [ 7529.781] (EE) 10: /usr/lib/xorg/Xorg (0x55ad1acad000+0x56e40) [0x55ad1ad03e40] [ 7529.781] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f60388b9421] [ 7529.781] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2a) [0x55ad1acedb2a] [ 7529.781] (EE) [ 7529.781] (EE) Segmentation fault at address 0x50 [ 7529.781] (EE) Fatal server error: [ 7529.781] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 7529.781] (EE) [ 7529.781] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 7529.781] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 7529.781] (EE) [ 7529.781] (II) AIGLX: Suspending AIGLX clients for VT switch [ 7529.833] (EE) Server terminated with error (1). Closing log file. Hardware: Dell Precision mobile workstation 5520 (Windows model, I couldn't get the Ubuntu version in my country), with Nvidia - but turned off in prime and Xorg is running on the Intel IGD. $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05) 00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 05) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1) 00:1d.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #15 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Device a171 (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 3D controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev ff) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu Artful Aardvark (development branch)" $ dpkg -l xorg* ii xorg 1:7.7+19ubuntu2 un xorg-docs ii xorg-docs-core1:1.7.1-1ubuntu1 un xorg-driver-binary
[Desktop-packages] [Bug 1716749] [NEW] Synaptics is not fully aware of display environment
Public bug reported: In a dual monitor environment where separate Xfce4 desktops are running on each monitor, you can start Synaptic in either desktop environment, but if you start it on display :0.1, it shows the Authenticate pop-up window on display :0.0. Once the password is entered, the main window will then appear on display :0.1. All the components of a given program should be display-environment-aware. There are a number of system applications that have similar problems. I'll report them as I continue to encounter this problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 12 11:21:53 2017 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/ksh SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1716749 Title: Synaptics is not fully aware of display environment Status in xorg package in Ubuntu: New Bug description: In a dual monitor environment where separate Xfce4 desktops are running on each monitor, you can start Synaptic in either desktop environment, but if you start it on display :0.1, it shows the Authenticate pop-up window on display :0.0. Once the password is entered, the main window will then appear on display :0.1. All the components of a given program should be display-environment-aware. There are a number of system applications that have similar problems. I'll report them as I continue to encounter this problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 12 11:21:53 2017 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/ksh SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-05-27 (108 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) Subsystem: Dell HD Graphics 620 Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 02) Subsystem: Dell Skylake Processor Thermal Subsystem Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) Subsystem: Dell Sunrise Point-LP Thermal subsystem Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) Subsystem: Dell Sunrise Point-LP CSME HECI Kernel driver in use: mei_me Kernel modules: mei_me 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) Subsystem: Dell Sunrise Point-LP LPC Controller 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) Subsystem: Dell Sunrise Point-LP PMC Kernel driver in use: intel_pmc_core 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) Subsystem: Dell Device 075b Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) Subsystem: Dell Sunrise Point-LP SMBus Kernel modules: i2c_i801 3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) Subsystem: Dell RTS525A PCI Express Card Reader Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 3c:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0115 (rev 01) Subsystem: Toshiba America Info Systems Device 0001 Kernel driver in use: nvme Kernel modules: nvme -- 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/1716503 Title: gnome-shell --wayland works only when --mode=initial-setup Status in gnome-shell package in Ubuntu: Incomplete Bug description: Package: gnome-shell Version: 3.25.91-0ubuntu4 marcogh@fate:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Since a couple of version of gnome-shell, --wayland doesn't work anymore. When launching from console with: gnome-shell --wayland --display-server --mode=classic the screen remains black, the cursor appears in the middle, and nothing else. killing gnome-shell from remote ssh brings the console back, with no error. Curiously, it works (and it's wayland) when i add --mode=initial-setup The Xorg version works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpa
[Desktop-packages] [Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup
sorry for the delay. -- 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/1716503 Title: gnome-shell --wayland works only when --mode=initial-setup Status in gnome-shell package in Ubuntu: Incomplete Bug description: Package: gnome-shell Version: 3.25.91-0ubuntu4 marcogh@fate:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Since a couple of version of gnome-shell, --wayland doesn't work anymore. When launching from console with: gnome-shell --wayland --display-server --mode=classic the screen remains black, the cursor appears in the middle, and nothing else. killing gnome-shell from remote ssh brings the console back, with no error. Curiously, it works (and it's wayland) when i add --mode=initial-setup The Xorg version works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716456] Re: crash on click Activities when app is running
I purged the xorg-edgers ppa in order to eliminate unstable libraries ... yet the crash continues to occur. I could not get an earlier version to downgrade xserver-xorg-video- nouveau and doing some tests. The situation gets very unstable when I allocate 1 application in each workarea ... when it arrives in 4 or 5 workareas the session falls and ubuntu returns to the login interface. -- 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/1716456 Title: crash on click Activities when app is running Status in gnome-shell package in Ubuntu: Incomplete Bug description: I believe this bug is related to the video driver but I'm not sure ... Anyway there goes the report: This is a crash that happens every time I open two different applications (for example: Chromium and Nautilus), one of them in workspace 1 and the other in workspace 2. When I change the focus between them for some time (from 3 to 5 times), there is a crash that causes, first, the window manager (or gnome shell, I'm not sure) to reboot, then, if I insist on trying to switch between the applications for some more times, the crash seems to be more severe and ubuntu returns to the login screen (gdm3). I'm using a dell inspiron 15 series 7000 (gaming), notebook with 2 displays (one is the display of the notebook itself and the other is an LG 23EA53, connected via HDMI and configured as a primary) To make the focus change I use the mouse, I click on "Activities" and, with the mouse, I click on the application that appears in the workspaces pile to the right of the display, below and above, successively until the crach occurs. Using Alt-TAB it seems at first that the crash does not occur ... or it takes longer to occur :-) This crash occurs when both applications are in the same workspace as well ... And if one of the applications is a virtual machine session of Virtualbox, crash occurs more quickly (with less focus shifts). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 14:46:38 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-12 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10
Another possible duplicate: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262 -- 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/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 Status in network-manager package in Ubuntu: In Progress Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: In Progress Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed before rebooting you should have a network connection after you reboot. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install netplan, configure to set up static network on an ethernet device using netplan. 4) Upgrade to yakkety 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
I am affected by this problem and possibly another very similar issue using a Sony MDR-100ABN headset. Using two different computers (one with BT built-in, one with a USB-Dongle), both running Ubuntu 17.04 (same bluez and pulseaudio versions), I experience different behavior. On PC1 I have the same error as described but after several pairing/unpairing or connecting/disconnecting tries this can is often resolved. This means switching between A2DP (stereo output) and HFP/HSP (mono output, mono input) is working just fine. Ultimately this looks like an actual bt connection issue to me. On PC2 the behavior is similar, but with a different error message: "[pulseaudio] backend-native.c: connect(): Die angeforderte Funktion ist nicht implementiert" (I think the original libc string is "Function not implemented"). Here I haven't been able to get HFP/HSP working at all. Both systems show the headset connected as 'Headset', 'Handsfree' and 'Audio-Ausgabe' (='Audio output'). The output from bluetoothctl is also the same: [h.ear (MDR-100ABN)]# show Controller 00:15:83:E8:XX:XX (masked) Name: XXX (masked) Alias: XXX (masked) Class: 0x0c0104 Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d052B Discovering: no Software versions: pulseaudio, pulseaudio-module-bluetooth and pulseaudio-utils: 1:10.0-1ubuntu2 (amd64) bluez: 5.43-0ubuntu1 (amd64) Please let me know what other type of information you need and I will try to provide that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716775] [NEW] Please consider disabling gnome-shell animations by default
Public bug reported: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. - Am filing this bug 1st rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. + Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1716775 Title: Please consider disabling gnome-shell animations by default Status in ubuntu-settings package in Ubuntu: New Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1716775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716456] Re: crash on click Activities when app is running
I am still doing some tests but there is a possibility that the cause of these crashs is some or some gnome extensions. I turned off the extensions: - Native Windows Placement (https://extensions.gnome.org/extension/18/native-window-placement/) - Auto Move Windows (https://extensions.gnome.org/extension/16/auto-move-windows/) - Window Navigator (https://extensions.gnome.org/extension/10/windownavigator/) ... and I tried to repeat the incident but it looks like the gnome-shell has stabilized, but it's still not conclusive. I'll continue the tests tomorrow. -- 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/1716456 Title: crash on click Activities when app is running Status in gnome-shell package in Ubuntu: Incomplete Bug description: I believe this bug is related to the video driver but I'm not sure ... Anyway there goes the report: This is a crash that happens every time I open two different applications (for example: Chromium and Nautilus), one of them in workspace 1 and the other in workspace 2. When I change the focus between them for some time (from 3 to 5 times), there is a crash that causes, first, the window manager (or gnome shell, I'm not sure) to reboot, then, if I insist on trying to switch between the applications for some more times, the crash seems to be more severe and ubuntu returns to the login screen (gdm3). I'm using a dell inspiron 15 series 7000 (gaming), notebook with 2 displays (one is the display of the notebook itself and the other is an LG 23EA53, connected via HDMI and configured as a primary) To make the focus change I use the mouse, I click on "Activities" and, with the mouse, I click on the application that appears in the workspaces pile to the right of the display, below and above, successively until the crach occurs. Using Alt-TAB it seems at first that the crash does not occur ... or it takes longer to occur :-) This crash occurs when both applications are in the same workspace as well ... And if one of the applications is a virtual machine session of Virtualbox, crash occurs more quickly (with less focus shifts). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 14:46:38 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-12 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 500175] Re: Canceling an installation in Software Center crashes debconf with "Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthroug
** Tags added: rls-aa-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/500175 Title: Canceling an installation in Software Center crashes debconf with "Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66," Status in aptdaemon package in Ubuntu: Confirmed Status in debconf package in Ubuntu: Confirmed Status in software-center package in Ubuntu: Confirmed Status in aptdaemon source package in Lucid: Won't Fix Status in debconf source package in Lucid: Won't Fix Status in software-center source package in Lucid: Won't Fix Bug description: Binary package hint: acroread I accidentally clicked "Cancel" when it asked me if I wanted to set Adobe Reader as the default PDF viewer. It then apparently crashed. == HOW TO REPRODUCE == In software-center choose "Adobe Reader 9" and install it. At prompt "Set Adobe Reader as the default PDF viewer" click "Cancel" The installation crashes with the error below The relevant error is = Setting up acroread (9.2-1karmic1) ... Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, line 6. Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, line 6. Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, line 6. Use of uninitialized value in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 202, line 6. Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, line 6. Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, line 6. Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, line 6. Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212, line 6. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, line 6. Use of uninitialized value $val in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 83, line 4. Use of uninitialized value $val in concatenation (.) or string at /usr/share/perl5/Debconf/Format/822.pm line 84, line 4. dpkg: error processing acroread (--configure): subprocess installed post-installation script returned error exit status 128 = ProblemType: Package AptOrdering: acroread: Install acroread: Configure Architecture: i386 Date: Thu Dec 24 17:06:00 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 128 NonfreeKernelModules: wl Package: acroread (not installed) ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: acroread Title: package acroread (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Uname: Linux 2.6.31-17-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/500175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716788] [NEW] Hang on running Windows 8 VM in virtualBox
Public bug reported: To (try to) reproduce: Start Windows 8 in VirtualBox Run the Gnome System Monitor whilst the vm is starting Try to switch tabs within the Gnome System Monitor My result: Gnome System Monitor hangs. Mint 18.2 x64 Cinnamon. Gnome System Monitor 3.18.2-1ubuntu1 ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1716788 Title: Hang on running Windows 8 VM in virtualBox Status in gnome-system-monitor package in Ubuntu: New Bug description: To (try to) reproduce: Start Windows 8 in VirtualBox Run the Gnome System Monitor whilst the vm is starting Try to switch tabs within the Gnome System Monitor My result: Gnome System Monitor hangs. Mint 18.2 x64 Cinnamon. Gnome System Monitor 3.18.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1716788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 932714] Re: Audio settings won't open: gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist()
*** This bug is a duplicate of bug 932446 *** https://bugs.launchpad.net/bugs/932446 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/932714 Title: Audio settings won't open: gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: iI cannot open the audio settings neither from the system settings nor the notification bar in the top right corner. dmesg reporst this: gnome-control-c[2221]: segfault at 18 ip b749c54c sp bff99440 error 4 in libgtk-3.so.0.314.0[b71f6000+4da000] ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.2.2-2ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Wed Feb 15 14:21:56 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120213) ProcCmdline: gnome-control-center sound-nua SegvAnalysis: Segfault happened at: 0xb749c54c :mov 0x18(%eax),%ebp PC (0xb749c54c) ok source "0x18(%eax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%ebp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: gtk_tree_model_get_valist () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 gtk_tree_model_get () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/control-center-1/panels/libsoundnua.so g_cclosure_marshal_VOID(unsigned int0_t) () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 21.2-0ubuntu4 gnome-bluetooth3.2.2-0ubuntu1 indicator-datetime 0.3.1-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/932714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display
I'm not able to reproduce with 1.18.3-0ubuntu1.1 on my 16.04 LTS laptop with external screen (higher resolution than built-in) and Intel graphics. Robert, any ideas? Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1716752 Title: LightDM Bypass - lock screen doesn't resize after adding new display Status in lightdm package in Ubuntu: New Bug description: I'm able to consistently bypass LightDM and access my desktop without a password, simply by plugging in my external monitor. I'm running it on Linux Mint - let me know if this bug is more appropriate for their issue tracker. I made a 1 minute video demonstrating the issue, which might be easier to understand than text. Sorry in advance for filming vertically. https://www.youtube.com/watch?v=EWs_SQJ1-Ak 1) $ lsb_release -rd Description: Linux Mint 18.2 Sonya Release: 18.2 2) $ apt-cache policy lightdm lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) I plugged in my external monitor to my laptop while it was locked. I expected my computer to remain locked even though I had plugged in a new display. 4) The new monitor was not covered by LightDM, allowing me to interact with it. Additionally, parts of my laptop monitor became uncovered. Notes: My laptop display is a 3200x1800 QHD (HiDPI) display when it's standalone but I downscale it to 1600x900 when it has an attached monitor, due to Ubuntu's scaling issues when connecting HiDPI and regular monitors. It's possible that LightDM doesn't think to resize, or resizes incorrectly, when the laptop screen automatically downscales as the new display is attached. I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce 840M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1716752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
This affects linux-aws 4.4.0-1020-aws as well. I ran into this issue on that kernel. https://github.com/collectd/collectd/issues/2321#issuecomment-311634825 Seems maybe fixed in 4.4.0-1022-aws ** Bug watch added: github.com/collectd/collectd/issues #2321 https://github.com/collectd/collectd/issues/2321 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux- image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in commons-daemon package in Ubuntu: Confirmed Status in eclipse package in Ubuntu: Confirmed Status in imagej package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in octave package in Ubuntu: Confirmed Status in python-jpype package in Ubuntu: Confirmed Status in rustc package in Ubuntu: Confirmed Status in scilab package in Ubuntu: Confirmed Status in linux package in Debian: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716793] Re: Gnome session fails to lock automatically when VirtualBox VM is in the foreground
*** This bug is a duplicate of bug 49579 *** https://bugs.launchpad.net/bugs/49579 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 49579, so it is being marked as such. This is a fundamental bug in the design of X11 and cannot be easily fixed within X11. You should manually lock your screen if a locked session is important to you. Please continue to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 49579 screen doesn't lock when some menu is open -- 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/1716793 Title: Gnome session fails to lock automatically when VirtualBox VM is in the foreground Status in gnome-shell package in Ubuntu: Confirmed Bug description: In Ubuntu Gnome 16.04, if a VirtualBox VM is in the foreground, Gnome will not lock the screen automatically, and will display a message that it couldn't lock the screen. This could allow an unauthorized user with physical access to gain access to the session. Locking the session manually from the menu still works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zavl zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 18:58:03 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 'org.gnome.Nautilus.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716415] Re: Alt + Tab then Alt + Right / Left arrow logs me out
** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1716415 Title: Alt + Tab then Alt + Right / Left arrow logs me out Status in gnome-shell package in Ubuntu: Incomplete Bug description: One of my systems if I use Alt + Tab to launch the window switcher and then use Alt + Right or Left arrow to switch windows I either receive a tty or get the gdm lock screen. Neither behavior is what I'd expect - the key stroke moving through the window list. This seems to work on another system of mine and certainly did work on this system (otherwise I wouldn't be using the key stroke) so perhaps a package was updated and I haven't rebooted yet? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 11 07:32:15 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1698 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup
Please try reproducing the problem again, and as soon as it happens switch VTs, login and take a copy of the system log: journalctl > journalctl.txt and attach it here. -- 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/1716503 Title: gnome-shell --wayland works only when --mode=initial-setup Status in gnome-shell package in Ubuntu: Incomplete Bug description: Package: gnome-shell Version: 3.25.91-0ubuntu4 marcogh@fate:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Since a couple of version of gnome-shell, --wayland doesn't work anymore. When launching from console with: gnome-shell --wayland --display-server --mode=classic the screen remains black, the cursor appears in the middle, and nothing else. killing gnome-shell from remote ssh brings the console back, with no error. Curiously, it works (and it's wayland) when i add --mode=initial-setup The Xorg version works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716456] Re: crash on click Activities when app is running
I suggest you install the official Nvidia drivers for stability: sudo apt install nvidia-375 Also, do you have any crash files in /var/crash/ ? -- 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/1716456 Title: crash on click Activities when app is running Status in gnome-shell package in Ubuntu: Incomplete Bug description: I believe this bug is related to the video driver but I'm not sure ... Anyway there goes the report: This is a crash that happens every time I open two different applications (for example: Chromium and Nautilus), one of them in workspace 1 and the other in workspace 2. When I change the focus between them for some time (from 3 to 5 times), there is a crash that causes, first, the window manager (or gnome shell, I'm not sure) to reboot, then, if I insist on trying to switch between the applications for some more times, the crash seems to be more severe and ubuntu returns to the login screen (gdm3). I'm using a dell inspiron 15 series 7000 (gaming), notebook with 2 displays (one is the display of the notebook itself and the other is an LG 23EA53, connected via HDMI and configured as a primary) To make the focus change I use the mouse, I click on "Activities" and, with the mouse, I click on the application that appears in the workspaces pile to the right of the display, below and above, successively until the crach occurs. Using Alt-TAB it seems at first that the crash does not occur ... or it takes longer to occur :-) This crash occurs when both applications are in the same workspace as well ... And if one of the applications is a virtual machine session of Virtualbox, crash occurs more quickly (with less focus shifts). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 14:46:38 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-12 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716809] [NEW] choppy graphics
Public bug reported: graphics frame-rate is choppy in chrome, both stills and video, no problems before recent-ish update(s) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-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: Tue Sep 12 19:04:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. BeaverCreek [Radeon HD 6520G] [1043:2122] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-04-05 (160 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK Computer Inc. K53TK ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=f4c1c213-4cf8-455f-a1d4-76311b393c40 ro vesafb.invalid=1 nopat plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TK dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK53TK:pvr1.0:rvnASUSTeKComputerInc.:rnK53TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer 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.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Sep 5 11:56:19 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 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/1716809 Title: choppy graphics Status in xorg package in Ubuntu: New Bug description: graphics frame-rate is choppy in chrome, both stills and video, no problems before recent-ish update(s) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-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: Tue Sep 12 19:04:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. BeaverCreek [Radeon HD 6520G] [1043:2122] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-04-05 (160 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK Computer Inc. K53TK ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=f4c1c213-4cf8-455f-a1d4-76311b393c40 ro vesafb.invalid=1 nopat plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1716674] Re: virtualbox crush guest or freeze host screen
It sounds like the app (virtualbox itself) is frozen so reassigning... Also note under gnome-shell a frozen app is difficult to move or resize. This is a feature of Wayland and does not indicate a problem with the shell itself. ** Package changed: gnome-shell (Ubuntu) => virtualbox (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/1716674 Title: virtualbox crush guest or freeze host screen Status in virtualbox package in Ubuntu: New Bug description: Virtualbox: 5.1.26 (ubuntu package) + VirtualBox 5.1.26 Oracle VM VirtualBox Extension Pack Host: ubuntu 17.10 (default gnomelibgnome-desktop-3-12 3.25.91.1-0ubuntu2) 4.12.0-12-generic AMD Ryzen5 1600 Guest: ubuntu 16.04 + guest addition The application window of the running guest will crash. Or the host OS screen is not updated. (The mouse pointer responds.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1716674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716700] Re: "Please sync pulseaudio from debian Buster" where pulseaudio (11.0-1)
Thanks. Yes we are planning on getting 11.0 into Ubuntu 18.04 ... https://trello.com/c/2Cy6kdqt/37-upgrade-to-pulseaudio-110 ** Tags added: pulse11 ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1716700 Title: "Please sync pulseaudio from debian Buster" where pulseaudio (11.0-1) Status in pulseaudio package in Ubuntu: Triaged Bug description: PulseAudio 11.0 release notes Changes at a glance Support for newer AirPlay hardware USB and bluetooth devices preferred over internal sound cards The default sink and source configuration is remembered better Bluetooth HSP headset role implemented Bluetooth HFP audio gateway role implemented (requires oFono) Bluetooth HSP audio gateway and HFP hands-free unit roles can be enabled simultaneously Upmixing can now be disabled without bad side effects Avoid having unavailable sinks or sources as the default Option to avoid resampling more often Option to automatically switch bluetooth profile to HSP more often Better latency regulation in module-loopback Changed module argument names in module-ladspa-sink and module-virtual-surround-sink Fixed input device handling on Windows Improved bluetooth MTU configuration (warning! this causes some hardware to not work any more, see the details below for how to fix it) GNU Hurd support Applications can request LADSPA or virtual surround filtering for their streams Support for 32-bit applications on 64-bit systems in padsp https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1716700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1716415] Re: Alt + Tab then Alt + Right / Left arrow logs me out
On Wed, Sep 13, 2017 at 01:02:14AM -, Daniel van Vugt wrote: > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete Why is this incomplete? I recall it happening during more than one session and it seems like a rather horrible bug to me (although I might be biased). -- Brian Murray -- 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/1716415 Title: Alt + Tab then Alt + Right / Left arrow logs me out Status in gnome-shell package in Ubuntu: Incomplete Bug description: One of my systems if I use Alt + Tab to launch the window switcher and then use Alt + Right or Left arrow to switch windows I either receive a tty or get the gdm lock screen. Neither behavior is what I'd expect - the key stroke moving through the window list. This seems to work on another system of mine and certainly did work on this system (otherwise I wouldn't be using the key stroke) so perhaps a package was updated and I haven't rebooted yet? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 11 07:32:15 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1698 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716813] [NEW] When using vaapi in a wayland session a gl renderer launch icon appears
Public bug reported: Test case: install gstreamer10-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Attachment added: "Screenshot from 2017-09-12 21-32-02.png" https://bugs.launchpad.net/bugs/1716813/+attachment/4949084/+files/Screenshot%20from%202017-09-12%2021-32-02.png ** Also affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears Status in gstreamer-vaapi package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Test case: install gstreamer10-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1716813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716415] Re: Alt + Tab then Alt + Right / Left arrow logs me out
Because in comment #2 suggested you could not reproduce the problem any more. Generally if there's a chance that some update has fixed a bug then the best approach is to set it to incomplete and see if the problem reoccurs in the following 60 days. That way it closes itself rather than adding to the backlog. But if you want it open then no problem. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1716415 Title: Alt + Tab then Alt + Right / Left arrow logs me out Status in gnome-shell package in Ubuntu: New Bug description: One of my systems if I use Alt + Tab to launch the window switcher and then use Alt + Right or Left arrow to switch windows I either receive a tty or get the gdm lock screen. Neither behavior is what I'd expect - the key stroke moving through the window list. This seems to work on another system of mine and certainly did work on this system (otherwise I wouldn't be using the key stroke) so perhaps a package was updated and I haven't rebooted yet? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 11 07:32:15 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1698 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716813] Re: When using vaapi in a wayland session a gl renderer launch icon appears
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => Confirmed -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case: install gstreamer10-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716813] Re: When using vaapi in a wayland session a gl renderer launch icon appears
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer-vaapi (Ubuntu) Status: New => Confirmed -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case: install gstreamer10-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716813] Re: When using vaapi in a wayland session a gl renderer launch icon appears
Confirmed, but I wonder if this is a dock/shell bug. If that OpenGL window is actually the video sub-surface then the shell or dock should ideally recognise it's a child and not list it as an application window. ** Changed in: gstreamer-vaapi (Ubuntu) Importance: Undecided => Low ** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case: install gstreamer1.0-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716813] Re: When using vaapi in a wayland session a gl renderer launch icon appears
** Description changed: Test case: - install gstreamer10-vaapi + install gstreamer1.0-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case: install gstreamer1.0-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716460] Re: Unmet dependencies on 16.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mono-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono-tools in Ubuntu. https://bugs.launchpad.net/bugs/1716460 Title: Unmet dependencies on 16.04 Status in mono-tools package in Ubuntu: Confirmed Bug description: After installing mono-complete in Ubuntu 16.04, trying to install mono-tools-devel shows the following: $ sudo apt install mono-tools-devel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mono-tools-devel : Depends: libmono-cecil-private-cil (< 5.2.0.197) but 5.2.0.215-0xamarin10+ubuntu1604b1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1716460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716813] Re: When using vaapi in a wayland session a gl renderer launch icon appears
I wouldn't have the tech know-how to explore if it's a 'dock/shell bug', I do see 2 things 1. happens with gnome-shell's default dock also (gnome-session 2. See this line which doesn't occur without vaapi totem[2604]: Native Windows taller than 65535 pixels are not supported -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case: install gstreamer1.0-vaapi log into wayland session play a video in totem What happens: A non usable icon appears in launcher Basically harmless but would be better if it didn't show ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 21:34:06 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716707] Re: libreoffice writer crashes on start
The same problem was reported by others: https://askubuntu.com/questions/946624/libreoffice-writer-will-not-open https://askubuntu.com/questions/927859/libreoffice-writer-crashes-on-start The problem persists after I reinstalled libreoffice (remove, install, update, autoremove,upgrade-full). The lowriter command only displays the launch dialog. No error messages are displayed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1716707 Title: libreoffice writer crashes on start Status in libreoffice package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:5.3.1-0ubuntu2 Candidate: 1:5.3.1-0ubuntu2 Version table: *** 1:5.3.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages 100 /var/lib/dpkg/status apt-show-versions -r libreoffice* libreoffice:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-avmedia-backend-gstreamer:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base-core:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-base-drivers:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-calc:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-common:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-core:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-draw:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-gnome:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-gtk3:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-impress:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-java-common:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-librelogo:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-math:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-nlpsolver:all/zesty 0.9+LibO5.3.1-0ubuntu2 uptodate libreoffice-ogltrans:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-pdfimport:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-report-builder:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-report-builder-bin:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-script-provider-bsh:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-script-provider-js:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-script-provider-python:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-sdbc-firebird:i386 not installed libreoffice-sdbc-hsqldb:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-sdbc-postgresql:i386/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-style-breeze:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-style-galaxy:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-style-tango:all/zesty 1:5.3.1-0ubuntu2 uptodate libreoffice-wiki-publisher:all/zesty 1.2.0+LibO5.3.1-0ubuntu2 uptodate libreoffice-writer:i386/zesty 1:5.3.1-0ubuntu2 uptodate 3) What is expected to happen in Writer is . Start libreoffice writer from: - Desktop menu: Office => Libre Office Writer - Filetype association: /.../anyfile.odf or /.../anyfile.doc - from Libre suite => Libre Office Writer The libreoffice writer initial dialog is displayed. After the dialog indicates "100% complete", the dialog closes. Then, the writer application opens a blank document or the selected document. 4) What happened instead is... (All in step 3 above until: After the dialog indicates "100% complete", the dialog closes). But, the writer crashes or fails to start. The writer does not open. There are no error messages or dialogs displayed. The problem does not occur with the other libreoffice applications (suite, base, calc, impress, math). -Version- Kernel: Linux 4.10.0-33-generic (i686) Compiled : #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 C Library : GNU C Library version (Ubuntu GLIBC 2.24-9ubuntu2.2) 2.24 (unstable) Default C Compiler: GNU C Compiler version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) Distribution : Ubuntu 17.04 -Current Session- Desktop Environment : LXDE (Lubuntu) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libreoffice-writer 1:5.3.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 CurrentDesktop: LXDE Date: Tue Sep 12 11:02:21 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (339 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1716707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-package
[Desktop-packages] [Bug 1686573] Re: USB Modem not displayed in network manager
[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: modemmanager (Ubuntu) Status: Incomplete => Expired -- 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/1686573 Title: USB Modem not displayed in network manager Status in modemmanager package in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Status in plasma-nm package in Ubuntu: Expired Bug description: 4G USB WAN modem will not display in network manager, but is fully detected by the kernel and is displayed in ip link journal; Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: new high-speed USB device number 5 using xhci_hcd Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has an invalid interface number: 7 but max is 3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has no interface number 2 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device found, idVendor=1199, idProduct=68a3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Product: AC760S Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Manufacturer: Sierra Wireless, Incorporated Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: SerialNumber: 359822042204515 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.0: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB0 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.1: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB1 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.3: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB2 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwan0: register 'sierra_net' at usb-:00:10.0-2, Sierra Wireless USB-to-WWAN Modem, ce:6b:97:53:02:07 Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: checking bus 5, device 5: "/sys/devices/pci:00/:00:10.0/usb5/5-2" Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: bus: 5, device: 5 was not an MTP device Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwp0s16f0u2i7: renamed from wwan0 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4733] devices added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4734] device added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7) Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB1): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB0): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Creating modem with plugin 'Sierra (legacy)' and '4' ports Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB1): 'Cannot add port 'tty/ttyUSB1', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Modem for device at '/sys/devices/pci:00/:00:10.0/usb5/5-2' successfully created Apr 27 10:57:01 Paul-HP-Laptop ModemManager[846]: Modem: state changed (unknown -> disabled) Apr 27 10:57:01 Paul-HP-Laptop NetworkManager[898]: [1493254621.9962] (ttyUSB2): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0002] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/5) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0043] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0065] device (ttyUSB2): modem state 'enabling' Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0080] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none') [20 30 0] Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling) Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/Mod
[Desktop-packages] [Bug 1686573] Re: USB Modem not displayed in network manager
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1686573 Title: USB Modem not displayed in network manager Status in modemmanager package in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Status in plasma-nm package in Ubuntu: Expired Bug description: 4G USB WAN modem will not display in network manager, but is fully detected by the kernel and is displayed in ip link journal; Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: new high-speed USB device number 5 using xhci_hcd Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has an invalid interface number: 7 but max is 3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has no interface number 2 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device found, idVendor=1199, idProduct=68a3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Product: AC760S Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Manufacturer: Sierra Wireless, Incorporated Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: SerialNumber: 359822042204515 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.0: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB0 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.1: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB1 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.3: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB2 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwan0: register 'sierra_net' at usb-:00:10.0-2, Sierra Wireless USB-to-WWAN Modem, ce:6b:97:53:02:07 Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: checking bus 5, device 5: "/sys/devices/pci:00/:00:10.0/usb5/5-2" Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: bus: 5, device: 5 was not an MTP device Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwp0s16f0u2i7: renamed from wwan0 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4733] devices added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4734] device added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7) Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB1): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB0): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Creating modem with plugin 'Sierra (legacy)' and '4' ports Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB1): 'Cannot add port 'tty/ttyUSB1', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Modem for device at '/sys/devices/pci:00/:00:10.0/usb5/5-2' successfully created Apr 27 10:57:01 Paul-HP-Laptop ModemManager[846]: Modem: state changed (unknown -> disabled) Apr 27 10:57:01 Paul-HP-Laptop NetworkManager[898]: [1493254621.9962] (ttyUSB2): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0002] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/5) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0043] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0065] device (ttyUSB2): modem state 'enabling' Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0080] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none') [20 30 0] Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling) Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedeskt
[Desktop-packages] [Bug 1686573] Re: USB Modem not displayed in network manager
[Expired for plasma-nm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plasma-nm (Ubuntu) Status: Incomplete => Expired -- 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/1686573 Title: USB Modem not displayed in network manager Status in modemmanager package in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Status in plasma-nm package in Ubuntu: Expired Bug description: 4G USB WAN modem will not display in network manager, but is fully detected by the kernel and is displayed in ip link journal; Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: new high-speed USB device number 5 using xhci_hcd Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has an invalid interface number: 7 but max is 3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has no interface number 2 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device found, idVendor=1199, idProduct=68a3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Product: AC760S Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Manufacturer: Sierra Wireless, Incorporated Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: SerialNumber: 359822042204515 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.0: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB0 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.1: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB1 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.3: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB2 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwan0: register 'sierra_net' at usb-:00:10.0-2, Sierra Wireless USB-to-WWAN Modem, ce:6b:97:53:02:07 Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: checking bus 5, device 5: "/sys/devices/pci:00/:00:10.0/usb5/5-2" Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: bus: 5, device: 5 was not an MTP device Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwp0s16f0u2i7: renamed from wwan0 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4733] devices added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4734] device added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7) Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB1): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB0): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Creating modem with plugin 'Sierra (legacy)' and '4' ports Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB1): 'Cannot add port 'tty/ttyUSB1', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Modem for device at '/sys/devices/pci:00/:00:10.0/usb5/5-2' successfully created Apr 27 10:57:01 Paul-HP-Laptop ModemManager[846]: Modem: state changed (unknown -> disabled) Apr 27 10:57:01 Paul-HP-Laptop NetworkManager[898]: [1493254621.9962] (ttyUSB2): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0002] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/5) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0043] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0065] device (ttyUSB2): modem state 'enabling' Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0080] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none') [20 30 0] Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling) Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemMana
[Desktop-packages] [Bug 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display
What desktop are you running? That seems to be an in-shell lock screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1716752 Title: LightDM Bypass - lock screen doesn't resize after adding new display Status in lightdm package in Ubuntu: New Bug description: I'm able to consistently bypass LightDM and access my desktop without a password, simply by plugging in my external monitor. I'm running it on Linux Mint - let me know if this bug is more appropriate for their issue tracker. I made a 1 minute video demonstrating the issue, which might be easier to understand than text. Sorry in advance for filming vertically. https://www.youtube.com/watch?v=EWs_SQJ1-Ak 1) $ lsb_release -rd Description: Linux Mint 18.2 Sonya Release: 18.2 2) $ apt-cache policy lightdm lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) I plugged in my external monitor to my laptop while it was locked. I expected my computer to remain locked even though I had plugged in a new display. 4) The new monitor was not covered by LightDM, allowing me to interact with it. Additionally, parts of my laptop monitor became uncovered. Notes: My laptop display is a 3200x1800 QHD (HiDPI) display when it's standalone but I downscale it to 1600x900 when it has an attached monitor, due to Ubuntu's scaling issues when connecting HiDPI and regular monitors. It's possible that LightDM doesn't think to resize, or resizes incorrectly, when the laptop screen automatically downscales as the new display is attached. I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce 840M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1716752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716821] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1714330 *** https://bugs.launchpad.net/bugs/1714330 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 #1714330, 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/1716821/+attachment/4949098/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1716821/+attachment/4949100/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1716821/+attachment/4949103/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1716821/+attachment/4949104/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1716821/+attachment/4949105/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1716821/+attachment/4949106/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1716821/+attachment/4949107/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714330 gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() ** 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/1716821 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: shell crashed !! ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Sep 13 10:25:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'icon-theme' b"'Papirus'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7efbfd62e836:mov0x1a0(%rax),%rax PC (0x7efbfd62e836) ok source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2 meta_monitor_manager_kms_wait_for_flip () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV 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/1716821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
