[Bug 1768996] Re: Nautilus "Software caused connection abort" when copying file from smb share
I've been able to transfer files to my network drive through cifs. sudo mount -t cifs -o username=guest,guest,vers=1.0 //1.10.2.1/folder /home/user/mnt -- 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/1768996 Title: Nautilus "Software caused connection abort" when copying file from smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806165] Re: Ubuntu 18.10 I get logged off on resume from suspend - Unregistered Authentication Agent for unix-session
** Description changed: This is not a problem using only built in laptop screen however when I attach an external monitor and choose Setting->Display->Single Display then choose the external monitor to be the only active screen -> then when I suspend upon resume the external monitor lights up showing the password prompt which is good however after entering password all my launched applications are no longer running ... according to - /var/log/auth.log I get logged me out during this suspend/resume - this + /var/log/auth.log I get logged out during this suspend/resume - this issue is repeatable getting same behaviour whether using nouveau or nvidia drivers ... its a fresh 18.10 install not an upgrade - - Here is a clip from /var/log/auth.log look closely at messages just after `Lid opened` - + Here is a clip from /var/log/auth.log look closely at messages just + after `Lid opened` - Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session closed for user root Nov 30 21:20:18 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/863, but it's already registered Nov 30 21:20:19 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/862, but it's already registered Nov 30 21:40:36 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered Nov 30 21:40:39 nuem gnome-keyring-daemon[3057]: message repeated 2 times: [ asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered] Nov 30 21:49:25 nuem systemd-logind[523]: Lid closed. Nov 30 21:49:29 nuem systemd-logind[523]: Lid opened. Nov 30 21:49:51 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:49:52 nuem polkitd(authority=local): Unregistered Authentication Agent for unix-session:2 (system bus name :1.376, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 30 21:49:52 nuem gdm-password]: pam_unix(gdm-password:session): session closed for user upha Nov 30 21:49:52 nuem dbus-daemon[507]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.2100" (uid=1000 pid=31115 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) Nov 30 21:49:52 nuem systemd-logind[523]: Session 2 logged out. Waiting for processes to exit. Nov 30 21:49:53 nuem gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Nov 30 21:49:53 nuem systemd-logind[523]: New session c2 of user gdm. Nov 30 21:49:53 nuem systemd: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Nov 30 21:49:55 nuem systemd-logind[523]: Removed session 2. Nov 30 21:49:56 nuem systemd: pam_unix(systemd-user:session): session closed for user upha Nov 30 21:49:57 nuem polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.2108 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 30 21:50:07 nuem gdm-password]: pam_unix(gdm-password:session): session opened for user upha by (uid=0) Nov 30 21:50:07 nuem systemd-logind[523]: New session 37 of user upha. Nov 30 21:50:07 nuem systemd: pam_unix(systemd-user:session): session opened for user upha by (uid=0) Nov 30 21:50:17 nuem polkitd(authority=local): Registered Authentication Agent for unix-session:37 (system bus name :1.2405 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 30 21:50:19 nuem systemd-logind[523]: Session c2 logged out. Waiting for processes to exit. Nov 30 21:50:19 nuem polkitd(authority=local): Unregistered Authentication Agent for unix-session:c2 (system bus name :1.2108, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 30 21:50:19 nuem systemd-logind[523]: Removed session c2. Nov 30 21:52:50 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:52:59 nuem gdm-password]: gkr-pam: unlocked login keyring Nov 30 21:53:42 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:53:50 nuem gdm-password]: gkr-pam: unlocked login keyring Nov 30 22:17:02 nuem CRON[6950]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 30 22:17:02 nuem CRON[6950]: pam_unix(cron:session): session closed for user root - - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18
[Bug 1806165] [NEW] Ubuntu 18.10 I get logged off on resume from suspend - Unregistered Authentication Agent for unix-session
Public bug reported: This is not a problem using only built in laptop screen however when I attach an external monitor and choose Setting->Display->Single Display then choose the external monitor to be the only active screen -> then when I suspend upon resume the external monitor lights up showing the password prompt which is good however after entering password all my launched applications are no longer running ... according to /var/log/auth.log I get logged me out during this suspend/resume - this issue is repeatable getting same behaviour whether using nouveau or nvidia drivers ... its a fresh 18.10 install not an upgrade Here is a clip from /var/log/auth.log look closely at messages just after `Lid opened` - Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session closed for user root Nov 30 21:20:18 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/863, but it's already registered Nov 30 21:20:19 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/862, but it's already registered Nov 30 21:40:36 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered Nov 30 21:40:39 nuem gnome-keyring-daemon[3057]: message repeated 2 times: [ asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered] Nov 30 21:49:25 nuem systemd-logind[523]: Lid closed. Nov 30 21:49:29 nuem systemd-logind[523]: Lid opened. Nov 30 21:49:51 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:49:52 nuem polkitd(authority=local): Unregistered Authentication Agent for unix-session:2 (system bus name :1.376, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 30 21:49:52 nuem gdm-password]: pam_unix(gdm-password:session): session closed for user upha Nov 30 21:49:52 nuem dbus-daemon[507]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.2100" (uid=1000 pid=31115 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) Nov 30 21:49:52 nuem systemd-logind[523]: Session 2 logged out. Waiting for processes to exit. Nov 30 21:49:53 nuem gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Nov 30 21:49:53 nuem systemd-logind[523]: New session c2 of user gdm. Nov 30 21:49:53 nuem systemd: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Nov 30 21:49:55 nuem systemd-logind[523]: Removed session 2. Nov 30 21:49:56 nuem systemd: pam_unix(systemd-user:session): session closed for user upha Nov 30 21:49:57 nuem polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.2108 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 30 21:50:07 nuem gdm-password]: pam_unix(gdm-password:session): session opened for user upha by (uid=0) Nov 30 21:50:07 nuem systemd-logind[523]: New session 37 of user upha. Nov 30 21:50:07 nuem systemd: pam_unix(systemd-user:session): session opened for user upha by (uid=0) Nov 30 21:50:17 nuem polkitd(authority=local): Registered Authentication Agent for unix-session:37 (system bus name :1.2405 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 30 21:50:19 nuem systemd-logind[523]: Session c2 logged out. Waiting for processes to exit. Nov 30 21:50:19 nuem polkitd(authority=local): Unregistered Authentication Agent for unix-session:c2 (system bus name :1.2108, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 30 21:50:19 nuem systemd-logind[523]: Removed session c2. Nov 30 21:52:50 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:52:59 nuem gdm-password]: gkr-pam: unlocked login keyring Nov 30 21:53:42 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:53:50 nuem gdm-password]: gkr-pam: unlocked login keyring Nov 30 22:17:02 nuem CRON[6950]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 30 22:17:02 nuem CRON[6950]: pam_unix(cron:session): session closed for user root - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 30 23:41:25 2018 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Instal
[Bug 1793595] Re: Shell freezes, mostly when running chrome or editing text files.
[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/1793595 Title: Shell freezes, mostly when running chrome or editing text files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze on Intel Sandy Bridge i5-2500 GPU
[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/1792807 Title: Login screen freeze on Intel Sandy Bridge i5-2500 GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
** Changed in: mutter (Ubuntu Cosmic) Status: Triaged => Fix Released -- 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/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753776] Re: Graphics corruption just before login animation to Xorg sessions (Intel gen9 GPUs only)
Launchpad has imported 23 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=105518. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-03-15T09:31:00+00:00 Daniel van Vugt wrote: Xorg sessions are suddenly showing corruption upon login, briefly before the shell starts up. This seems to be related to the use of "-background none" by the DM. If I remove "-background none" from the DM code then the corruption is replaced by a less bad second or two of blackness. This problem seems to have started when Mesa 18.0.0 was introduced to Ubuntu 18.04. I can't seem to correlate it with anything else, and can't relate it to a specific Xorg update. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/24 On 2018-03-15T09:34:21+00:00 Michel Dänzer wrote: Please attach the corresponding Xorg log file. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/25 On 2018-03-15T09:37:24+00:00 Daniel van Vugt wrote: There's a log in the downstream bug: https://launchpad.net/bugs/1753776 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/27 On 2018-03-15T09:41:27+00:00 Michel Dänzer wrote: FWIW, you're more likely to get action on this if you reassign to the Mesa i965 driver. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/29 On 2018-03-15T09:42:48+00:00 Daniel van Vugt wrote: I'm not sure if the problem is confined to the Mesa i965 driver. It is possible. I have verified that the corruption occurs with both Xorg drivers though: modesetting and intel. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/30 On 2018-03-15T12:54:52+00:00 Timo Aaltonen wrote: seems to be limited to gen9 (and up?), can't reproduce on BDW but can on SKL/KBL/CFL Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/32 On 2018-03-16T01:24:54+00:00 Daniel van Vugt wrote: I agree with that assessment so far. KBL is affected, but HAS is not. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/40 On 2018-03-16T01:42:34+00:00 Daniel van Vugt wrote: KBL is affected, but HSW is not. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/41 On 2018-03-16T05:53:12+00:00 Daniel van Vugt wrote: OK, if the problem is only Intel and only gen9 then I am less concerned. But I will try to bisect this by next week. Certainly sounds like a Mesa 18 bug now. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/42 On 2018-03-19T01:40:58+00:00 Daniel van Vugt wrote: I can now also confirm in more detail that: HSW is not affected BDW is not affected SKL is affected KBL is affected Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776/comments/46 On 2018-03-19T09:42:52+00:00 Daniel van Vugt wrote: Bisected: 1efd73df39b39589d26f44d4927d2c65697bbe6e is the first bad commit commit 1efd73df39b39589d26f44d4927d2c65697bbe6e Author: Ben Widawsky Date: Tue May 30 17:24:06 2017 +0530 i965: Advertise the CCS modifier v2: Rename modifier to be more smart (Jason) FINISHME: Use the kernel's final choice for the fb modifier bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $) ~/scripts/measure_bandwidth.sh ./kmscube none Read bandwidth: 603.91 MiB/s Write bandwidth: 615.28 MiB/s bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $) ~/scripts/measure_bandwidth.sh ./kmscube ytile Read bandwidth: 571.13 MiB/s Write bandwidth: 555.51 MiB/s bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $) ~/scripts/measure_bandwidth.sh ./kmscube ccs Read bandwidth: 259.34 MiB/s Write bandwidth: 337.83 MiB/s v2: Move all references to the new fourcc code(s) to this patch. v3: Rebase, remove Yf_CCS (Daniel) Signed-off-by: Ben Widawsky Signed-off-by: Jason Ekstrand Acked-by: Daniel Stone Reviewed-by: Chad Versace :04 04 1770769b4
[Bug 1806146] [NEW] /usr/bin/gnome-software:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.30.2-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/348b9ddb7534cb63fe0dcac29ef8a00549bd3d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic xenial yakkety zesty -- 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/1806146 Title: /usr/bin/gnome- software:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805247] Re: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen
Confirmed same issue exists in Cosmic. Reported to upstream (https://gitlab.gnome.org/GNOME/gnome-shell/issues/831) We don’t intend to deviate from Canonical’s defaults for OEM projects unless necessary, but want to make sure that all issues are resolved when the defaults "are" Wayland. -- 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/1805247 Title: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805247/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
Found the following two entries had been added to /etc/apt/sources.list following automatic updates. deb [trusted=yes] http://ftp.us.debian.org/debian experimental main deb [trusted=yes] http://ftp.us.debian.org/debian sid main Commented them out and performed apt update. Then purged the following packages: apt purge gnome-settings-daemon gdm3 gnome-control-center gnome-initial-setup gnome-power-manager gnome-shell uatter ubuntu-desktop ubuntu-session This removed these packages, then reinstalled all pre-existing packages. Reboot returned system to normal functionality. -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
Ok, i've found that problem I was having had to do with IPv6 connectivity. Usually I disable the IPv6 connection because there are certain PPAs (archive.ubuntu.com, for example) that for some odd reason, never load, and they timeout on "sudo apt update". My network provider has no problem with the IPv6 service, but Ubuntu, usually, cannot load a PPA through IPv6. Because of that, I only allow IPv4 connectivity to be active, and that was the issue. It seems that g-i-s and g-c-c only want to connect via IPv6, even though it was disabled through the g-c-c. I think that both should first check on how the network is setup up and then load the webpages as determined by the settings. That is the issue. I hope it gets fixed. After I set IPv6 method to "Auto", both g-i-s and g-c-c loaded all log- in pages without a problem. -- 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/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
If you reboot after receiving this error you will be unable to get back into the system. Boot up will hang at "Started Update UTMP about System Runlevel Changes. Alt-F2 allows you to switch to login prompt. However, attempts to purge gnome and related dependencies or perform any updates fail. -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797582] Re: package gir1.2-gdm-1.0 3.28.3-0ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1797582 Title: package gir1.2-gdm-1.0 3.28.3-0ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
Found this Cairo edit, I have no idea if it is final or committed (some one here might know): https://gitlab.freedesktop.org/cairo/cairo/commit/bf597b89288b6271f56031d5a20bfaf59f146d4c -- 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/1560286 Title: Evince displays pdf file fine, but prints colors inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
This is page 7 printed as PDF, exactly as it gets out of the printer. ** Attachment added: "Aubert_Brumm_etal_2014_Sulawesi_Indonezia-pag-7+v2.pdf" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+attachment/5217756/+files/Aubert_Brumm_etal_2014_Sulawesi_Indonezia-pag-7+v2.pdf -- 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/1560286 Title: Evince displays pdf file fine, but prints colors inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
I add a pdf I get this in Ubuntu 18.10. Printing page 7 (and on), images look inverted. Only images, text is good. I printed as PDF and they turn dark (inverted I guess). Then I printed as Postscript (.ps) and they look fine, so a workaround would be to print files as postscript and then print them on the paper, but it is not a real solution. ** Attachment added: "from page 7 images are printed inverted in this pdf" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+attachment/5217755/+files/Aubert_Brumm_etal_2014_Sulawesi_Indonezia-pag-7+.pdf -- 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/1560286 Title: Evince displays pdf file fine, but prints colors inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806110] [NEW] O Gimp Fecha do nada
Public bug reported: GNU Image Manipulation Program version 2.10.6 git-describe: GIMP_2_10_4-278-g0a8173ffde C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-4ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1) using GEGL version 0.4.8 (compiled against version 0.4.8) using GLib version 2.58.1 (compiled against version 2.57.2) using GdkPixbuf version 2.38.0 (compiled against version 2.36.12) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.0 (compiled against version 2.13.0) using Cairo version 1.15.12 (compiled against version 1.15.12) ``` > fatal error: Erro de bus Stack trace: ``` # Stack traces obtained from PID 6445 - Thread 6584 # [New LWP 6523] [New LWP 6524] [New LWP 6526] [New LWP 6583] [New LWP 6584] [New LWP 6585] [New LWP 6587] [New LWP 7070] [New LWP 7143] [New LWP 7324] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Id Target Id Frame * 1Thread 0x7f9a6c36ee00 (LWP 6445) "gimp-2.10"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 2Thread 0x7f9a6ab06700 (LWP 6523) "gmain"0x7f9a6f1f46d9 in __GI___poll (fds=0x55becfc326d0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7f9a687a0700 (LWP 6524) "gdbus"0x7f9a6f1f46d9 in __GI___poll (fds=0x55becfc3bd50, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7f9a67f9f700 (LWP 6526) "dconf worker" 0x7f9a6f1f46d9 in __GI___poll (fds=0x55becfc24dd0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 5Thread 0x7f9a49cc7700 (LWP 6583) "async"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f9a494c6700 (LWP 6584) "worker" __libc_read (fd=51, buf=0x7f9a494c4fd0, nbytes=256) at ../sysdeps/unix/sysv/linux/read.c:26 7Thread 0x7f9a48cc5700 (LWP 6585) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f9a484c4700 (LWP 6587) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f9a4799a700 (LWP 7070) "threaded-ml" 0x7f9a6f1f46d9 in __GI___poll (fds=0x7f9a30002860, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7f9a42aa6700 (LWP 7143) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7f9a67562700 (LWP 7324) "paint"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 11 (Thread 0x7f9a67562700 (LWP 7324)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 No locals. #1 0x7f9a6f51263f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x55becf068cd7 in gimp_parallel_distribute () No symbol table info available. #3 0x55becf068e4e in gimp_parallel_distribute_area () No symbol table info available. #4 0x55becf18649d in gimp_gegl_convolve () No symbol table info available. #5 0x55becf141b04 in ?? () No symbol table info available. #6 0x55becf149e39 in gimp_paint_core_paint () No symbol table info available. #7 0x55becf13de93 in ?? () No symbol table info available. #8 0x55becee38312 in ?? () No symbol table info available. #9 0x55becee382a3 in ?? () No symbol table info available. #10 0x7f9a6f4f4135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #11 0x7f9a6f2d8164 in start_thread (arg=) at pthread_create.c:486
[Bug 1799205] Re: Ubuntu wayland sessions are not migrated to yaru
This bug was fixed in the package gnome-session - 3.30.1-1ubuntu1 --- gnome-session (3.30.1-1ubuntu1) disco; urgency=medium [ Iain Lane ] * Merge with Debian, remaining changes: - debian/control.in: + Recommend session-migration + Move xwayland dependency to gnome-session and make gnome-session Arch: any + Split gnome-startup-applications to a separate binary package so that it can be uninstalled without breaking the system + Add unity-session - Split ubuntu-session out of gnome-session. - Add upstart user session and systemd user session: debian/data, debian/gnome-session-bin.user-session.upstart - debian/gnome-session-bin.postinst, debian/gnome-session-bin.prerm: Moved registering gnome-session binary as a session manager to gnome-session-bin package - Add gnome-session-wayland transitional package - don't install gnome-mimeapps.list (installed by desktop-file-utils in Ubuntu): debian/gnome-session-common.dirs, gnome-session-common.install, gnome-session-common.maintscript, gnome-session-common.postinst - debian/patches/103_kill_the_fail_whale.patch: + Kill the Fail Whale as it tends to be more annoying than helpful - debian/patches/22_support_autostart_delay.patch: + Bugzilla patch to support adding a delay to autostart apps, using a "X-GNOME-Autostart-Delay" key in the desktop file - debian/patches/50_ubuntu_sessions.patch: + Add ubuntu session tweaks - debian/patches/51_remove_session_saving_from_gui.patch: + Add GNOME_SESSION_SAVE environment variable for people wanting to use the save session still, knowing that it can break your system if used unwisely - debian/patches/53_add_sessionmigration.patch: + launch session-migration if present at the start of the session. This sync tool runns different session migration scripts that can be provided in various desktop packages. - debian/patches/95_dbus_request_shutdown.patch: + Add "RequestShutdown" and "RequestReboot" DBus methods to allow other applications to shutdown or reboot the machine via the session manager. - debian/patches/ignore_gsettings_region.patch: + Ignore the "region" gsettings value - users' setting of LC_* variables saved in ~/.pam_environment. - debian/patches/revert_remove_gnome_session_properties.patch: + Don't merge translations into gnome-session-properties.desktop * debian/patches/50_ubuntu_sessions.patch: - moved to debian/patches/ubuntu/ubuntu-sessions.patch (using gbp topic) * ubuntu/ignore_gsettings_region.patch: Refresh [ Marco Trevisan (Treviño) ] * debian/ubuntu-settings-migrate-to-defaults.18.10.0.py: - renamed to ubuntu-settings-migrate-to-defaults.18.10.1.py + Also run in ubuntu-wayland desktop session (LP: #1799205) gnome-session (3.30.1-1) unstable; urgency=medium * Team upload * New upstream release * Bump Standards-Version to 4.2.1 * d/rules: Remove gnome-get-source.mk (please use uscan instead) * Set Rules-Requires-Root to no gnome-session (3.30.0-2) unstable; urgency=medium * Team upload * Release to unstable - d/gbp.conf, d/control: Set branch back to debian/master - d/watch: Only watch for upstream stable (even-numbered) releases gnome-session (3.30.0-1) experimental; urgency=medium * Team upload [ Iain Lane ] * debian/gbp.conf: Don't use patch numbers * d/p/debian/Revert-main-Remove-GNOME_DESKTOP_SESSION_ID-envvar.patch: Mark as not-needed upstream [ Raphaël Hertzog ] * Update gnome-mimeapps.list for evince's renamed desktop file (Closes: #908177) [ Simon McVittie ] * d/gbp.conf: Add standard post-import hook * New upstream release * d/copyright: Update -- Iain Lane Fri, 30 Nov 2018 16:32:53 + ** Changed in: gnome-session (Ubuntu) Status: In Progress => Fix Released -- 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/1799205 Title: Ubuntu wayland sessions are not migrated to yaru To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1799205/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
Affecting Ubuntu 18 since updates on 11/27. Update log file attached. /opt/symas/share/man/man1$ uname -a Linux launchpad.*.*** 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 GNU/Linux sudo apt-get install gnome-settings-daemon-schemas Reading package lists... Done Building dependency tree Reading state information... Done gnome-settings-daemon-schemas is already the newest version (3.28.1-0ubuntu1.1). gnome-settings-daemon-schemas set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (= 3.28.1-0ubuntu1) but 3.28.1-0ubuntu1.1 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: greybird-gtk-theme grub-gfxpayload-lists iputils-arping libart-2.0-2 libasn1-8-heimdal libfile-copy-recursive-perl libgcrypt20:i386 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libkrb5-26-heimdal liblz4-1:i386 libpcre3:i386 libroken18-heimdal libselinux1:i386 libsysmetrics1 libthunarx-2-0 libwind0-heimdal networkd-dispatcher python3-macaroonbakery python3-nacl python3-protobuf python3-pymacaroons python3-rfc3339 python3-tz thunar-data xubuntu-icon-theme zlib1g:i386 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gnome-settings-daemon The following packages will be upgraded: gnome-settings-daemon 1 upgraded, 0 newly installed, 0 to remove and 477 not upgraded. 1098 not fully installed or removed. Need to get 0 B/856 kB of archives. After this operation, 4,219 kB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 299204 files and directories currently installed.) Preparing to unpack .../gnome-settings-daemon_3.30.1.2-1_amd64.deb ... Unpacking gnome-settings-daemon (3.30.1.2-1) over (3.28.1-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/gnome-settings-daemon_3.30.1.2-1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/61-gnome-settings-daemon-rfkill.rules', which is also in package gnome-settings-daemon-schemas 3.28.1-0ubuntu1.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gnome-settings-daemon_3.30.1.2-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Attachment added: "Update Log File" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+attachment/5217740/+files/dpkg.log -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 461836] Re: Nautilus does not remember passwords to SMB shares in MS-Windows domain
** Changed in: gvfs Status: New => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/461836 Title: Nautilus does not remember passwords to SMB shares in MS-Windows domain To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/461836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802677] Re: Unmet Dependencies: gnome-settings-daemon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- 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/1802677 Title: Unmet Dependencies: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1802677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session
** Changed in: snapd (Ubuntu) Assignee: Zygmunt Krynicki (zyga) => (unassigned) ** Changed in: snapd (Ubuntu Cosmic) Assignee: Zygmunt Krynicki (zyga) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1794953 Title: GNOME Calculator snap has wrong theme in live session To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1794953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
This bug has been around since 14.04 and persists in 18.04 This bug causes unexpected filesystem corruption - hit the power button to suspend the laptop and put it in your suitcase. Take a flight and find it dead and corrupt on arrival. This bug causes lost work - Suspend the laptop, suspend fails, work you didn't save is lost because the system unexpectedly loses power. This bug causes permanent degradation of laptop batteries - Power policy set to power off at 20% capacity to extend laptop battery. Fails, battery is drained until it is flat, resulting in permanent damage and reduced capacity. This bug causes security violations - Suspend the laptop. Suspend never happens. Someone else comes and uses it because it never locked even though you hit the button. These are serious issues. The policy should be terminated immediately. Its purpose was to prevent lost work. Instead, it is causing lost work, lost hardware stability, lost security. -- 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/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806090] [NEW] package xdg-user-dirs 0.15-2ubuntu6 [modified: usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/de/LC_MESSAGES/xdg
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: xdg-user-dirs 0.15-2ubuntu6 [modified: usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo] ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Fri Nov 30 18:04:04 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: il pacchetto xdg-user-dirs non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2016-06-23 (890 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: xdg-user-dirs Title: package xdg-user-dirs 0.15-2ubuntu6 [modified: usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo] failed to install/upgrade: il pacchetto xdg-user-dirs non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-user-dirs (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/1806090 Title: package xdg-user-dirs 0.15-2ubuntu6 [modified: usr/share/locale/an/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/bs/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/de/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/eu/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/gd/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/id/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/is/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/jv/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/kn/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/kw/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/mr/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/ne/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/nl/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/pl/LC_MESSAGES/xdg-user-dirs.mo usr/share/locale/si/LC_MESSAGES/xdg-user-dirs.mo] failed to install/upgrade: il pacchetto xdg-user-dirs non è pronto per la configurazione impossibile configurarlo (stato corrente "half- installed") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1806090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers
Yes. grep lpadmin /etc/group lpadmin:x:116:casey -- 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/1805438 Title: Print settings present two distinct interfaces for adding printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers
Is your user account in the lpadmin group in /etc/group (this is default for the first user created during installation)? -- 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/1805438 Title: Print settings present two distinct interfaces for adding printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers
Thanks for your followup. journalctl | grep cups-pk-helper yields exactly two entries from that day: Nov 26 11:08:22 localhost.localdomain gnome-control-c[27707]: cups-pk-helper: addition of printer 1002 failed: client-error-not-authorized Nov 26 16:33:53 localhost.localdomain gnome-control-c[7361]: cups-pk-helper: addition of printer 1002 failed: client-error-not-authorized I can consistently reproduce this behavior. If I try to add another printer the same error results and yields the journalctl entry Nov 30 07:41:32 localhost.localdomain gnome-control-c[13550]: cups-pk- helper: addition of printer 958_small failed: client-error-not- authorized Is there a way to run cups-pk-helper in a verbose or debugging mode? -- 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/1805438 Title: Print settings present two distinct interfaces for adding printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749672] Re: [MIR] xdg-desktop-portal
** Also affects: xdg-desktop-portal (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1749672 Title: [MIR] xdg-desktop-portal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
So, i changed the language to english on my machine, but the same thing happens, it just won't load the page. And yes, i used the same machine to run the VM. I'm downloading the 18.10 ISO to install in a VM and see if it loads there. But this is a interesting situation, because it loads in a VM (at least in "disco"), but not the real machine. I'm going to test it on the new 18.10 VM and post any new comments here. -- 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/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
I should note that the page does "load", but it takes around 4 to 5
minutes to get anything on the screen. After the wait, when something
shows in the screen, I type my username, and proceed to type my password
it says that an error has ocurred. On the VM ("disco" VM) there is no
wait time, and everything happens without a hitch. I'll test now with
the "cosmic" VM.
--
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/1805426
Title:
Not able to log in into Google Account, aswell as Microsoft account
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805426/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers
For cups-pk-helper problems we need appropriate log files, as Sebastien already asked for. For the buttons, the "Additional printer settings" is not for adding printers but for getting into an advanced interface (system-config- printer). Perhaps one could rename it into "Advanced printer settings"? The "Add a printer..." in the center of the screen only appears if there is no printer set up at all. The "Add" button at the top is always there, to be able to add more printers when there is already at least one set up. I do not know whether one could improve the design here. I would leave this to the GUI experts. -- 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/1805438 Title: Print settings present two distinct interfaces for adding printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)
The ppa is maintained by Ubuntu GNOME and not an official Ubuntu archive ** Package changed: nautilus (Ubuntu) => ubuntu-gnome -- 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/1791991 Title: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1791991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers
Thanks, that looks normal. I'm Ccing Till who looks after printing in Ubuntu, maybe he has an idea what could be wrong/why cups-pk-helper errors out. You didn't attach your journalctl log around the time of the error, could you do that, it could include clues -- 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/1805438 Title: Print settings present two distinct interfaces for adding printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
Hum, do you use the same locale in the vm? Did you try a cosmic in a VM? Disco didn't have much changes in its desktop stack yet so it would weird to have it fixed there. Could have to do with the translations maybe? Could you try on your machine by switching the language to english? -- 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/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
I`m now running a virtual machine with "disco" and i`ve been able to connect all of my accounts without a problem. This bug seems to be affecting mainly "cosmic" (I don't know about "bionic"). So, it seems like the issue has been fixed on "disco", or my install of "cosmic" has a problem. But it is interesting that this is affecting some colleagues of mine, so it looks like the issue is not on my install of "cosmic". ** Also 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/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
** Also affects: hwdata (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gnome-desktop3 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity-settings-daemon (Ubuntu Trusty) Status: New => Invalid ** Changed in: hwdata (Ubuntu Xenial) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: hwdata (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: hwdata (Ubuntu Bionic) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: hwdata (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: hwdata (Ubuntu Cosmic) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: hwdata (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: hwdata (Ubuntu Trusty) Importance: Undecided => Low ** Changed in: hwdata (Ubuntu Trusty) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: gnome-desktop3 (Ubuntu Trusty) Importance: Undecided => Low ** Changed in: gnome-desktop3 (Ubuntu Trusty) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: gnome-desktop3 (Ubuntu Trusty) Status: New => In Progress ** Changed in: hwdata (Ubuntu Trusty) Status: New => In Progress ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)
Does the thumnailer still work on 32 bit with nautilus 3.30 from this ppa: https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/nautilus330/ If it does not then it's better to file a bug in debian. -- 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/1791991 Title: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
** Description changed:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
- Installed: 3.18.1.2-1ubuntu1.16.04.1
- Candidate: 3.18.1.2-1ubuntu1.16.04.1
- Version table:
- *** 3.18.1.2-1ubuntu1.16.04.1 500
- 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
- 100 /var/lib/dpkg/status
- 3.18.1.2-1ubuntu1 500
- 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ Installed: 3.18.1.2-1ubuntu1.16.04.1
+ Candidate: 3.18.1.2-1ubuntu1.16.04.1
+ Version table:
+ *** 3.18.1.2-1ubuntu1.16.04.1 500
+ 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
+ 100 /var/lib/dpkg/status
+ 3.18.1.2-1ubuntu1 500
+ 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
-
I've been having this issue sice before 14.04, which I recently upgraded
(fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the session
with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm pretty
sure that Chrome is doing something else of what i've found out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
-array [
- object path "/org/gnome/SessionManager/Inhibitor1686"
-]
- $ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
+ array [
+ object path "/org/gnome/SessionManager/Inhibitor1686"
+ ]
+ $ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
- $ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
+ $ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60 (1
minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open. No
matter the inhibitor is present or not.
-
I'm not sure where to go on. If it's a Chrome bug it must be using other
mechanisms to prevent the idle timeout. Any ideas on what to look for?
Julian.
--
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/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
** Description changed: + [Impact] + When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. + + [Test Case] + 1. Make sure ubuntu-dock is enabled + 2. Enable dash-to-dock too + 3. Lock the screen + 4. Make sure the dock does not appear on the lock screen + 5. Make sure there is no warning is the journal + + [Possible Regressions] + Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. + + [Original Bug] + After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) - --- + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805148] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1805148/+attachment/5217661/+files/ProcCpuinfoMinimal.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805148 Title: [radeon] Lock screen corrupt since upgrade to 18.04.01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805148] Re: [radeon] Lock screen corrupt since upgrade to 18.04.01
apport information ** Description changed: Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this laptop (an HP 6910p) became corrupt. When logged in and using the system, video display is fine, but the lock screen is consistently garbled as in the attached photo. Switching to Wayland made no difference in this behavior. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-01-23 (1038 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + GsettingsChanges: + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + InstallationDate: Installed on 2016-01-23 (1041 days ago) + InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + Package: mesa + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 + Tags: bionic wayland-session + Uname: Linux 4.15.0-39-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-14 (107 days ago) + UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1805148/+attachment/5217660/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805148 Title: [radeon] Lock screen corrupt since upgrade to 18.04.01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
** Also affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768996] Re: Nautilus "Software caused connection abort" when copying file from smb share
I have a similar issue but some slight differences. For example: gio copy file.log smb://1.10.2.1/folder/ gio: file:///home/user/file.log: Network dropped connection on reset When I copy, I get this error. On an old Linux Mint, I had the same issue and rolling samba back to 4.3.9 fixed it. My hard disk is connected to a D-Link DIR-636L. -- 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/1768996 Title: Nautilus "Software caused connection abort" when copying file from smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
Okay. Looks like this is the case for mutter-3.30.1. In the current
version in bionic mutter-3.28.3, I don't see "Wayland EGLStream:
${have_wayland_eglstream}" option in configure.
--
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/1805444
Title:
[nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with
EGLDevice backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
Yes, Ubuntu builds with EGLDevice support always enabled. But you can't explicitly select the "Wayland EGLStream" option - that's automatically detected. -- 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/1805444 Title: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805444] Re: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
I think on aarch64 mutter is compiled with EGLDevice backend enabled. I have opened this bug NVIDIA Tegra SoC. -- 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/1805444 Title: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805444] Re: Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
** Tags added: nvidia ** Summary changed: - Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend + [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend -- 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/1805444 Title: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805444] Re: Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
The bigger problem (than any missing commits) is that Ubuntu builds of mutter don't support EGLStreams: mutter-3.30.1 prefix: /usr/local source code location: . compiler: gcc Startup notification: yes libcanberra: yes libwacom: yes gudev yes Introspection:yes Session management: yes Wayland: yes Wayland EGLStream:no <-- Native (KMS) backend: yes EGLDevice:yes Remote desktop: no I think the missing build-dep isn't even in main. I can only find it in https://github.com/NVIDIA/egl-wayland but would love to be proven wrong. This is a problem on Ubuntu even when building upstream mutter with the "missing" commits. The required file wayland-eglstream-protocols.pc and friends is still missing from the Ubuntu distro. -- 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/1805444 Title: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805444] Re: Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend
... so even when you do get EGLDevice working, you don't have EGLStreams and so will be stuck with software rendering. -- 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/1805444 Title: [nvidia] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
