[Bug 1762910] Re: The position of audio mute icon doesn't keep alignment to audio on icon
Maybe also shrink the icon so as to ensure it never touches the bar when the bar is visible. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1762910 Title: The position of audio mute icon doesn't keep alignment to audio on icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys
Looks like a fix is coming: https://bugzilla.gnome.org/show_bug.cgi?id=782011 ** Bug watch added: GNOME Bug Tracker #782011 https://bugzilla.gnome.org/show_bug.cgi?id=782011 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=782011 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1692394 Title: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1692394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762910] Re: The position of audio mute icon doesn't keep alignment to audio on icon
To avoid any odd-looking padding I think the solution would be to enforce the OSD to stay as a square always, and just optionally paint the bar over the top (possibly with a border to avoid conflicting with some/future icons). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1762910 Title: The position of audio mute icon doesn't keep alignment to audio on icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
We know. There are 830 reports of this crash from 18.04 right now: https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c And globally this is the 9th most common gnome-shell crash for 18.04 (or 6th if you look at just the past month). ** Changed in: gnome-shell (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-09 (150 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.28.1-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-28 (11 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1759621/+attachment/5136525/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1759621/+attachment/5136526/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1759621/+attachment/5136524/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1759621/+attachment/5136523/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
Sadly this is still happening to me on 18.04 as well. Every single time I resume my machine from suspend. And it's not just that gnome-shell crashes, but I have to sit for a good 2-3 minutes while apport does its thing, while the machine is completely frozen from a UI perspective. This is such a huge usability issue! I still suspect it is being caused by some particular combination of gnome-shell extensions that are installed. I've tried (unsuccessfully) to pin down which one it is, but it never seems to work, leading me to believe it must be a combination. I've attached my journalctl output, captured from the moment I resumed my machine. Really hope we can get to the bottom of this! ** Attachment added: "journalctl-gnome-shell.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+attachment/5136522/+files/journalctl-gnome-shell.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 716280] Re: gvfsd-metadata process pegs CPU while nautilus waits
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/716280 Title: gvfsd-metadata process pegs CPU while nautilus waits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/716280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754674] Re: nautilus crashes on unzip attempt
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754674 Title: nautilus crashes on unzip attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
Please try to only report one issue per bug report. The first issue you report is in an area that has been bugging me for a few years too (see bug 1607677). Please reword the bug title and description to just be about that first issue. The second issue you report is possibly bug 1759300. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769845 Title: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1769845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769969] Re: GDM3 does not start if SDDM is installed (18.04)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1769969 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: sddm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769969 Title: GDM3 does not start if SDDM is installed (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby
See also related bugs: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=unlock ** Tags added: unlock -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769981 Title: Temporary screen freeze when coming back from screen standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed
*** This bug is a duplicate of bug 1723615 *** https://bugs.launchpad.net/bugs/1723615 Thanks. Let's track this in bug 1723615 then. If you find more crash files then please continue to report them using 'ubuntu-bug' and the robots will hopefully be able to analyse those and tell you what each one is. ** This bug has been marked a duplicate of bug 1723615 gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769720 Title: Logged out when unplugging external monitors with screen locked and lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768993] Re: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot
No problem. This bug is now closed. Anyone else who has problems can open a new bug. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1768993 Title: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1422253/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
There's probably no way GDM could cause this directly. But indirectly if you are logging into a Wayland session in one case and Xorg in the other, then that might be the main factor here. Please try logging into both Xorg and Wayland sessions to see if one works better. Also, for Nvidia there used to be settings to control tearing in the nvidia control panel. So you shouldn't need to "To get rid of tearing I added nvidia-drm.modeset=1"...? ** Changed in: gdm3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
I upgraded from Ubuntu 17.10 to 18.04 and all was fine for a couple weeks. I think an update yesterday (5/7) caused the problem. I have two accounts on the system. I can initially log into either fine but switching to the other causes the purple screen with cursor only. It does not matter if I log out of the first account or switch user, either way I have the problem. The password seems to be accepted fine. It seems that the windows don't start or start correctly. I'm using an HP dv7-2043cl Notebook -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
Your bug report appears to be from Ubuntu 17.10. Please consider upgrading to Ubuntu 18.04 LTS. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769845 Title: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769372] Re: Prompt the user when the power button is pressed on a VM
OK, as is the pattern this week, the confusion here is the intersection of two different bugs. Not one. My gitlab merge request solves a different problem to this bug. ** Summary changed: - Prompt the user when the power button is pressed + Prompt the user when the power button is pressed on a VM ** Changed in: gnome-control-center (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1769372 Title: Prompt the user when the power button is pressed on a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1769372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
No, that 'area' setting doesn't work on my touchpad for some reason. A alternative i found at https://askubuntu.com/questions/881939/libinput- how-to-map-different-tappings-to-buttons-tappingbuttonmap-has-no-effe/ does something useful that i'd like to be a setting in the future, exchange the 'double finger tap' by the 'triple finger tap' that is double finger tap is mouse 3. Unfortunately i also can't make it work. I suspect my driver is always being set to synaptics. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769845 Title: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768258] Re: Intermittend black screen - after login on bootup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1768258 Title: Intermittend black screen - after login on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...
Hello Frank, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Artful) Status: New => Won't Fix ** Changed in: nplan (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1756322 Title: 'netplan apply' fails when trying to activate another interface on another QETH device ... To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1756322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro
I've a proposed fix at
https://gitlab.gnome.org/3v1n0/mutter/commit/993a40c9a4e161e40faa0467f98eadd1ac50dd22
I'm discussing with upstream about it.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1422253/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
It could be that fixing this would also fixes lp:1703300 https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Changed in: gdm3 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769224] Re: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769224 Title: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1769224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768993] Re: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot
@Daniel Unfortunately I am unable to reproduce the bug anymore. Something I did above fixed the error. I have both gdm3 and sddm installed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1768993 Title: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769982] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
*** This bug is a duplicate of bug 1723615 *** https://bugs.launchpad.net/bugs/1723615 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 #1723615, 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/1769982/+attachment/5136315/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1769982/+attachment/5136317/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1769982/+attachment/5136322/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1769982/+attachment/5136323/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1769982/+attachment/5136324/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1769982/+attachment/5136325/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1769982/+attachment/5136326/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1723615 gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769982 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769982/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769991] [NEW] [16.04] Unable to import OpenVPN configuration into Network Manager
Public bug reported: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- - An example configuration that fails to import is as follows: + An example configuration that fails to import is as follows (with some + critical components excluded, like a proper remote address, or a proper + x509 name): client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite - remote ipaddr 8443 tcp + remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper - x509 name): + x509 name); this is a config that otherwise works with a Sophos XG + Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend.
[Bug 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed
Note that there are crashes around the same time in /usr/lib/hidpi- daemon/hidpi-daemon and /usr/lib/hidpi-daemon/hidpi-notification, which are provided by System76, but looking at the dumps in /var/crash for them, it looks like they are crashing _as a result of_ the gnome-shell crash, as opposed to because of it. The hidpi-daemon crash says this: GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4) which I _think_ means it was trying to message gnome-shell and failed because the shell had crashed. And the hidpi-notification crash says this: Title: hidpi-notification crashed with GLib.GError in get(): g-dbus- error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.system76.hidpi was not provided by any .service files (2) which I think means that it crashed because hidpi-daemon crashed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769720 Title: Logged out when unplugging external monitors with screen locked and lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Sure, here it is. ** Attachment added: "apt-clone_system_state.tar.gz" https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+attachment/5136348/+files/apt-clone_system_state.tar.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769954 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769720] Re: Logged out when unplugging external monitors with screen locked and lid closed
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769982 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769720 Title: Logged out when unplugging external monitors with screen locked and lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769981] [NEW] Temporary screen freeze when coming back from screen standby
Public bug reported: When waking up the PC screen from standby, quite often the screen freezes for 10-20s. I can't move the mouse or type anything. After a while, it unfreezes. This is quite annoying because often the freeze is long enough to send the screen to standby again for absence of singal, so then I have to wake it up and wait again. This is not 100% reproducible but happens very frequently, both when the screen is locked and when it's not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 8 20:26:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-25 (72 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769981 Title: Temporary screen freeze when coming back from screen standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Do you happen to have and could you provide us with the following file from the system? /var/log/dist-upgrade/apt-clone_system_state.tar.gz Thanks in advance. ** Changed in: desktop-file-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769954 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Changed in: gdm Status: Unknown => Confirmed ** Changed in: gdm Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768993] Re: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot
I found out that gdm3 will not start if sddm is installed. As the reporter is using KDE too, this might be the problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1768993 Title: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769969] [NEW] GDM3 does not start if SDDM is installed (18.04)
Public bug reported: After upgrading my office machines to 18.04, some machines did not start the GDM3. After some testing the problem was that the ones that it did not work, had SDDM installed too (KDE environment in those machines). The upgrade were from 17.10 and 16.04. Note that reistalling sddm, gdm3, lightdm, dpkg-reconfigure gdm3, none worked. On gdm3 side: systemctl is-active gdm3 reports static (which might be the problem). After removing sddm and rebooting, everything worked as expected. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769969 Title: GDM3 does not start if SDDM is installed (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769224] Re: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04)
This is correct, both keyboards appear in /etc/default/keyboard. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769224 Title: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1769224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Bug watch added: GNOME Bug Tracker #795940 https://bugzilla.gnome.org/show_bug.cgi?id=795940 ** Changed in: gdm Importance: Undecided => Unknown ** Changed in: gdm Status: New => Unknown ** Changed in: gdm Remote watch: None => GNOME Bug Tracker #795940 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767817] Re: Full text search does not work
I have the same problem. Does also not work with the nautilus version from flathub. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769954 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769954] [NEW] package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: desktop-file-utils 0.23-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Tue May 8 16:59:12 2018 Ec2AMI: ami-70873908 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t2.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: dependency problems - leaving triggers unprocessed Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago) ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ec2-images -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769954 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom
I'm thinking that Multi-Arch: foreign on the transitional package libp11 -kit-gnome-keyring might help. If someone wants to verify that, please do, otherwise I'll try tomorrow. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1768541 Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1543345] Re: nautilus ignores the --geometry= positions unless sudo is used
For nautilus, neither position nor size works for either user or sudo in the Ubuntu 18.04 release, nautilus package 1:3.26.3-0ubuntu4. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1543345 Title: nautilus ignores the --geometry= positions unless sudo is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1543345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom
Pretty sure at least I did at several points in the past. Not sure they were active at the time of the report, though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1768541 Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom
Anyone affected - were you using any PPAs? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1768541 Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
** Description changed: + Lenovo ideapad 510-15IKB OS: Ubuntu 18.04 bionic Kernel: x86_64 Linux 4.15.0-20-generic DE: GNOME CPU: Intel Core i5-7200U @ 4x 3.1GHz GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus) UEFI boot, Secure Boot disabled. I installed the proprietary graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. Everything works as expected if lightdm is used instead of gdm3. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732002] Re: cloud images in lxc get ipv6 address
This got landed in netplan.io 0.35 in bionic. The changes still should be part of a SRU. ** Changed in: nplan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732002 Title: cloud images in lxc get ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769224] Re: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04)
On 2018-05-08 09:25, Bodinux wrote: > In my case, the two layouts are correctly available for choice. Then I suppose they are both included in the file /etc/default/keyboard. > When this happens with bugs#1766137, it makes 18.04 not usable for a > family computer. (error on the password leading to a blank screen). Right, but bug #1766137 is being worked on. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769224 Title: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1769224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652404] Re: .desktop file fails with unhelpful error message "The was an error launching the application"
* https://gitlab.gnome.org/GNOME/nautilus/issues/357#note_114616 Where the Files developer says: 'How can we make the error message more helpful in such a case?' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1652404 Title: .desktop file fails with unhelpful error message "The was an error launching the application" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1652404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652404] Re: .desktop file fails with unhelpful error message "The was an error launching the application"
Karl (or anyone else wanting this bug fixed) can you answer this question on GitLab please? Otherwise this bug may not be fixed: https://gitlab.gnome.org/GNOME/nautilus/issues/357 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1652404 Title: .desktop file fails with unhelpful error message "The was an error launching the application" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1652404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769677] Re: gnome-software reads system proxy settings in a wrong way
** Description changed: After setting a proxy (e.g. http proxy) in Settings, gnome-software will show a message saying something like `E: https://mirrors.ustc.edu.cn/ubuntu bionic/universe amd64 libkf5archive5 amd64 5.44.0-0ubuntu1 is not (yet) available (Unsupported proxy configured: 127.0.0.1://1234)` when attempt to install software (not a snap package). That is to say, - it parse the domain part as the protocol part, which is incorrect. + it parses the domain part as the protocol part, which is incorrect. - The proxy settings it shows seems to come from the system proxy settings + The proxy settings it shows seem to come from the system proxy settings as it shows 13:59:45:0380 GsPluginPackageKit Setting proxies (http: 127.0.0.1:1234, https: (null), ftp: (null), socks: (null), no_proxy: localhost,127.0.0.0/8,::1, pac: (null)) in `gnome-software --verbose`. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1769677 Title: gnome-software reads system proxy settings in a wrong way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1769677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
For your middle click and right click issues, please see the Mouse Click Emulation section in GNOME Tweaks > Mouse & Touchpad. Does setting that to Area do what you expect? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769845 Title: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769509] Re: package libp11-kit-gnome-keyring 3.28.0.2-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gn
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1769509 Title: package libp11-kit-gnome-keyring 3.28.0.2-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1769509/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set (Optimus)
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Description changed: OS: Ubuntu 18.04 bionic Kernel: x86_64 Linux 4.15.0-20-generic - DE: GNOME + DE: GNOME CPU: Intel Core i5-7200U @ 4x 3.1GHz GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus) UEFI boot, Secure Boot disabled. I installed the proprietary graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. - Other GNU/Linux distributions such as Manjaro don't seem to be affected - which is why I'm reporting this here. + Everything works fine if lightdm is used instead of gdm3. ** Summary changed: - Vulkan not working if nvidia-drm.modeset=1 is set (Optimus) + Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) ** Description changed: OS: Ubuntu 18.04 bionic Kernel: x86_64 Linux 4.15.0-20-generic DE: GNOME CPU: Intel Core i5-7200U @ 4x 3.1GHz GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus) UEFI boot, Secure Boot disabled. I installed the proprietary graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. - Everything works fine if lightdm is used instead of gdm3. + Everything works as expected if lightdm is used instead of gdm3. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
@Wouter Last one is excellent find: I also noticed that sometimes my suspend leads to complete laptop freeze and force power off is necessary. Now you made realize it has to to with gnome-settings: I can only use suspend if I did not start gnome-settings before, even though it is not running when I try to suspend. Note to myself: never use suspend after you used gnome-settings -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
An additional note is that this also seems to occur when I unlock my notebook and the settings is not yet open (but I used it before locking it). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
Also having this issue on my Acer aspire v3-772g with clean install on 18.04, although - no nvidia driver(s) installed. Really a clean install. I tried installing the nvidia driver, but then I came across a different issue, which seems to be related to bug #1752053. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
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 Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
Mmm. I used 'xev' as per this link: https://wiki.archlinux.org/index.php/Libinput#Manual_button_re-mapping to find which buttons are triggering o keypad interactions. Sadly, apparently taps to the touchpad 'column' are are not even recognized (or double taps). I recognizes scroll down (5) and scroll up (4) as buttons but it appears be impossible at this level. Maybe i was hallucinating using that area as 3rd mouse button previously? It also recognizes single tap on the central area to button 1 (same as left mouse button), and double tap to button 3 (same as right mouse button). Very very very occasionally (like once every 30 times) it recognizes a triple tap as 2 (middle mouse) instead of (3) right click. When it doesn't disastrously move the pointer. I'm wondering if i can use 'xinput set-button-map' to reassign the central area double tap for button 2 and leave the actual physical button right as button 3. Probably will change both with my luck and i'll not be able to right click. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769845 Title: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760486] Re: Desktop icons under dock when auto-hide on
*** This bug is a duplicate of bug 1723117 *** https://bugs.launchpad.net/bugs/1723117 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1760486 Title: Desktop icons under dock when auto-hide on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769845] [NEW] The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
Public bug reported: First, the obvious: the mouse experience out of the box (at least on ubuntu 17.04) is bad. I thought this was because Wayland is slightly slower on animations + mouse movement but although this is happening for some reason (memory leak, whatever) it's mostly because the setting to set the mouse 'Acceleration Profile' to 'adaptive' is hidden in the gnome-tweak tool and set to default 'linear'. I highly suspect that this setting was on by default on X11 synaptics, because my mouse experience became equal after i turned it to adaptive when it was inferior before. This is probably the cause of many of the mouse complaints on the ubuntu upgrade. Another problem. Previously, on Xorg and synaptics i could use the right border area of my touchpad to simulate a middle mouse button click (that button doesn't exist on my keypad that has a structure like this: (imagine # is non-breaking spaces here because i sure can't make them work here) --- |###|#| |###|#| |###|#| |###|#| |###|#| |###|#| |###|#| --- |##|##| --- (i have a acer aspire 5738 if you want to see images on google) The bottom are the left and right mouse buttons, the right column was for scrolling (another bug: doesn't actually work on nautilus at the moment but works on Firefox). Previously taps on that scroll area could open firefox links, open tabs in nautilus etc, as per 3rd mouse button. Now that whole area only does scrolling and i have to try the lottery of trying the 'three finger tap' on the central are to simulate mouse click (this doesn't work 80% of the time, and the other 15% is right clicking, that's two fingers. Even if it works, 3 fingers probably meanwhile moved the cursor when i lifted or tapped). I'd *really really* like it if i could configure those areas somehow, either graphically or on a config file. Meanwhile i'm using ctrl+tap or ctrl+click but that requires two hands. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 8 09:26:49 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-25 (590 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-05-06 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session ** Description changed: First, the obvious: the mouse experience out of the box (at least on ubuntu 17.04) is bad. I thought this was because Wayland i slightly slower on animations + mouse movement but although this is happening for some reason (memory leak, whatever) it's mostly because the setting to set the mouse 'Acceleration Profile' to 'adaptive' is hidden in the gnome-tweak tool. I highly suspect that this setting was on by default on X11 synaptics, because my mouse experience because equal after i turned it to adaptive when it was inferior before. This is probably the cause of many of the mouse complaints on the ubuntu upgrade. Another problem. Previously, on Xorg and synaptics i could use the right border area of my touchpad to simulate a middle mouse button click (that button doesn't exist on my keypad that has a structure like this: --- - | | | + | | | | | | | | | | | | | | | | | | | | | --- | | | --- The bottom are has the left and right mouse buttons, the right column was for scrolling (another bug: doesn't actually work on nautilus at the moment but works on Firefox). Previously taps on that scroll area could open firefox links, open tabs in nautilus etc, as per 3rd mouse button. Now that whole area only does scrolling and i have to try the lottery of trying the 'three finger tap' on the central are to simulate mouse click (this doesn't work 80% of the time, and the other 15% is right clicking, that's two fingers. Even if it works, 3 fingers probably meanwhile moved the cursor when i lifted or tapped). I'd *really really* like it if i could configure those areas somehow, either graphically or on a config file. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64
[Bug 1764944] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1679903 *** https://bugs.launchpad.net/bugs/1679903 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1764944 Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1764944/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768786] Re: Screen is displayed when resuming from suspend
Added to Trello: https://trello.com/c/3CWvCfPV/1-bug1768786-screen-is- displayed-when-resuming-from-suspend -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1768786 Title: Screen is displayed when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1543345] Re: nautilus ignores the --geometry= positions unless sudo is used
I have the same problem (I can't tell whether it would work with sudo, though). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1543345 Title: nautilus ignores the --geometry= positions unless sudo is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1543345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
Please report this bug to the Gnome developers here: https://gitlab.gnome.org/GNOME/mutter/issues -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721248/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
Done some more test: the problem seems restricted to Intel HD Graphics 620 used by Luca Ciavatta https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204 and my Intel HD Graphics 630. I still have the problem on Ubuntu 18.10: corrado@corrado-p9-cc-0506:~$ inxi -SCGx System:Host: corrado-p9-cc-0506 Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Gnome 3.28.1 Distro: Ubuntu Cosmic CANIMAL (development branch) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Skylake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 802 4: 800 Graphics: Card-1: Intel HD Graphics 630 driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.19.6 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.0.2 direct render: Yes corrado@corrado-p9-cc-0506:~$ apt policy totem totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p9-cc-0506:~$ apt policy gstreamer1.0-vaapi gstreamer1.0-vaapi: Installed: 1.14.0-1 Candidate: 1.14.0-1 Version table: *** 1.14.0-1 500 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p9-cc-0506:~$ BUT NO PROBLEM WITH A DIFFERENT HARDWARE: mao@mao-p3:~$ inxi -SCGx System:Host: mao-p3 Kernel: 4.13.0-39-generic x86_64 bits: 64 gcc: 7.2.0 Desktop: Gnome 3.26.2 (Gtk 3.22.25-0ubuntu0.1) Distro: Ubuntu 17.10 CPU: Dual core Intel Core i3-4130 (-HT-MCP-) arch: Haswell rev.3 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13568 clock speeds: max: 3400 MHz 1: 898 MHz 2: 1335 MHz 3: 1334 MHz 4: 1300 MHz Graphics: Card: Intel 4th Generation Core Integrated Graphics Controller bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.5 ) driver: i915 Resolution: 1680x1050@59.88hz OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa 17.2.8 Direct Render: Yes mao@mao-p3:~$ apt policy totem totem: Installed: 3.26.0-0ubuntu1 Candidate: 3.26.0-0ubuntu1 Version table: *** 3.26.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status mao@mao-p3:~$ apt policy gstreamer1.0-vaapi gstreamer1.0-vaapi: Installed: 1.12.3-1ubuntu1 Candidate: 1.12.3-1ubuntu1 Version table: *** 1.12.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status mao@mao-p3:~$ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721248/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760905] Re: nautilus does not start at all
@seb128 @SebastienBacher Thanks Deleting that file helped. :-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1760905 Title: nautilus does not start at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1760905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760905] Re: nautilus does not start at all
@seb128 @SebastienBacher Thanks Deleting that file helped. :-) ** Changed in: nautilus (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1760905 Title: nautilus does not start at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1760905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769224] Re: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04)
In my case, the two layouts are correctly available for choice. So that part is OK. Indeed as per the comment you quote : It may be motivated to ask upstream why they don't make use of the information provided by accountsservice in the same way as unity-greeter does. When this happens with bugs#1766137, it makes 18.04 not usable for a family computer. (error on the password leading to a blank screen). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769224 Title: keyboard layout on greeter is not stored per user (function lost from 16.04 to 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1769224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769834] [NEW] WLAN Adapter RTL 8821AU not recognized
Public bug reported: This Adapter works well under Windows 10 (64 Bit) but is not recognized by the Ubuntu 18.04 Desktop OS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 8 09:04:39 2018 InstallationDate: Installed on 2018-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1769834 Title: WLAN Adapter RTL 8821AU not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1769834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767693] Re: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz
** Tags removed: 18.04 ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767693 Title: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1767693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723080] Re: Caldav Issues with evolution 3.26
I have a suspicion that I cannot verify, though. It might be that the new version of evolution is not backward compatible with older caldav specifications. I stopped using evolution and use Thunderbird and Lightning. There are some glitches but overall it works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1723080 Title: Caldav Issues with evolution 3.26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1723080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
