[Bug 1721658] Re: Unintuitive dialogue when setting resolution
https://bugzilla.gnome.org/show_bug.cgi?id=788630 ** Bug watch added: GNOME Bug Tracker #788630 https://bugzilla.gnome.org/show_bug.cgi?id=788630 -- 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/1721658 Title: Unintuitive dialogue when setting resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1721658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721947] Re: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver()
*** This bug is a duplicate of bug 1701843 *** https://bugs.launchpad.net/bugs/1701843 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 #1701843, 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/1721947/+attachment/4964319/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1721947/+attachment/4964321/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1721947/+attachment/4964328/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1721947/+attachment/4964329/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1721947/+attachment/4964330/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1721947/+attachment/4964332/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1721947/+attachment/4964333/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1701843 ** 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-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1721947 Title: gnome-screensaver crashed with SIGSEGV in XGetScreenSaver() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1721947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721949] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1556601 *** https://bugs.launchpad.net/bugs/1556601 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 #1556601, 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/1721949/+attachment/4964340/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1721949/+attachment/4964342/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1721949/+attachment/4964345/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1721949/+attachment/4964346/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1721949/+attachment/4964347/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1721949/+attachment/4964348/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1721949/+attachment/4964349/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1556601 gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1721949 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720760] Re: Under Xorg app windows unscaled until gnome tweaks is launched.
Seems to have gone away with recent upgrades. I can't tell exactly which as I was attempting to use wayland under amd and even under nvidia-387 (which worked fine except for a couple of random system freezes during closing windows). Back on nvidia/xorg because of that (although not exhaustively tested that *that* isn't still going to happen), and the scaling problem appears to have resolved. Guessing that was fixed upstream in 3.26.1. mutter version 3.26.1-1 gnome-shell 3.26.1-0ubuntu1 nvidia-387 387.12-0ubuntu0~gpu17.10.1 from graphics-drivers/ppa There were problems *selecting* 200% scaling in this environment with two monitors. I had to try several times before it took, but it did eventually. That'll be a different bug though. -- 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/1720760 Title: Under Xorg app windows unscaled until gnome tweaks is launched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 237967] Re: control-q should quit
I read up on this one on the link provided. If Ctrl q is not allocated, it should be easy to close the current version. Surely you have a linux build. It is very standard to have ctrl Q not ctrl W -- 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/237967 Title: control-q should quit To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/237967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 237967] Re: control-q should quit
I read up on this one on the link provided. If Ctrl q is not allocated, it should be easy to close the current version. Surely you have a linux build. It is very standard to have ctrl Q not ctrl W -- 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/237967 Title: control-q should quit To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/237967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718453] Re: Cannot install steam on a clean 16.04.3 machine
After trying to install it gives me: Running Steam on ubuntu 16.04 64-bit STEAM_RUNTIME is enabled automatically Installing breakpad exception handler for appid(steam)/version(0) libGL error: unable to load driver: r600_dri.so libGL error: driver pointer missing libGL error: failed to load driver: r600 libGL error: unable to load driver: r600_dri.so libGL error: driver pointer missing libGL error: failed to load driver: r600 libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast in terminal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1718453 Title: Cannot install steam on a clean 16.04.3 machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1718453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721963] [NEW] No mouse cursor on Wayland when Universal Access > Zoom is selected
Public bug reported: Using default login on 17.10 Beta, which I believe is Wayland, when Universal Access > Zoom is selected the mouse cursor disappears. The mouse continues to function, but no cursor is visible. It is ok when used with X login. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 15:33:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2017-10-03 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171003) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1721963 Title: No mouse cursor on Wayland when Universal Access > Zoom is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721963/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722000] Re: gnome shell crashes after display config is changed to only show on a secondary monitor
** Attachment added: "After" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+attachment/4964664/+files/after.png -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722000] Re: gnome shell crashes after display config is changed to only show on a secondary monitor
This used to work before recent a update of several distro packages. Currently settings are not applied and everything falls back to "Join displays" instead of "Single Display" -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722000] [NEW] gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 00007f22c7bdf877 sp 00007ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000])
Public bug reported: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "before-applying.png" https://bugs.launchpad.net/bugs/1722000/+attachment/4964658/+files/before-applying.png -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722000] Re: gnome shell crashes after display config is changed to only show on a secondary monitor
This used to work before recent a update of several distro packages. Currently settings are not applied and everything falls back to "Join displays" instead of "Single Display". --- After debugging that a little bit more I can see that the bug is not triggered if I do not change scaling from 100% to 200% at the same time. The primary laptop display goes offline and I only have a secondary running. If I try to go from "Scaling: 100%" to 200%, I immediately get the problematic behavior. ➜ ~ echo $XDG_SESSION_DESKTOP ubuntu-xorg This is what goes to syslog right after I press a button to change scaling to 200%. http://paste.ubuntu.com/25694579/ ** Summary changed: - gnome shell crashes after display config is changed to only show on a secondary monitor + gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722003] [NEW] Some free (gratis) packages require logging in with a Snap Store account
Public bug reported: https://i.redd.it/ellp7c7yggqz.png Some free (gratis) packages require logging in with a Snap Store account in Ubuntu/GNOME Software. This is, quite frankly, ridiculous. I should not need an account to install any software. Neither should anyone else. These packages are available via package managers with no account required, therefore the GUI front end, this Ubuntu/GNOME Software app, should not require an account either. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1722003 Title: Some free (gratis) packages require logging in with a Snap Store account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1722003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722002] [NEW] Ignore the "region" gsettings value
Public bug reported: The /usr/bin/gnome-session wrapper sets some LC_* variables based on the "region" gsettings value. Since we rely on ~/.pam_environment for those variables, setting them from /usr/bin/gnome-session is redundant, and may occasionally cause unexpected behavior. ** Affects: gnome-session (Ubuntu) Importance: Medium Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1722002 Title: Ignore the "region" gsettings value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1722002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722001] [NEW] "Launch" button does not always work
Public bug reported: Video demonstration: https://www.youtube.com/watch?v=Sbn-02k_n9E The "Launch" button in Ubuntu/GNOME Software does not always work. Launching the same program from the GNOME interface or the Terminal works fine. Tested on Ubuntu 17.10 64-bit Beta2 Artful Aardvark. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1722001 Title: "Launch" button does not always work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1722001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720438] Re: brightness control broken nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-power-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722004] [NEW] Lock screen cover can't be dismissed with a double-click
Public bug reported: Demonstration: https://www.youtube.com/watch?v=gIUq196KnVg The lock screen cover can't be dismissed with a double-click or double- tap. The only methods to dismiss it is by pressing a keyboard key or dragging the mouse up while holding click, the latter of which is unintuitive for desktops. As is intuitive, and as other products have done, such as Windows 10 and LG phones, the cover should be dismissable with a double-click or a double-tap of the screen. This should be given Wishlist priority. Tested on Ubuntu 17.10 64-bit Beta2 Artful Aardvark. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1722004 Title: Lock screen cover can't be dismissed with a double-click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1722004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720438] Re: brightness control broken nvidia
@brinstar, yes I did the sudo update-grub part, and tried acpi_brightness=[native|vendor] which for me makes the Fn hot keys not working (when you press them, no brightness icon appears). Last update brought in NVidia drivers 384.90, but no joy, the problem is still present. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722005] [NEW] Image-heavy PDF no longer displays
Public bug reported: The PDF from https://archive.org/details/kamikiukulelemet00newy displayed fine under zesty, but under artful it shows up as lots of blank white pages. This is the same under other PDF viewers, so I suspect the real bug is in one of the shared libraries used by all of them. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 20:53:07 2017 InstallationDate: Installed on 2014-05-29 (1227 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-07 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1722005 Title: Image-heavy PDF no longer displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1722005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722005] Re: Image-heavy PDF no longer displays
Interestingly the .djvu file of the same images from the torrent works smoothly and without incident. the PDF claims to be a PDF/A of some variety, so I'd have assumed it was less complicated a dataset than most! -- 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/1722005 Title: Image-heavy PDF no longer displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1722005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 139393] Re: evolution filters must be specific for mailboxes
** Changed in: evolution Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/139393 Title: evolution filters must be specific for mailboxes To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/139393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720438] Re: brightness control broken nvidia
I tried also: sudo su -c 'echo 10 > /sys/class/backlight/acpi_video0/brightness'. Pressing the Fn keys brings up the OSD brightness control, which reflects the value of the /sys/class/backlight/acpi_video0/brightness file (and viceversa), but the actual screen brightness does not change. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712011] Re: Unable to close Printer properties
** Changed in: gtk Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1712011 Title: Unable to close Printer properties To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1712011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722002] Re: Ignore the "region" gsettings value
** Branch linked: lp:~gunnarhj/gnome-session/lp1722002 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1722002 Title: Ignore the "region" gsettings value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1722002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722009] Re: gnome-shell crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1701289 *** https://bugs.launchpad.net/bugs/1701289 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 #1701289, 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/1722009/+attachment/4964699/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1722009/+attachment/4964701/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1722009/+attachment/4964705/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1722009/+attachment/4964706/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1722009/+attachment/4964707/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1722009/+attachment/4964708/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1722009/+attachment/4964709/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1701289 gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat() ** 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/1722009 Title: gnome-shell crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722010] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1721064 *** https://bugs.launchpad.net/bugs/1721064 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 #1721064, 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/1722010/+attachment/4964711/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1722010/+attachment/4964713/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1722010/+attachment/4964717/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1722010/+attachment/4964718/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1722010/+attachment/4964719/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1722010/+attachment/4964720/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1722010/+attachment/4964721/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1721064 gnome-control-center crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1722010 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721064] Re: gnome-control-center crashed with SIGSEGV
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/1721064 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1721064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722011] Re: gnome-calendar crashed with SIGSEGV in gtk_widget_queue_draw()
*** This bug is a duplicate of bug 1702473 *** https://bugs.launchpad.net/bugs/1702473 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 #1702473, 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/1722011/+attachment/4964723/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1722011/+attachment/4964725/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1722011/+attachment/4964729/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1722011/+attachment/4964730/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1722011/+attachment/4964731/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1722011/+attachment/4964732/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1722011/+attachment/4964733/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1702473 ** 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-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1722011 Title: gnome-calendar crashed with SIGSEGV in gtk_widget_queue_draw() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1722011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1581713] Re: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package
How long until this fix is pushed downstream to Ubuntu and GNOME Software? The issue is present in Ubuntu 17.10 64-bit Beta 2 Artful Aardvark. -- 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/1581713 Title: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1581713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722025] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1722024 *** https://bugs.launchpad.net/bugs/1722024 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 #1722024, 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/1722025/+attachment/4964777/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1722025/+attachment/4964779/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1722025/+attachment/4964784/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1722025/+attachment/4964785/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1722025/+attachment/4964786/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1722025/+attachment/4964787/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1722025/+attachment/4964788/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1722024 ** 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/1722025 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1021375] Re: Nautilus says the USB stick is read only when it is not
On Latest 17.04, killall nautilus and restarting nautilus doesn't help. Maybe I am not doing the right thing in detail. So for a couple of years now, every time I present something at a conference, I panic because I'm not going to be able to write my PDF file on a USB key in order to share it -- thanks to this bug. This is nutty. -- 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/1021375 Title: Nautilus says the USB stick is read only when it is not To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722028] [NEW] nautilus dead when renaming folder after creating folder
Public bug reported: Hello! This record is for bug evidence in ubuntu 17.04 nautilus 3.20.4 Please check this bug. Bug occur when renaming folder in korean after creating folder! May be unicode bug... https://youtu.be/G_FcGdn20eE My computer using ubuntu 17.04 i5-6200u ram 4gb cybertr...@nate.com 17.10.08 ** Affects: nautilus (Ubuntu) Importance: Undecided Assignee: greendot (greendot) Status: New ** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => greendot (greendot) ** Description changed: Hello! This record is for bug evidence in ubuntu 17.04 nautilus 3.20.4 Please check this bug. - Bug occur when renaming folder after creating folder! + Bug occur when renaming folder in korean after creating folder! May be unicode bug... https://youtu.be/G_FcGdn20eE - My computer using ubuntu 17.04 i5-6200u ram 4gb cybertr...@nate.com 17.10.08 -- 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/1722028 Title: nautilus dead when renaming folder after creating folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1722028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652618] Re: Impossible to unlock the screen when using non-English language
Hi, this issue is reproduced on my 17.04 system with lightdm display manager. -- 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/1652618 Title: Impossible to unlock the screen when using non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1652618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
