[Bug 1736072] [NEW] Encrypted swap does not work
Public bug reported: On a working system, i've added a new hdd, and decided to use it as the main device storage. So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation. Booting with that new install, i hit a cryptswap1 timeout after beeing frozen around 1 minute. oem@ubuntu:~$ journalctl | grep cryptswap systemd[1]: Starting Cryptography Setup for cryptswap2... systemd[1]: Started Cryptography Setup for cryptswap2. systemd[1]: Found device /dev/mapper/cryptswap2. systemd[1]: Activating swap /dev/mapper/cryptswap2... kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1 extents:1 across:10584572k FS systemd[1]: Activated swap /dev/mapper/cryptswap2. systemd[1]: Starting Cryptography Setup for cryptswap1... systemd[1]: Started Cryptography Setup for cryptswap1. oem@ubuntu:~$ journalctl | grep timeout systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'. Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition. /etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens. oem@ubuntu:~$ swapon -s FilenameTypeSizeUsedPriority /dev/dm-0 partition 10584572221184 -1 Conclusion: -ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions - the cryptsetup version is not well supporting the kernel/systemd settings/configs As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these. http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:1.7.3-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 4 07:26:17 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic upgrade-software-version ** Description changed: On a working system, i've added a new hdd, and decided to use it as the main device storage. - So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. + So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation. Booting with that new install, i hit a cryptswap1 timeout after beeing frozen around 1 minute. oem@ubuntu:~$ journalctl | grep cryptswap - Dec 04 05:07:09 ubuntu systemd[1]: Starting Cryptography Setup for cryptswap2... - Dec 04 05:07:09 ubuntu systemd[1]: Started Cryptography Setup for cryptswap2. - Dec 04 05:07:09 ubuntu systemd[1]: Found device /dev/mapper/cryptswap2. - Dec 04 05:07:09 ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap2... - Dec 04 05:07:09 ubuntu kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1 extents:1 across:10584572k FS - Dec 04 05:07:09 ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap2. - Dec 04 05:07:09 ubuntu systemd[1]: Starting Cryptography Setup for cryptswap1... - Dec 04 05:07:09 ubuntu systemd[1]: Started Cryptography Setup for cryptswap1. + systemd[1]: Starting Cryptography Setup for cryptswap2... + systemd[1]: Started Cryptography Setup for cryptswap2. + systemd[1]: Found device /dev/mapper/cryptswap2. + systemd[1]: Activating swap /dev/mapper/cryptswap2... + kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1 extents:1 across:10584572k FS + systemd[1]: Activated swap /dev/mapper/cryptswap2. + systemd[1]: Starting Cryptography Setup for cryptswap1... + systemd[1]: Started Cryptography Setup for cryptswap1. + oem@ubuntu:~$ journalctl | grep timeout - Dec 04 05:08:36 ubuntu systemd[1]:
[Bug 1634354] Re: Copy and paste keyboard shortcuts on right click menu do not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1634354 Title: Copy and paste keyboard shortcuts on right click menu do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1634354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736046] [NEW] No sound indicator when login screen is ready
Public bug reported: unity-greeter gives an audio indication when the login screen is ready. This is considered an accessibility feature for people who have limited eyesight. (It's still possible for a computer to take well over a minute from startup to get to the Ubuntu login screen. For instance, LP: #1670336 is not fixed yet.) GDM in at least Ubuntu 17.10/18.04 does not play an audio indication. gnome-session-canberra includes /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop That file has these contents: [Desktop Entry] Type=Application Name=GNOME System Ready Sound Comment=Plays a sound whenever your system is ready for login Exec=/usr/bin/canberra-gtk-play --id="system-ready" --description="GNOME System Ready" OnlyShowIn=GNOME; AutostartCondition=GSettings org.gnome.desktop.sound event-sounds X-GNOME-Autostart-Phase=Application X-GNOME-Provides=login-sound ubuntu-sounds provides the system-ready sound in /usr/share/sounds/ubuntu/stereo/system-ready.ogg I tried commenting out the OnlyShowIn and AutostartCondition lines just in case one of them was at fault but it didn't make a difference. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: a11y artful bionic -- 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/1736046 Title: No sound indicator when login screen is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1736046/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
@dino99 Happy to open a new bug report on this, as it still appears to be an issue in latest Ubuntu 17.10. Usually when reporting bugs, I opt to prefer adding information to an existing bug report that I have high confidence describes the problem I am seeing. I believe this helps to reduce creating many duplicates and to focus community effort on resolving the main underlying problem rather than bug report management overhead from many duplicates or "me too" comments with no helpful debug info. If this is not preferred on this project, or for some reason doesn't fit the developer bug triage process here, that's fine. I'm happy to add information upstream or in another LaunchPad bug. Back to this problem: As it is a segfault reported in upstream gnome-shell which has something to do with OpenGL + resize behavior, I don't believe borked settings are the issue, nothing I've seen yet points towards that, although it'd be nice if the problem could be resolved by a config change instead of code change. This system never had any gnome-shell installed because Unity was there instead. Therefore, no pre-existing gnome-shell configuration can be hanging around. I've posted to upstream bug, but some info was here. To clarify: I do not have an Nvidia optimus nor do I use noveau, but use older nvidia-340 binary drivers. This is the nvidia recommended set of drivers for my card. Another comment in the upstream report mentions the issue may not have as much to do with Nvidia as it does with Xrandr fast video mode changes. I have confirmed this behavior in my own testing, and have a reproduction test case that works pretty reliably for me: Reproduction Command: # Use output and modes that are valid for you... xrandr --output HDMI-0 --mode 1920x1080 ; xrandr --output HDMI-0 --mode 1920x1080 ; xrandr --output HDMI-0 --mode 800x600 ; xrandr --output HDMI-0 --mode 1920x1080 I've tested this a couple times and it looks like I am able to trigger the crash just with fast xrandr commands. -- 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/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()
** Changed in: totem (Debian) Status: Unknown => Fix Released -- 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/1710858 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 103571] ✈Re: omg! that's interesting
Dear, Below are a few interesting facts you might be interested in, I think this information could be helpful, read it here http://www.studiocitymd.com/acagx.php?UE8xMDM1NzFAYnVncy5sYXVuY2hwYWQubmV0 Sent from my iPhone, Pietro Marchionda -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/103571 Title: Cover art plugin regression: sidebar resizing results in bad image quality To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/103571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()
Created backport requrest for fixed version of apparmor-profiles-extra https://bugs.launchpad.net/artful-backports/+bug/1736039 -- 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/1710858 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()
** Bug watch added: Debian Bug tracker #879900 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879900 ** Also affects: totem (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879900 Importance: Unknown Status: Unknown -- 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/1710858 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()
Crash happens only if `usr.bin.totem` AppArmor profile from `apparmor- profiles-extra` is enabled. -- 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/1710858 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1710858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 241198] Re: gdm doesn't respect umask setting
There's something closely related happening in actual ubuntu 17.10 : https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1701757 https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754 It makes managing muti-users machines and shared folders almost impossible… -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/241198 Title: gdm doesn't respect umask setting To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/241198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736030] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1732878 *** https://bugs.launchpad.net/bugs/1732878 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 #1732878, 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/1736030/+attachment/5017922/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1736030/+attachment/5017924/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1736030/+attachment/5017927/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1736030/+attachment/5017928/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1736030/+attachment/5017929/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1736030/+attachment/5017930/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1736030/+attachment/5017931/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1732878 gnome-shell crashed with signal 5 in g_log_default_handler() ** 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/1736030 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
Hello Everyone. I've been following this thread and tried every fix here to no avail. I live in Canada and I want to keep my Ubuntu in English, with Canadian Locale because most of the time I'll be writing in english and working regularly with Canadian (very similar to us) locale, I guess... but when I'm relaxing Talking to family or friends in Brasil, I'll need accents like áéíúú and the f'ing ç. Right now the closest I've come was having 2 "entry methods" that I switch back and forth. 1) English (Canada) for when I'm writing in english and 2) English (US, International with DeadKeys) for when I want to write Portuguese-BR. Here is what I've done so far My Ubuntu version to begin with: geraldo@geraldubuntu:~$ uname -v #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 Language support: English (Canada) Keyboard input method (None) (had tried with iBus) no difference. Those two keyboards layout as mentioned. Two changes in ~/.profile (Comment #115 and other): geraldo@geraldubuntu:~$ cat ~/.profile | grep export export LC_CTYPE=pt_BR.UTF-8 export XCOMPOSEFILE=/usr/share/X11/locale/pt_BR.UTF-8/Compose Here is how my locale look like, so I know comment #115 is set properly: geraldo@geraldubuntu:~$ locale LANG=en_CA.UTF-8 LANGUAGE=en_CA:en LC_CTYPE=pt_BR.UTF-8 LC_NUMERIC="en_CA.UTF-8" LC_TIME="en_CA.UTF-8" LC_COLLATE="en_CA.UTF-8" LC_MONETARY="en_CA.UTF-8" LC_MESSAGES="en_CA.UTF-8" LC_PAPER="en_CA.UTF-8" LC_NAME="en_CA.UTF-8" LC_ADDRESS="en_CA.UTF-8" LC_TELEPHONE="en_CA.UTF-8" LC_MEASUREMENT="en_CA.UTF-8" LC_IDENTIFICATION="en_CA.UTF-8" LC_ALL= Also tried edditing other files... please note: geraldo@geraldubuntu:~$ cat /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache | grep cedilla "/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so" "cedilla" "Cedilla" "gtk30" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en" geraldo@geraldubuntu:~$ cat /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache | grep cedilla "/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so" "cedilla" "Cedilla" "gtk30" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en" And I'm still getting ć. Any tips for me? This is frustrating :/ Thank you for your time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (46226). https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736018] Re: gjs-console crashed with SIGSEGV in g_slice_free_chain_with_offset()
*** This bug is a duplicate of bug 1715273 *** https://bugs.launchpad.net/bugs/1715273 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 #1715273, 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/1736018/+attachment/5017891/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1736018/+attachment/5017893/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1736018/+attachment/5017897/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1736018/+attachment/5017898/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1736018/+attachment/5017899/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1736018/+attachment/5017900/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1736018/+attachment/5017901/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715273 ** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1736018 Title: gjs-console crashed with SIGSEGV in g_slice_free_chain_with_offset() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1736018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1564695] Re: The command "who -m" doesn't work
Closing now as gnome-terminal has been released, and there is no comment since #7 above. ** Changed in: vte2.91 (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntukylin Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1564695 Title: The command "who -m" doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1564695/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
** Description changed: That error is logged: gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 oem@ubuntu:~$ localectl System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: fr X11 Model: pc105 X11 Variant: oss So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 and then ran 'sudo locale-gen' and finally rebooted. But the error is still logged after reboot: either i need to set also 'VC Keymap', but how ?, or it is related to the vte version actually used (and need an upgrade) + (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 3 17:17:45 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728383] Re: Unable to create a DBus proxy for GnomeScreensaver
*** This bug is a duplicate of bug 1736011 *** https://bugs.launchpad.net/bugs/1736011 ** This bug has been marked a duplicate of bug 1736011 CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- 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/1728383 Title: Unable to create a DBus proxy for GnomeScreensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1728383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717355] Re: X11 session crashes when locked/unlocked
*** This bug is a duplicate of bug 1736011 *** https://bugs.launchpad.net/bugs/1736011 ** This bug is no longer a duplicate of bug 1728383 Unable to create a DBus proxy for GnomeScreensaver ** This bug has been marked a duplicate of bug 1736011 CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- 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/1717355 Title: X11 session crashes when locked/unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1717355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- 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/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
** Description changed: That error is logged: gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 oem@ubuntu:~$ localectl -System Locale: LANG=en_US.UTF-8 -VC Keymap: n/a - X11 Layout: fr -X11 Model: pc105 - X11 Variant: oss + System Locale: LANG=en_US.UTF-8 + VC Keymap: n/a + X11 Layout: fr + X11 Model: pc105 + X11 Variant: oss - So, with googling help, i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 - and then ran 'sudo locale-gen' and finally rebooted. + So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 + and then ran 'sudo locale-gen' and finally rebooted. + + But the error is still logged after reboot: either i need to set also + 'VC Keymap', but how ?, or it is related to the vte version actually + used (and need an upgrade) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 3 17:17:45 2017 EcryptfsInUse: Yes ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736012] [NEW] package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed')
Public bug reported: ocurre esta error al prender el computador ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evince-common 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 2 14:45:21 2017 DpkgHistoryLog: Start-Date: 2017-12-02 14:45:00 Commandline: apt-get install gimp Requested-By: juanmarcon (1000) Install: liblapack3:amd64 (3.6.0-2ubuntu2, automatic), libgegl-0.3-0:amd64 (0.3.4-1ubuntu2, automatic), libraw15:amd64 (0.17.1-1ubuntu0.1, automatic), libumfpack5.7.1:amd64 (1:4.4.6-1, automatic), libcamd2.4.1:amd64 (1:4.4.6-1, automatic), libccolamd2.9.1:amd64 (1:4.4.6-1, automatic), gimp-data:amd64 (2.8.16-1ubuntu1.1, automatic), python-cairo:amd64 (1.8.8-2, automatic), gimp:amd64 (2.8.16-1ubuntu1.1), libblas-common:amd64 (3.6.0-2ubuntu2, automatic), libbabl-0.1-0:amd64 (0.1.16-1, automatic), libgfortran3:amd64 (5.4.0-6ubuntu1~16.04.5, automatic), libamd2.4.1:amd64 (1:4.4.6-1, automatic), libsdl1.2debian:amd64 (1.2.15+dfsg1-3, automatic), python-gtk2:amd64 (2.24.0-4ubuntu1, automatic), libgimp2.0:amd64 (2.8.16-1ubuntu1.1, automatic), libblas3:amd64 (3.6.0-2ubuntu2, automatic), python-gobject-2:amd64 (2.28.6-12ubuntu1, automatic), libcholmod3.0.6:amd64 (1:4.4.6-1, automatic) ErrorMessage: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-11-22 (10 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic root=UUID=d4cd7dcc-09f3-453d-95f3-95d9e6bf686f ro quiet splash vt.handoff=7 SourcePackage: evince Title: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1736012 Title: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] [NEW] CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited:
Public bug reported: That error is logged: gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 oem@ubuntu:~$ localectl System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: fr X11 Model: pc105 X11 Variant: oss So, with googling help, i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 and then ran 'sudo locale-gen' and finally rebooted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 3 17:17:45 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (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 gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720131] Re: logind holds open file descriptor to DRI nodes, preventing nvidia suspend
** Changed in: systemd 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/1720131 Title: logind holds open file descriptor to DRI nodes, preventing nvidia suspend To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1720131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735993] Re: Ghost window & launcher icon not selected when opening a folder in external disk
I've realized the new window that is created when you open the external disk unit DOES have an icon on Launcher, which gets selected when it has focus and correctly shows the triangle(s) indicating its existing window(s). But it is separated from Nautilus' main Launcher icon. This is a completely broken UI design. There's no reason to generate a separate icon in Launcher with a different symbol, and even if that made sense, there should be some kind of animation when this happens showing you that the existing window was destroyed and a new one has been created. The overall user experience is inconsistent: if you look at the window you are interacting with, all seems like you keep using the same window, interacting with its contents which change. If you look at the Launcher icons, it looks like a new window has been created and the old one destroyed. -- 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/1735993 Title: Ghost window & launcher icon not selected when opening a folder in external disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735993] Re: Ghost window & launcher icon not selected when opening a folder in external disk
** Attachment added: "Screenshot from 2017-12-03 14-28-50.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+attachment/5017774/+files/Screenshot%20from%202017-12-03%2014-28-50.png -- 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/1735993 Title: Ghost window & launcher icon not selected when opening a folder in external disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735993] Re: Ghost window & launcher icon not selected when opening a folder in external disk
** Attachment added: "Screenshot from 2017-12-03 14-29-08.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+attachment/5017775/+files/Screenshot%20from%202017-12-03%2014-29-08.png -- 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/1735993 Title: Ghost window & launcher icon not selected when opening a folder in external disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735993] [NEW] Ghost window & launcher icon not selected when opening a folder in external disk
Public bug reported: I have an external disk connected via USB; it contains several logical units one of which is called "IOM_data". Steps to reproduce the issue: 1. Open Nautilus 2. On the left panel, select the IOM_data unit Expected behavior: Should display the contents of the external disk unit, and Nautilu's Launcher icon should still be selected. Observed behavior: Displays the contents of the external unit, but the Launcher icon of Nautilus is no longer highlighted, not only that, it doesn't have any triangle on the left of it, as if no Nautilus window was open at all. Additional steps: 3. Now click on Nautilus' Launcher icon Expected result: Since the icon should be already selected in the first place, nothing should happen at all. If in the meantime you had given focus to some other window, this should simply give focus back to the existing Nautilus window where you had opened the external disk unit. Observed result: This opens a NEW Nautilus window, showing by default the Home folder. The Launcher icon looks like this is the only existing Nautilus window. However, the other Nautilus window with the external disk unit still exists. You can reach it with Alt+Tab or by minimizing/moving other windows until it becomes visible. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 3 14:29:20 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1513 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: I have an external disk connected via USB; it contains several logical units one of which is called "IOM_data". Steps to reproduce the issue: 1. Open Nautilus 2. On the left panel, select the IOM_data unit Expected behavior: Should display the contents of the external disk unit, and Nautilu's Launcher icon should still be selected. Observed behavior: Displays the contents of the external unit, but the Launcher icon of Nautilus is no longer highlighted, not only that, it doesn't have any triangle on the left of it, as if no Nautilus window was open at all. - Additional steps: 3. Now click on Nautilus' Launcher icon Expected result: Since the icon should be already selected in the first place, nothing should happen at all. If in the meantime you had given focus to some other window, this should simply give focus back to the existing Nautilus window where you had opened the external disk unit. Observed result: This opens a NEW Nautilus window, showing by default the Home folder. The Launcher icon looks like this is the only existing Nautilus window. However, the other Nautilus window with the external disk unit still exists. You can reach it with Alt+Tab or by minimizing/moving other windows until it becomes visible. - - The very fact that a window CAN exist without having a corresponding icon in Launcher is either a bug or a design flaw in the Unity itself (or in Launcher, or whoever is responsible for that). This should be something IMPOSSIBLE at the lowest level. And there are other instances of that happening unrelated to Nautilus (I think I reported some). - Besides that, I guess Nautilus is doing something wrong too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 3 14:29:20 2017 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' - b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'" - b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' + b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'" +
[Bug 1735986] Re: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display
apport information ** Tags added: apport-collected artful wayland-session ** Description changed: I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So now running on 17.10. I upgraded to 17.10 because I hoped for better HiDPI scaling support. My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with Intel graphics (it has nvidia too, but disabled). Additionally, I have an external Dell U3011 2560x1600 30" display connected to it. When I logged into graphical session (selected the default Ubuntu session), I confirmed wayland is running by checking loginctl: loginctl show-session 2 -p Type Type=wayland With external display connected, display settings show that the high DPI laptop screen got scaling set automatically to 200%, and the external low DPI display got scaling set to 100%. So far, looks good - automatic detection of hi dpi screens did the right thing. The built-in Ubuntu applications like terminal, file browser or setting window work fine. When I start e.g. the terminal, it appears first on the laptop screen - it is scaled properly, then I drag it to the external screen and once I release the mouse button, the window shrinks to 2x smaller, so it adapts to lower DPI of that screen. Everything is sharp and crispy and the sizes are ok. Problems: * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on the external screen. Everything is twice too big. When started, they appear first on the built-in hiDPI screen with the correct size, but after dragging to the external screen, they remain scaled by 200%. * When I enabled dock to be displayed on all screens, the dock icons are twice too big on the external screen. So, 200% scaling seems to be applied to the dock on both screens. * Sometimes the mouse pointer is twice as large. Sometimes it is twice too small. I didn't figure out yet when it happens. Sometimes it is only twice too large when over the desktop background, but ok when over an application window. This is a very minor issue, but looks funny. - What I tried so far: Resetting dconf to factory settings with: dconf reset -f /org/gnome/ did not help. Then I tried enabling experimental fractional scaling, with 200% / 100% scales set (I do not really need fractional scaling, but I hoped it changes how things are rendered and where scaling is applied). This actually helped for both scaling issues - including the dock scaling problem. Windows get even properly scaled in the *middle of dragging* between displays. Everything is the right size with this setting on. Really cool. Unfortunately now the image on the builtin display for the non-native applications like Firefox, Chrome or Idea is severely blurred. And it is blurred even if I disconnect the external display. It looks as if it rendered these apps at half the resolution (I noticed xrandr shows 1920x1080 for that screen, but ubuntu display settings window shows 3840x2160) and then upscaled twice the bitmap to reach higher 4k real screen resolution. The blur does not happen for native Ubuntu apps like terminal. Unfortunately the blurring effect is much stronger than if I just manually force the builtin screen to 1920x1080. In this case everything is a bit lower resolution, but still sharp enough. - Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi - support for me at all, despite some rumours it should have. I still have - to switch to lower resolution on the builtin display to get everything - crisp and the right size. + Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for me at all, despite some rumours it should have. I still have to switch to lower resolution on the builtin display to get everything crisp and the right size. + --- + ApportVersion: 2.20.7-0ubuntu3.5 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-04-12 (234 days ago) + InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 + Package: gnome-control-center 1:3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash + Tags: artful wayland-session + Uname: Linux 4.14.3-041403-generic x86_64 + UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) + UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1735986/+attachment/5017750/+files/Dependencies.txt -- You received this bug
[Bug 1735986] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1735986/+attachment/5017751/+files/JournalErrors.txt -- 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/1735986 Title: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1735986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735986] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1735986/+attachment/5017752/+files/ProcCpuinfoMinimal.txt -- 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/1735986 Title: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1735986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735986] [NEW] Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display
Public bug reported: I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So now running on 17.10. I upgraded to 17.10 because I hoped for better HiDPI scaling support. My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with Intel graphics (it has nvidia too, but disabled). Additionally, I have an external Dell U3011 2560x1600 30" display connected to it. When I logged into graphical session (selected the default Ubuntu session), I confirmed wayland is running by checking loginctl: loginctl show-session 2 -p Type Type=wayland With external display connected, display settings show that the high DPI laptop screen got scaling set automatically to 200%, and the external low DPI display got scaling set to 100%. So far, looks good - automatic detection of hi dpi screens did the right thing. The built-in Ubuntu applications like terminal, file browser or setting window work fine. When I start e.g. the terminal, it appears first on the laptop screen - it is scaled properly, then I drag it to the external screen and once I release the mouse button, the window shrinks to 2x smaller, so it adapts to lower DPI of that screen. Everything is sharp and crispy and the sizes are ok. Problems: * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on the external screen. Everything is twice too big. When started, they appear first on the built-in hiDPI screen with the correct size, but after dragging to the external screen, they remain scaled by 200%. * When I enabled dock to be displayed on all screens, the dock icons are twice too big on the external screen. So, 200% scaling seems to be applied to the dock on both screens. * Sometimes the mouse pointer is twice as large. Sometimes it is twice too small. I didn't figure out yet when it happens. Sometimes it is only twice too large when over the desktop background, but ok when over an application window. This is a very minor issue, but looks funny. - What I tried so far: Resetting dconf to factory settings with: dconf reset -f /org/gnome/ did not help. Then I tried enabling experimental fractional scaling, with 200% / 100% scales set (I do not really need fractional scaling, but I hoped it changes how things are rendered and where scaling is applied). This actually helped for both scaling issues - including the dock scaling problem. Windows get even properly scaled in the *middle of dragging* between displays. Everything is the right size with this setting on. Really cool. Unfortunately now the image on the builtin display for the non-native applications like Firefox, Chrome or Idea is severely blurred. And it is blurred even if I disconnect the external display. It looks as if it rendered these apps at half the resolution (I noticed xrandr shows 1920x1080 for that screen, but ubuntu display settings window shows 3840x2160) and then upscaled twice the bitmap to reach higher 4k real screen resolution. The blur does not happen for native Ubuntu apps like terminal. Unfortunately the blurring effect is much stronger than if I just manually force the builtin screen to 1920x1080. In this case everything is a bit lower resolution, but still sharp enough. Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for me at all, despite some rumours it should have. I still have to switch to lower resolution on the builtin display to get everything crisp and the right size. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1735986 Title: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1735986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735969] [NEW] Windows move to background
Public bug reported: Ubuntu 17.10 mutter 3.26.2-0ubuntu0.1 Open three windows, one using the entire left half of the screen, one using the entire right half of the screen, and one small window that you put (entirely) in front of the large window on the left side. If you focus the window on the right side, the small window is put behind the large window on the left side. I expect the small window to remain in front of the large window on the left side since it is not affected by the window on the right side. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/1735969 Title: Windows move to background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1735969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
