[Bug 1786757] Re: screencast no output on 3 display monitor
and then tell us the ID of the new bug. -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
Thanks. Your desktop size of 4880x1085 is likely the factor here. I find that surprising because apparently the AMD Cedar GPU shouldn't max out until textures reach 16384x16384 [1]. Maybe it's a video encoding limitation then, such as [2] [3]. The Gnome shell developers might know already, so please report the bug to them at: https://gitlab.gnome.org/GNOME/mutter/issues [1] https://www.x.org/wiki/RadeonFeature/ [2] https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels [3] https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding#Tiers_and_levels -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730281] Re: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen
*** This bug is a duplicate of bug 1725384 *** https://bugs.launchpad.net/bugs/1725384 See also https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1765356 -- 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/1730281 Title: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
See attached glxinfo ** Attachment added: "glxinfo output" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+attachment/5174973/+files/glxinfo -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
See attached xrandr output ** Attachment added: "xrandr output" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+attachment/5174972/+files/xrandr -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
I'm using the built-in screencast by pressing CTRL+ALT+SHIFT+R -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776916] Re: gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 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/1776916 Title: gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open files] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1776916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755536] Re: gnome-control-center is not open ubuntu 18.04
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1755536 Title: gnome-control-center is not open ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755536/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
Please also run these commands and send us the output: glxinfo xrandr -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786883] Re: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland
** Attachment added: "journal3.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1786883/+attachment/5174971/+files/journal3.txt ** Summary changed: - [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland + [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. No Wayland login option. -- 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/1786883 Title: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. No Wayland login option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
When you say "screencast" what tool are you using there? -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
Monitor 1 1600 x 900 VGA Monitor 2 1600 x 900 VGA Monitor 3 1680 x 1050 DVI -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786883] [NEW] [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland
Public bug reported: The cosmic login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. I can tell because from ssh user 'gdm' is running: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 and not the usual Xwayland. Also the login screen offers no choice of Xorg or Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.29.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Tue Aug 14 11:41:31 2018 InstallationDate: Installed on 2018-05-26 (79 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: High Status: New ** Affects: mutter (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug cosmic regression ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Tags added: regression -- 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/1786883 Title: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786883] Re: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland
** Attachment added: "journal2.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1786883/+attachment/5174970/+files/journal2.txt -- 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/1786883 Title: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786883] Re: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland
In both cases I see: Aug 14 11:40:46 kab gnome-shell[890]: X Wayland crashed; exiting Aug 14 11:49:16 kab gnome-shell[890]: X Wayland crashed; exiting which would explain why the Wayland option is missing when I finally get a login screen. Unfortunately there are no crash files or core dumps :( -- 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/1786883 Title: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786883] Re: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1786883/+attachment/5174967/+files/journal.txt ** Description changed: The cosmic login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland. I can tell because from ssh user 'gdm' is running: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 - and not the usual Xwayland. + and not the usual Xwayland. Also the login screen offers no choice of + Xorg or Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.29.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Tue Aug 14 11:41:31 2018 InstallationDate: Installed on 2018-05-26 (79 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_AU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash SourcePackage: gdm3 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1786883 Title: [regression] Login screen flickers to black a few times on boot and then finally settles on using Xorg instead of Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786872] Re: [regression] Cosmic login screen never appears on about 50% of boots
Incomplete. Since I logged this bug gdm3 has upgraded and I get bug 1786883 instead. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1786872 Title: [regression] Cosmic login screen never appears on about 50% of boots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1786757/+attachment/5174969/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
apport information ** Tags added: apport-collected bionic ** Description changed: - Ubuntu 18 shows only black output on 3 monitor display screencast. I'm - using desktop with videocard with 3 display output (HDMI, VGA, DVI). On - dual monitor, screecast works fine while on 3 monitors the output is - only black screen. + Ubuntu 18 shows only black output on 3 monitor display screencast. I'm using desktop with videocard with 3 display output (HDMI, VGA, DVI). On dual monitor, screecast works fine while on 3 monitors the output is only black screen. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + 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 2018-06-08 (66 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_PH.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1786757/+attachment/5174968/+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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786881] Re: Languages always shown with English names
** Summary changed: - Languages always shown with english names + Languages always shown with English names -- 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/1786881 Title: Languages always shown with English names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786881] [NEW] Languages always shown with english names
Public bug reported: [Impact] Selecting a language from Settings always shows the names in English (e.g. German) instead of the name in the native language (e.g. Deutsch). [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: A list of languages is available, using the native language for each item, e.g. "English, Deutsch, ..." Observed result: A list of languages is available, using the English translations for each item, e.g. "English, German, ..." ** Affects: gnome-control-center (Ubuntu) Importance: Medium Status: Triaged ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium -- 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/1786881 Title: Languages always shown with english names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786880] Re: Changing language doesn't show previously selected language
This seems due to the 0010-set-language.patch in accountsservice. It means when Settings chooses a locale (e.g. en_US.UTF-8) this is changed to en_US in accountsservice. When Settings uses this to select the current language it doesn't match against any entry. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged -- 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/1786880 Title: Changing language doesn't show previously selected language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786880] [NEW] Changing language doesn't show previously selected language
Public bug reported: [Impact] Changing language in Settings doesn't show currently selected language. [Test Case] 1. Open Settings 2. Go to "Region & Language" panel 3. Click on "Language" Expected result: The list of available languages shows the current language selected. Observed result: No languages are shown as selected. ** Affects: gnome-control-center (Ubuntu) Importance: Medium Status: Triaged -- 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/1786880 Title: Changing language doesn't show previously selected language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769221] Re: switching user fails
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 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/1769221 Title: switching user fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786851] Re: package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1774039 *** https://bugs.launchpad.net/bugs/1774039 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1774039, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1774039 package gdm3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 -- 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/1786851 Title: package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] Re: screencast no output on 3 display monitor
1. What is the resolution of your monitors? 2. Please run this command to send us more information: apport-collect 1786757 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786046] Re: Bypass Login Screen by replugging in external monitors
** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High -- 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/1786046 Title: Bypass Login Screen by replugging in external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786046/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
Interesting. That sounds similar to bug 1786872. Are you sure your bug title is correct? "Screen randomly turns black minutes after successfully login with GDM" Have you really logged in with your username and password *before* the bug occurs? Or do you just mean the machine has booted when you say "login"? ** Tags added: nvidia ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver
I've tracked down the offending source code: https://gitlab.gnome.org/GNOME/gtk/blob/master/gdk/x11/gdkmain-x11.c#L242 and unfortunately it will just exit without leaving a crash or dump file :( Just an idea: Please try this to see if it stops the problem from happening: sudo apt remove mesa-va-drivers gstreamer1.0-vaapi If that doesn't fix it then the next step I think is to ask for help from the Totem developers. So please open a new "issue" here: https://gitlab.gnome.org/GNOME/totem/issues -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1780475 Title: Fatal IO error 11 on totem startup when using the Nvidia binary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
xfce4 (Ubuntu) → Invalid means that Theo believes this bug is not a bug in xfce4. But it is still a bug in another component(s). See that task and others at the top of the page. -- 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/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
It looks like the upstream bug is actually: https://github.com/micheleg/dash-to-dock/issues/196 ** Tags added: artful bionic ** Bug watch added: github.com/micheleg/dash-to-dock/issues #196 https://github.com/micheleg/dash-to-dock/issues/196 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/196 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765356] Re: "Show Applications" button triggers too often on touchscreen
*** This bug is a duplicate of bug 1725384 *** https://bugs.launchpad.net/bugs/1725384 Sorry, I forgot the Ubuntu dock is a separate component. Now I look at the Ubuntu dock bugs this sounds like bug 1730281, which is presently marked as a duplicate of bug 1725384. So this bug should probably be merged with those. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** This bug has been marked a duplicate of bug 1725384 On touch screens, the apps icon in the dock does not open when touched -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1765356 Title: "Show Applications" button triggers too often on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786872] [NEW] [regression] Cosmic login screen never appears on about 50% of boots
Public bug reported: In the past week or two, cosmic has failed to finish booting in about half of all cases (on multiple machines). The problem is that the graphical login screen never appears. Instead the machine stays on a text console. WORKAROUND: I can force the system to finish booting and make the login screen appear just by switching VTs and back: Ctrl+Alt+F4, Ctrl+Alt+F1 Then within a second or so the login screen appears. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Tue Aug 14 09:19:45 2018 InstallationDate: Installed on 2018-05-26 (79 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug cosmic regression -- 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/1786872 Title: [regression] Cosmic login screen never appears on about 50% of boots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
What does "status: invalid" mean? In XFCE > Settings > Additional Drivers > Additional Drivers, it's currently set to "NVIDIA Corporation GF106M [GeForce GTX 460M] "[x] Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested)". Other options are "[ ] Using NVIDIA bindary driver - version 340.106 from nvidia-340 (proprietary)" and "[ ] Using X.Org server - Nouveau display driver from xserver-xorg-video-nouveau (open source)" Tried to install nvidia-340, but it cocked up and left the system in a bad state. I couldn't even revert to nvidia-driver-390 without doing a lot of "apt --fix-broken install ... dpkg-divert --remove" loops. Installed the nouveau driver, doesn't send output to the primary display, had to plug in a second display. (???) used "xfwm4-tweaks-settings" to make sure Compositing is turned on. Started "totem vapourwave.mp4" and... no transparency. does_not_reproduce NVIDIA website says the latest "long lived" (stable?) version is 390.77 (2018-07-16). https://www.nvidia.com/Download/driverResults.aspx/136120/en-us . It won't let me install it because of the kernel modules already installed, which I can't remove with modprobe nor rmmod because "resource is in use" despite no dependencies and I already stopped X.Org. I'll keep trying. Looking like it's a bad interaction between Totem and the NVIDIA proprietary driver (nvidia-driver-390). Weird that the other video players, even the gstreamer-based ones, don't suffer the same problem. -- 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/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
Looks like the next step would be to test with an older NVIDIA driver version from the Ubuntu repository, and maybe with the slightly newer version 390.77 from the NVIDIA website also. ** Changed in: xfce4 (Ubuntu) Status: Incomplete => Invalid -- 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/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786851] [NEW] package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Public bug reported: Ubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: gdm3:amd64: Install libgdm1:amd64: Install gir1.2-gdm-1.0:amd64: Install libarchive13:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Aug 13 17:45:09 2018 DuplicateSignature: package:gdm3:3.28.2-0ubuntu1.4 Setting up gdm3 (3.28.2-0ubuntu1.4) ... dpkg: error processing package gdm3 (--configure): installed gdm3 package post-installation script subprocess returned error exit status 10 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-03-14 (152 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1786851 Title: package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786851] Re: package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- 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/1786851 Title: package gdm3 3.28.2-0ubuntu1.4 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
I didn't try 'marco' because I didn't know what that is. Installing it now. totem used with 'marco' and 'compton' are not washed out, but strangely transparent. See attached image for 'marco' -- compton is the same just no messages on stderr from compton. ** Attachment added: "totem.with.marco.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1767711/+attachment/5174902/+files/totem.with.marco.png -- 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/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783311] Re: Upgrade to 3.28.3 and SRU it
Marc, do you have logs for journalctl /usr/bin/gnome-shell when this happens? Anyway feel free to open a bug for that. -- 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/1783311 Title: Upgrade to 3.28.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1783311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
I suggested to test with MATE's compositing window manager "marco" also. Any results? Another test case would be to use xfwm4 with disabled compositor plus "compton" (standalone compositing manager). -- 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/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package libreoffice - 1:5.1.6~rc2-0ubuntu1~xenial4 --- libreoffice (1:5.1.6~rc2-0ubuntu1~xenial4) xenial; urgency=medium * debian/libreoffice-mysql-connector.triggers.in, debian/libreoffice-wiki-publisher.triggers.in: - removed, file path triggers do not need to be activated explicitly * debian/libreoffice-common.triggers.in: switch to -noawait trigger (LP: #1780996) -- Olivier Tilloy Fri, 03 Aug 2018 13:00:22 +0200 ** Changed in: libreoffice (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.24 --- ubuntu-release-upgrader (1:18.04.24) bionic; urgency=medium * DistUpgradeController.py: Remove an unnecessary debugging entry when calculating the debs to remove. ubuntu-release-upgrader (1:18.04.23) bionic; urgency=medium * Upgrade libc6 before other packages to work around trigger issues (LP: #1766890) -- Brian Murray Thu, 09 Aug 2018 10:54:40 -0700 ** Changed in: ubuntu-release-upgrader (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764779] Re: Nautilus crashed open Windows-partition
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/glib2.0/+git/glib2.0/+merge/353003 -- 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/1764779 Title: Nautilus crashed open Windows-partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib/+bug/1764779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Update Released
The verification of the Stable Release Update for ubuntu-release- upgrader has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712661] Re: gnome-shell crash using ubuntu-dock with dual monitors
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1712661 Title: gnome-shell crash using ubuntu-dock with dual monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1712661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
Hello Ferdinand, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
Hello Leon, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767956] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monit
Hello errors.ubuntu.com, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767956 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monitor_manager() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal
Hello Marco, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784398 Title: Changing monitor settings crashes on meta_window_wayland_move_resize_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783311] Please test proposed package
Hello Marco, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1783311 Title: Upgrade to 3.28.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1783311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro
Hello Jimmy, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: mutter (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1422253/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
Hello Rachel, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784671] Re: Keeping Alt+Space pressed shows the window menu and then minimizes the window
Indeed, that was fixed in gnome-shell 3.29.4 while in cosmic we've 3.29.90 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- 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/1784671 Title: Keeping Alt+Space pressed shows the window menu and then minimizes the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
There is a fundamental difference between search (what you do when you don't know where something is) and navigate (what you do when you know exactly where something is, and want to go there). Why the gnome team have chosen to conflate them, and their mental state while doing so, is anyone's guess. But from a usability perspective, it is broken. -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I also did some more verification with the graphical frontend and the apt-clone file restored, and it worked perfectly well, with libc6 upgraded first. Progress reporting was a bit weird as it went to 100% for the libc stuff, and then down again, but it could be worse. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782681] Re: Upgrade to 3.26.4 and SRU it
Since this versioning was used in some other packages, I've used this, but if you prefer another versioning we can change that. I've not strong opinions on that, just I find this more readable. -- 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/1782681 Title: Upgrade to 3.26.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786792] [NEW] Nautilus does not have option to change properties of symbolic link
Public bug reported: Steps to reproduce: 1. have `file1` somewhere 2. make symbolic link to `file1` as `symlink1` (for example with Nautilus: Create Link or ) 3. rename `file1` to new name (now `symlink1` is broken) 4. try to edit `symlink1` properties to point to the new name Expected results: * Nautilus allows to change properties of the symbolic link Actual results: * Nautilus does not allow to change properties of the symbolic link ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 13 17:49:20 2018 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+268+38'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-04-28 (106 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic cosmic trusty xenial -- 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/1786792 Title: Nautilus does not have option to change properties of symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
> I can't completely understand what GNOME developers are trying to achieve! > 18.04 LTS and 18.10 are trying to perform search after entering first letter. The underlying assumption seems to be that when you type the name of a file, the only thing you may possibly want is to search for that file, and that if the search is recursive within subdirectory, that's even better, and that the only reason you may not want that, is because a recursive search can become slow; but since they have optimized search so much that it is always instant-fast (or so they claim), then who wouldn't want Nautilus to just start searching recursively and instantly showing you the search results as you type? Genius, right? Wrong. Becaue even assuming a recursive search in a bazillion files could be performed in a nanosecond, that is not necessarily what we want when we type a partial filename. Many of us just want to SELECT a file within the current directory while still viewing all of its contents and not just the matching file/s. Perhaps you want to simply SPOT that file and select other ones that are near to it, or actually select that one but also other ones. When you want to do a search, which is a completely different thing, you can do Ctrl+F. -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767431] Re: restore type-ahead find, again
*** This bug is a duplicate of bug 1164016 *** https://bugs.launchpad.net/bugs/1164016 ** This bug has been marked a duplicate of bug 1164016 restore type-ahead find -- 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/1767431 Title: restore type-ahead find, again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728184] Re: mozjs38 is no longer supported by Mozilla
** No longer affects: 0ad (Ubuntu) ** No longer affects: libproxy ** No longer affects: libproxy (Ubuntu) ** No longer affects: cjs (Ubuntu) ** Project changed: cinnamon-project => cjs (Ubuntu) ** Changed in: cjs (Ubuntu) Importance: Unknown => Undecided ** Changed in: cjs (Ubuntu) Status: Fix Released => New ** Changed in: cjs (Ubuntu) Remote watch: github.com/linuxmint/cjs/issues #52 => None ** No longer affects: cjs (Ubuntu) ** Summary changed: - mozjs38 is no longer supported by Mozilla + Please remove mozjs38 from Ubuntu ** Description changed: mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It has not been supported by Mozilla since June 2016. - Please migrate to mozjs52, the only version currently supported by - Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in - Debian Testing. + Now that nothing in Ubuntu 18.10 "cosmic" depends on it, please remove + mozjs38 from Ubuntu. - Currently these packages depend on mozjs38 - -- - 0ad (embedded code copy) - cjs - libproxy1-plugin-mozjs - - https://github.com/linuxmint/cjs/issues/52 - https://github.com/libproxy/libproxy/issues/71 + For reference, we expect to ship Ubuntu 18.10 with mozjs60 and mozjs52. + Cinnamon's cjs uses mozjs52 and I don't expect it to be ported to + mozjs60 in time for 18.10's release. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mozjs38 in Ubuntu. https://bugs.launchpad.net/bugs/1728184 Title: Please remove mozjs38 from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1728184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786591] Re: password mode: save greyed out if certificate is not chosen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Sounds like this is a problem with the Network Manager OpenVPN plugin rather than OpenVPN itself, so I'm retasking the bug. ** Package changed: openvpn (Ubuntu) => network-manager-openvpn (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1786591 Title: password mode: save greyed out if certificate is not chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1786591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786591] [NEW] password mode: save greyed out if certificate is not chosen
You have been subscribed to a public bug: When: adding a new VPN connection under: VPN type "Password" Problem: the "Save" button remains greyed out unless a "CA Certificate" is chosen. Expected solution: a way to disable the "CA Certificate" setting. Comments: My VPN provider (TU Darmstadt) does not require a certificate, only a name/password pair. On the corresponding Network Manager tab, there is no way to disable the CA Certificate. The "Save" button remains grayed out unless some "CA Certificate" is chosen. As a test, I attempted to add a certificate from another connection. The button was then accessible, but the connection could not be established. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openvpn 2.3.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Aug 11 09:02:54 2018 InstallationDate: Installed on 2018-07-05 (36 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- password mode: save greyed out if certificate is not chosen https://bugs.launchpad.net/bugs/1786591 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
I can't completely understand what GNOME developers are trying to achieve! This functionality was used for years. Ubuntu 14.04 LTS and 16.04 are not affected. But 18.04 LTS and 18.10 are trying to perform search after entering first letter. The patch for Nautilus in 18.04 LTS is available (see https://askubuntu.com/q/275883/66509 and https://launchpad.net/~lubomir-brindza/+archive/ubuntu/nautilus-typeahead ). -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
Sorry, but I forgot one thing. When the screen turns black, I can recover the graphical session switching between a virtual console and the console that is supporting the graphical session with alt+control+f5 and alt+control+f2 or alt+control+f1. No issues with nomodeset so far. -- 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/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
** Tags added: bionic cosmic -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767431] Re: restore type-ahead find, again
** Tags added: bionic cosmic -- 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/1767431 Title: restore type-ahead find, again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Merge proposal linked: https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352976 -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765356] Re: "Show Applications" button triggers too often on touchscreen
Here is their answer: > The default Ubuntu session is not upstream GNOME. In particular > the dash is replaced with a Unity-style dock, so please test > with the non-default "pure GNOME" session first. Can the team at Canonical that deals with the Unity-style dock verify the behavior is not introduced by their code? -- 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/1765356 Title: "Show Applications" button triggers too often on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Merge proposal linked: https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352976 -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Merge proposal linked: https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352973 -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Merge proposal linked: https://code.launchpad.net/~dgadomski/ubuntu/+source/gdm3/+git/lp1782152/+merge/352973 -- 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/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786694] Re: calendar applet doesn't connect with google
Can you clarify what applet? Can you take photo and attach it here please. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1786694 Title: calendar applet doesn't connect with google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1786694/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786046] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1786046/+attachment/5174712/+files/ProcCpuinfoMinimal.txt -- 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/1786046 Title: Bypass Login Screen by replugging in external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786046/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786046] Re: Bypass Login Screen by replugging in external monitors
apport information ** Tags added: apport-collected bionic ** Description changed: I found a bug in ubuntu At the login screen buster/sid Linux 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I use my work laptop and today when I came back to office I connected both my external monitor. 1 HDMI cable and 1 Mini display port cable. Then I realize one screen on the right had my login screen prompting for password and the left monitor was unlock, I was able to navigate the mouse and use the computer just fine. However all the keyboard input was sent to the password prompt. I did the test a couple time and each time I was able to reproduce the issue. #1: Lock the computer #2: Disconnect both external monitor #3: Reconnect external monitor ( my sequence was HDMI -> Display port ) #4: You've bypass the login screen. When doing the demo to my colleague I was able to completely bypass the login screen on both screen and had complete mouse and keyboard input. At that time I was not able anymore to lock my session. I had to reboot the laptop. Laptop model: Manufacturer: LENOVO Product Name: 20FN002VCA Version: ThinkPad T460 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-30 (104 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: gdm3 3.28.2-0ubuntu1.3 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_CA + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1786046/+attachment/5174711/+files/Dependencies.txt -- 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/1786046 Title: Bypass Login Screen by replugging in external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786046/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765356] Re: "Show Applications" button triggers too often on touchscreen
GNOME Shell bug #480 created, https://gitlab.gnome.org/GNOME/gnome- shell/issues/480 -- 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/1765356 Title: "Show Applications" button triggers too often on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
I just had this on 18.04 after applying this upgrade via software- updater. At least I think that's the cause. Start-Date: 2018-08-13 08:00:02 Commandline: aptdaemon role='role-commit-packages' sender=':1.123' Install: linux-image-4.15.0-30-generic:amd64 (4.15.0-30.32, automatic), linux-headers-4.15.0-30:amd64 (4.15.0-30.32, automatic), linux-modules-extra-4.15.0-30-generic:amd64 (4.15.0-30.32, automatic), linux-modules-4.15.0-30-generic:amd64 (4.15.0-30.32, automatic), linux-headers-4.15.0-30-generic:amd64 (4.15.0-30.32, automatic) Upgrade: ca-certificates-java:amd64 (20170930ubuntu1, 20180516ubuntu1~18.04.1), xserver-xorg-input-all:amd64 (1:7.7+19ubuntu7, 1:7.7+19ubuntu7.1), xserver-xorg:amd64 (1:7.7+19ubuntu7, 1:7.7+19ubuntu7.1), libvte-2.91-0:amd64 (0.52.2-1ubuntu1~18.04.1, 0.52.2-1ubuntu1~18.04.2), intel-microcode:amd64 (3.20180425.1~ubuntu0.18.04.1, 3.20180425.1~ubuntu0.18.04.2), linux-headers-generic:amd64 (4.15.0.29.31, 4.15.0.30.32), linux-libc-dev:amd64 (4.15.0-29.31, 4.15.0-30.32), python3-wadllib:amd64 (1.3.2-3, 1.3.2-3ubuntu0.18.04.1), linux-image-generic:amd64 (4.15.0.29.31, 4.15.0.30.32), snapd:amd64 (2.33.1+18.04ubuntu2, 2.34.2+18.04), lshw:amd64 (02.18-0.1ubuntu6, 02.18-0.1ubuntu6.18.04.1), google-chrome-stable:amd64 (68.0.3440.75-1, 68.0.3440.84-1), console-setup-linux:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), console-setup:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), amd64-microcode:amd64 (3.20180524.1~ubuntu0.18.04.1, 3.20180524.1~ubuntu0.18.04.2), linux-signed-generic:amd64 (4.15.0.29.31, 4.15.0.30.32), liblxc1:amd64 (3.0.1-0ubuntu1~18.04.1, 3.0.1-0ubuntu1~18.04.2), gir1.2-vte-2.91:amd64 (0.52.2-1ubuntu1~18.04.1, 0.52.2-1ubuntu1~18.04.2), guile-2.0-libs:amd64 (2.0.13+1-5build2, 2.0.13+1-5ubuntu0.1), libmspack0:amd64 (0.6-3, 0.6-3ubuntu0.1), xserver-xorg-video-all:amd64 (1:7.7+19ubuntu7, 1:7.7+19ubuntu7.1), xorg:amd64 (1:7.7+19ubuntu7, 1:7.7+19ubuntu7.1), libmysqlclient20:amd64 (5.7.22-0ubuntu18.04.1, 5.7.23-0ubuntu0.18.04.1), keyboard-configuration:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), libvte-2.91-common:amd64 (0.52.2-1ubuntu1~18.04.1, 0.52.2-1ubuntu1~18.04.2), x11-common:amd64 (1:7.7+19ubuntu7, 1:7.7+19ubuntu7.1), liblxc-common:amd64 (3.0.1-0ubuntu1~18.04.1, 3.0.1-0ubuntu1~18.04.2), linux-generic:amd64 (4.15.0.29.31, 4.15.0.30.32) End-Date: 2018-08-13 08:01:14 Solved by rebooting. sudo dumpkeys |grep -E '^(\W+)alt(\W+)keycode (105|106) = (Incr|Decr)_Console' still shows the entries after reboot, but Alt+Left/right doesn't switch vt anymore. -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782681] Re: Upgrade to 3.26.4 and SRU it
...I actually see this is some versioning scheme used by the desktop team for gnome-related packages (just saw it in mutter as well). Seeing that Robie approved of uploads with this versioning fir mutter, I suppose you can re-upload it without changing the version number... -- 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/1782681 Title: Upgrade to 3.26.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786757] [NEW] screencast no output on 3 display monitor
Public bug reported: Ubuntu 18 shows only black output on 3 monitor display screencast. I'm using desktop with videocard with 3 display output (HDMI, VGA, DVI). On dual monitor, screecast works fine while on 3 monitors the output is only black screen. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: screencast -- 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/1786757 Title: screencast no output on 3 display monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver
I've done that and the bug still occurs, but it doesn't generate any core or crash file. -- 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/1780475 Title: Fatal IO error 11 on totem startup when using the Nvidia binary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783364] Re: Preference 'recursive-search' is ignored when set to 'never'
Anyone? This is clearly a bug in Nautilus -- 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/1783364 Title: Preference 'recursive-search' is ignored when set to 'never' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1783364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765356] Re: "Show Applications" button triggers too often on touchscreen
Yes. To escalate the issue please report it to the Gnome developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new bug ID. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765356 Title: "Show Applications" button triggers too often on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782681] Re: Upgrade to 3.26.4 and SRU it
Is there any reason why suddenly the version number for the SRU is 1:3.26.4-0~ubuntu18.04.1 ? Not sure we ever had a scheme like this before. To me it seems like the security-team's versioning of 1:3.26.4-0ubuntu0.18.04.1 would fit better and be more consistent with what we have in other series. If there is a specific reason for that, please mention it here and re- upload. If not, I would like to request changing the version number and re-uploading. Usually I change versioning myself and re-upload during review, but I have been informed that for desktop packages this interferes with some internal tooling, so rejecting this instead. If there is no specific reason for the versioning and you do *not* wish to change the versioning scheme, please find a different SRU member who might have a different opinion. -- 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/1782681 Title: Upgrade to 3.26.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782681] Re: Upgrade to 3.26.4 and SRU it
** Also affects: nautilus (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1782681 Title: Upgrade to 3.26.4 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765356] Re: "Show Applications" button triggers too often on touchscreen
Can we escalate this issue somehow? Where does it have to be fixed? Upstream? What about certification? Can that help to escalate the issue? - https://certification.ubuntu.com/hardware/201712-26045/ (ThinkPad X1 Carbon 6th Generation) - https://certification.ubuntu.com/hardware/201603-20841/ (Dell Inspiron 13 2-in-1 5000 Series) - https://certification.ubuntu.com/hardware/201605-22328/ (Dell Inspiron 13 2-in-1 5000 Series) - No certification yet for ASUS T304UA 2-in-1 - No certification yet for ThinkPad Yoga 12 (S120) - No certification yet for Dell Venue 11 Pro 7140 The problem seems generic to touch screen devices in general. As long as this isn't fixed the GNOME desktop (and thus Ubuntu) isn't ready for devices equipped with touch screens, including the popular 2-in-1 convertibles. -- 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/1765356 Title: "Show Applications" button triggers too often on touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver
Sorry, I spend so much time debugging Xorg server crashes that for a moment I forgot this was about totem... Please try running the following commands before running totem: ulimit -c unlimited export GDK_SYNCHRONIZE=1 totem Hopefully the crash still occurs. Now look in either: * the current directory; or * your home directory; or * /var/crash for a new core file or crash file. When found, run: ubuntu-bug THEFILE and tell us the new bug ID created. -- 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/1780475 Title: Fatal IO error 11 on totem startup when using the Nvidia binary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
There is an ongoing bionic SRU in bionic-proposed still. Please help verifying it as without it release we can not proceed with reviewing this upload. -- 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/1775226 Title: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Also affects: nautilus (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver
Sorry Daniel, I don't understand what you need. The bug occurs immediately after I try to launch totem: juloliv@juloliv:~$ totem Gdk-Message: 10:52:39.290: totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. There is no particular "context": it crashes all the time, as soon as it's launched, and there is no log to attach that I know of. -- 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/1780475 Title: Fatal IO error 11 on totem startup when using the Nvidia binary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784522] Re: Update evolution to 3.28.5
Hello Jeremy, or anyone else affected, Accepted evolution into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution/3.28.5-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: evolution (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1784522 Title: Update evolution to 3.28.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver
OK. Can you please attach a log file showing the IO error with some more context? -- 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/1780475 Title: Fatal IO error 11 on totem startup when using the Nvidia binary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780475] Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver
I tried steps 1, 2 and 3, but it doesn't change a thing: the crash occurs, the message "totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1." is spawned in the terminal, but no .crash file is generated. -- 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/1780475 Title: Fatal IO error 11 on totem startup when using the Nvidia binary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1780475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04
The fix suggested by hgrie works for me. ibus-setup is running ibus- daemon, which immediately fixed the issue and lasts until logout. I note that adding 'ibus-daemon --xim' as a startup application is a permanent fix for the issue in my case. -- 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/1573755 Title: Compose and dead keys stopped working with XIM after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1573755/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786579] Re: If I change inputs or turn off my TV, my windows will change positions
That said, if you maximize a window then there is a reasonable argument that the status of "maximized" should stay true no matter the resolution of the output, and especially since they are so similar in resolution. It's a matter of opinion as to whether a maximized window should retain its maximized status when it's also forced to resize to fit the new resolution. So... 1. Please report the bug to the Gnome people and see what they say. If they agree to keep it open then we will too: https://gitlab.gnome.org/GNOME/gnome-shell/issues 2. As a workaround, try: (a) Keeping the window smaller; or (b) Keeping the window full screen (F11); or (c) Simulate the Nvidia case by logging into "Ubuntu" instead of "Ubuntu on Wayland". ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1786579 Title: If I change inputs or turn off my TV, my windows will change positions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786579] Re: If I change inputs or turn off my TV, my windows will change positions
If you think so. But I will say this sort of thing does not happen under Windows with the same TV/receiver, and on the same machine/TV/receiver when I was running an Nvidia card with the Nvidia proprietary drivers, it didn't do it either. Something strange must be happening here, and I opened the bug report because I lack the expertise to figure out what the deal is. I would suggest against assuming that this is desired behavior without trying to replicate it. But it's up to you. -- 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/1786579 Title: If I change inputs or turn off my TV, my windows will change positions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1786579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
