[Bug 1728474] Re: ctrl-alt-f1 closes all running programs
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1728474 Title: ctrl-alt-f1 closes all running programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C
Hi, Thanks for the tips here, I managed to get keyboard backlight working on Kubuntu 17.04 with my NP900X3J - Samsung Style S50 (the key to change it still doesnt works, and requires a reboot). I have to adapt what Kieran said, what I did was: # cd /sys/firmware/efi/efivars # xxd -p KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 070004 # lsattr KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 i-- KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 # chattr -i KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 # lsattr KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 --- KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 # echo 070004 | xxd -p -r > KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 # xxd -p KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 070004 # chattr +i KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 # xxd -p KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852 070004 # sudo reboot And it started to work with ambient light sensor. thanks! -- 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/1203592 Title: Keyboard backlight does not work in Samsung Series 9 NP900X4C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739980] Re: Depends libpopper68 version 0.57.0-2ubuntu4 but only 0.57.0-2ubuntu4.1 is available
Your theory appears to have been correct. libpoppler68 is now appearing as version 0.57.0-2ubuntu4 Apologies if the bug was unnecessary. I didn't realize this scenario could occur in the archives. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1739980 Title: Depends libpopper68 version 0.57.0-2ubuntu4 but only 0.57.0-2ubuntu4.1 is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1739980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1623792] Re: possible sigbus
The fix was released in version 4.2.0 last year and is available in Ubuntu since Zesty. ** Changed in: zeromq3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1623792 Title: possible sigbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1623792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718253] Re: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial
libzmq5-dev is a virtual package. libzmq5 is the correct dependency, and it is in Xenial: https://packages.ubuntu.com/xenial/libzmq5 ** Changed in: zeromq3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1718253 Title: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1718253/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722034] Re: org.gnome.Shell.desktop[2331]: Window manager warning: "XF86RFKill" is not a valid accelerator
There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives/wayland- devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. -- 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/1722034 Title: org.gnome.Shell.desktop[2331]: Window manager warning: "XF86RFKill" is not a valid accelerator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1731928] Re: Evince hangs giving "Failed to Reload: Timeout was reached"
yes, i do have a custom kernel. On Thu, Dec 28, 2017 at 1:20 PM joostetowrote: > I just saw this bug too. > > Do we both happen to have linux kernel 4.14.0 installed? Mine is > custom-compiled, > and I believe 4.14.0 isn't part of ubuntu 17.10 yet, right? > > DistroRelease: Ubuntu 17.10 > > uname -a > Linux abelo 4.14.0-custom #1 SMP Wed Nov 15 19:50:07 CET 2017 x86_64 > x86_64 x86_64 GNU/Linux > > dpkg -l evince > [...] > ii evince 3.26.0-1 amd64 > Document (PostScript, PDF) viewer > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1731928 > > Title: > Evince hangs giving "Failed to Reload: Timeout was reached" > > Status in evince package in Ubuntu: > Invalid > > Bug description: > Evince recently stopped working for me. > > If I try to load a pdf from the command line I get "Failed to Reload: > Timeout was reached" after many seconds to minutes of hanging. The > CPU is not used excessively during this period. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: evince 3.26.0-1 > Uname: Linux 4.14.0-jakeday-surface x86_64 > ApportVersion: 2.20.7-0ubuntu3.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Mon Nov 13 15:03:08 2017 > InstallationDate: Installed on 2017-05-01 (196 days ago) > InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 > (20170412) > SourcePackage: evince > UpgradeStatus: Upgraded to artful on 2017-11-01 (12 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1731928/+subscriptions > -- 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/1731928 Title: Evince hangs giving "Failed to Reload: Timeout was reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1731928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691867] Re: New binary name: gnome-user-docs instead of gnome-user-guide
** Changed in: vino (Ubuntu) Status: New => Fix Released -- 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/1691867 Title: New binary name: gnome-user-docs instead of gnome-user-guide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-commander/+bug/1691867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739022] Re: Wayland session does not start any more when bash is the default shell
I would like to opine specifically that if $XDG_DATA_DIRS is specifically not what the shell expects -- for example it might contain a corrupted character from translating between fish arrays and bash arrays -- Gnome Shell on Wayland will not start. On X11, Gnome Shell will start. This is concerning because, by default, when I took a fresh 17.10 install and installed fish, then changed my shell to it, it did not have the correct value for XDG_DATA_DIRS and I wasn't able to start a wayland session at all. -- 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/1739022 Title: Wayland session does not start any more when bash is the default shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731928] Re: Evince hangs giving "Failed to Reload: Timeout was reached"
I just saw this bug too. Do we both happen to have linux kernel 4.14.0 installed? Mine is custom-compiled, and I believe 4.14.0 isn't part of ubuntu 17.10 yet, right? DistroRelease: Ubuntu 17.10 uname -a Linux abelo 4.14.0-custom #1 SMP Wed Nov 15 19:50:07 CET 2017 x86_64 x86_64 x86_64 GNU/Linux dpkg -l evince [...] ii evince 3.26.0-1 amd64 Document (PostScript, PDF) viewer -- 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/1731928 Title: Evince hangs giving "Failed to Reload: Timeout was reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1731928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740416] [NEW] nfs and cifs mounts are attempted too early in boot process
Public bug reported: Systemd should automatically wait for networking and DNS systems to be in place prior to attempting to mount CIFS or NFS filesystems. This was the behavior under Ubuntu 17.04. After upgrading to 17.10 the behavior changed. Systemd no longer waits for networking and DNS to be initialized before attempting to mount network filesystems. This requires me to manually mount these systems or add a hack in the rc.local file. Adding _netdev to the fstab entry does not change the incorrect behavior. Here is the example that worked under 17.04 but no longer works under 17.10: drobo5n:/mnt/DroboFS/Shares/PublicNFS /mnt/drobo5n nfs async,proto=tcp 0 0 I also tried: drobo5n:/mnt/DroboFS/Shares/PublicNFS /mnt/drobo5n nfs _netdev,async,proto=tcp 0 0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 28 12:44:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-23 (370 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=f8d7b91b-a6a4-4ead-a69c-d6249fc9b9ed ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/docker.service → /etc/systemd/system/docker.service.d/override.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to artful on 2017-12-28 (0 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1740416 Title: nfs and cifs mounts are attempted too early in boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740404] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1706097, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1740404/+attachment/5028391/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1740404/+attachment/5028393/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1740404/+attachment/5028397/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1740404/+attachment/5028398/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1740404/+attachment/5028399/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1740404/+attachment/5028400/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1740404/+attachment/5028401/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1740404 Title: gvfsd-mtp crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1740404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740404] [NEW] gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Public bug reported: One more gvfs probrem, if needed extra info... ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.34.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6 Uname: Linux 4.14.0-3-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 Date: Thu Dec 28 13:02:20 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2016-08-02 (512 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/6 SegvAnalysis: Segfault happened at: 0x7f7a267af5a9: mov0x18(%rax),%rax PC (0x7f7a267af5a9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2017-11-24 (34 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1740404 Title: gvfsd-mtp crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1740404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740345] Re: Upgrade epiphany-browser to 3.26.5.1
This bug was fixed in the package epiphany-browser - 3.26.5.1-1ubuntu1 --- epiphany-browser (3.26.5.1-1ubuntu1) bionic; urgency=medium * Sync with Debian (LP: #1740345). Remaining change: - Modify 07_bookmarks.patch: + Add Ubuntu-specific default bookmarks, borrowed from Firefox epiphany-browser (3.26.5.1-1) unstable; urgency=medium * New upstream release epiphany-browser (3.26.4-1) unstable; urgency=medium * New upstream release * Update Vcs fields for conversion to git * Add debian/gbp.conf * Bump Standards-Version to 4.1.2 -- Jeremy BichaWed, 27 Dec 2017 23:32:12 -0500 ** Changed in: epiphany-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1740345 Title: Upgrade epiphany-browser to 3.26.5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1740345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728143] Re: Screen freezes after waking from suspend with Gnome on Wayland
I am facing the exact same thing with a fresh install of 17.10 on my XPS 13 9343. The occurrence seems absolutely random, but it feels like the occurrence becomes more often over the time. I will now switch to Xorg for both GDM and the session itself. I report back after some days. For me, while the issue occurs I can still toggle the keyboard back light and the wireless kill switch. The network seems fully responsive, but as I logged in using SSH, I was not able to find any log messages or strange system behavior. -- Greetings from 34c3 (just writing this in case anyone wants to meet for debugging :-)) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1728143 Title: Screen freezes after waking from suspend with Gnome on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1728143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739980] Re: Depends libpopper68 version 0.57.0-2ubuntu4 but only 0.57.0-2ubuntu4.1 is available
Thanks for taking your time to report this issue and help making Ubuntu better. I was unable to reproduce this issue on Ubuntu 17.10 (though I tested with amd64). My theory is that the installable packages might have been temporarily out of sync (some had the latest 0.57.0-2ubuntu4.1 version, but not all). Could you please run `sudo apt update` and see if that makes the package installable? If the problem persists, could you attach the output from `apt policy libpoppler-qt5-1`? ** Changed in: poppler (Ubuntu) Status: New => Incomplete ** Tags added: unmetdeps -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1739980 Title: Depends libpopper68 version 0.57.0-2ubuntu4 but only 0.57.0-2ubuntu4.1 is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1739980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 671024] Re: can't connect to more than one openvpn at once
*** This bug is a duplicate of bug 91389 *** https://bugs.launchpad.net/bugs/91389 ** Also affects: network-manager-openvpn (openSUSE) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/671024 Title: can't connect to more than one openvpn at once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/671024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724024] Re: can't set usable scale for hidpi internal display if when using external display less than 1600x1200
Still experiencing this issue after the latest patch Ubuntu 17.10 Gnome Shell Version: GNOME Shell 3.26.2 Mutter Version: mutter 3.26.2 Preconditions: Two monitors (2560x1440 and 3840x2160) Steps to reproduce: - Open gnome-control-center from command line - Navigate to Devices -> Displays - Change scale from 100% to 200% Expected: - Able to apply the scale changes to the monitor Actual: - Receive error in the terminal Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitor scales must be identical -- 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/1724024 Title: can't set usable scale for hidpi internal display if when using external display less than 1600x1200 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend
For now, I use this workaround: Open Gnome "Settings", go to "Devices" -> "Colour" and toggle the colour management for the screen(s) off and on again. -- 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/1686895 Title: Gnome Night Light stays warmer after overnight suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686895/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs