[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
** Changed in: gdm3 (Ubuntu) Status: Expired => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Won't Fix Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
Anyone using the NVIDIA driver please see bug 1870736 and bug 1873403 instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871849] Re: Firefox does not properly play full screen videos using fractional scale at 125%
** Summary changed: - [nvidia] Firefox does not properly play full screen videos using fractional scale at 125% + Firefox does not properly play full screen videos using fractional scale at 125% ** Tags removed: nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871849 Title: Firefox does not properly play full screen videos using fractional scale at 125% Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: firefox does not properly play full screen videos using fractional scale at 125% --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-29 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
Sounding more and more like a kernel bug. Especially since comment #13 mentions that it occurs in 5.5 (but not 5.4!?). ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
The above comment probably belongs in bug 1834058. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
** Changed in: gtk Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in GTK+: Fix Released Status in apport package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
** No longer affects: apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in GTK+: Fix Released Status in apport package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782962] Re: Tearing in chromium-browser video playback
I am removing Xorg from this bug. If Xorg is to blame at all then it's probably already covered by one of the other existing bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=tearing ** No longer affects: xorg-server (Ubuntu) ** Tags added: tearing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1782962 Title: Tearing in chromium-browser video playback Status in chromium-browser package in Ubuntu: New Bug description: Test video: https://youtu.be/22ftfoCSPQI Tested in chromium-browser with setting "Use hardware acceleration when available". Oh, when I use google-chrome, instead, there is no such tearing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 338350/1038352 files, 2274396/4150016 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Jul 22 08:53:00 2018 DistUpgraded: 2018-04-14 11:02:07,544 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-45-generic, x86_64: installed bbswitch, 0.8, 4.15.0-29-generic, x86_64: installed bbswitch, 0.8, 4.4.0-128-generic, x86_64: installed bbswitch, 0.8, 4.4.0-130-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:853b] InstallationDate: Installed on 2014-09-21 (1399 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) MachineType: Dell Inc. OptiPlex 745 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 ro SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-04-14 (98 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 22 08:40:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHESEN PS2 to USB Converter KEYBOARD, id 8 inputCHESEN PS2 to USB Converter KEYBOARD, id 9 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10 xserver.errors: No devices detected. Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1782962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
Oh come to think of it, there is a commonality between Firefox, VLC and Chrome. That is they all try to follow the system theme but all three are NOT GTK apps. They each use different toolkits. So I fear this is the same basic problem that will need to be fixed in three different toolkits. ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => firefox (Ubuntu) ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Also affects: vlc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
I guess you've turned off integrated titlebars, which is why I see different behaviour and no bug in Wayland sessions. ** Package changed: firefox (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791307] Re: GTK theme doesn't match the host system
** Summary changed: - [snap] GTK theme doesn't match the host system + GTK theme doesn't match the host system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1791307 Title: GTK theme doesn't match the host system Status in chromium-browser package in Ubuntu: Triaged Bug description: The GTK theme of the chrome and file open/save dialogs doesn't match the theme on the host system. See attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1791307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
See also bug 1791307 for Chromium. Perhaps these bugs need to be integrated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] [NEW] Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
You have been subscribed to a public bug: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. ** Affects: firefox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: focal -- Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) https://bugs.launchpad.net/bugs/1872844 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 409739] Re: Support http_proxy
This almost works.. it fails for me when i have a large number of files
to backup, and works fine when there's just a few. The number of files
is not consistent though, with ~2000 files it sometimes works and
sometimes doesn't.
I'm using a swift-based provider and swift itself can upload the files
using a proxy fine and very quickly. Is there a way we can just dump the
duplicity backups locally after reading them from the server and upload
them manually?
Curiously the the failure message is an SSL mismatch one from the
requests library. Looking at the packet dump when it works duplicity
uses TLS 1.2 the whole time. When it fails a "Encypted Alert" packet
arrives.
Without changing the verbosity it hangs while uploading the diff tars,
with the output: `Attempt 1 failed. ConnectionError: None`
And running duplicity with the `--verbosity d` argument gives me the
accompanying:
```
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/duplicity/backend.py",
line 374, in inner_retry
return fn(self, *args)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/duplicity/backend.py",
line 545, in put
self.__do_put(source_path, remote_filename)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/duplicity/backend.py",
line 531, in __do_put
self.backend._put(source_path, remote_filename)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/duplicity/backends/swiftbackend.py",
line 150, in _put
open(util.fsdecode(source_path.name), u'rb'))
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/swiftclient/client.py",
line 1913, in put_object
response_dict=response_dict)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/swiftclient/client.py",
line 1753, in _retry
service_token=self.service_token, **kwargs)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/swiftclient/client.py",
line 1380, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/swiftclient/client.py",
line 484, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/swiftclient/client.py",
line 472, in request
files=files, **self.requests_args)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/swiftclient/client.py",
line 453, in _request
return self.request_session.request(*arg, **kwarg)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/requests/sessions.py",
line 530, in request
resp = self.send(prep, **send_kwargs)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packiddyages/requests/sessions.py",
line 643, in send
r = adapter.send(request, **kwargs)
File
"/home/me/.virtualenvs/duplicity/lib/python3.6/site-packages/requests/adapters.py",
line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: [SSL: WRONG_VERSION_NUMBER] wrong version
number (_ssl.c:852)
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/409739
Title:
Support http_proxy
Status in Déjà Dup:
Invalid
Status in Duplicity:
Confirmed
Status in deja-dup package in Ubuntu:
Invalid
Bug description:
Binary package hint: deja-dup
I'm using my own S3 server. deja-dup does not support setting the S3 server
(i.e., it appears to be hard coded to use aws.amazon.com). Generally this is
not
a problem if the program would respect the http proxy setting, however,
deja-dup
does not appear to do this. When I run deja-dup as follows:
http_proxy=http://localhost:8080 deja-dup
it fails and I do not see any access attempts in my S3 server's logs.
Thanks.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/deja-dup
Package: deja-dup 7.4-0ubuntu2
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
SourcePackage: deja-dup
Uname: Linux 2.6.28-14-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/409739/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861409] Re: searching for irc takes more than 10 minutes
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1861409 Title: searching for irc takes more than 10 minutes Status in gnome-software package in Ubuntu: Expired Bug description: A fresh install, searching for IRC and still waiting for the results after 10 minutes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.34.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 30 10:58:56 2020 InstallationDate: Installed on 2020-01-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.34.2-1ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1861409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic
[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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic Status in gnome-shell package in Ubuntu: Expired Bug description: lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-shell gnome-shell: Installato: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidato: 3.34.1+git20191024-1ubuntu1~19.10.1 Tabella versione: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages First there was an issue with hibernation: after resuming, the gnome session was not restored and a new one was created (I had to login again from start). Here are some relevant log lines: [ 21.375254] PM: Image signature found, resuming [ 21.375255] PM: resume from hibernation [ 21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 21.376719] OOM killer disabled. [ 21.376832] PM: Marking nosave pages: [mem 0x-0x0fff] [ 21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004] [ 21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff] [ 21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f] [ 21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff] [ 21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff] [ 21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x] [ 21.377562] PM: Basic memory bitmaps created [ 24.367114] PM: Using 3 thread(s) for decompression [ 24.367115] PM: Loading and decompressing image data (1585416 pages)... [ 24.367127] Hibernate inconsistent memory map detected! [ 24.367138] fbcon: Taking over console [ 24.367139] PM: Image mismatch: architecture specific data [ 24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s) [ 24.368077] PM: Error -1 resuming [ 24.368079] PM: Failed to load hibernation image, recovering. [ 24.368347] PM: Basic memory bitmaps freed [ 24.368347] OOM killer enabled. [ 24.368347] Restarting tasks ... done. [ 24.384357] Console: switching to colour frame buffer device 240x67 [ 24.404345] PM: resume from hibernation failed (-1) Then, since next restart I cannot login anymore, as the session keeps crashing immediately after entering user's password. The only way I could login back was by selecting the previous kernel version on boot (5.3.0-26-generic instead of 5.3.0-29-generic). I also noticed all gnome extensions (Applications Menu and Hibernate Status Button ) stopped working and were disabled. Boot journal attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Expired Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863164] Re: ImportError: could not import gobject (error was: ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so: undefined symbol: PyExc_NotImp
[Expired for pygobject (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pygobject (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1863164
Title:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64
-linux-gnu.so: undefined symbol: PyExc_NotImplementedError'))
Status in pygobject package in Ubuntu:
Expired
Status in python3.8 package in Ubuntu:
Invalid
Bug description:
Steps to reproduce:
1. Install Ubuntu 20.04 LTS
2. Start first terminal with `tail -f ~/.xsession-errors`
3. Start second terminal and run `caja -q` from here
Expected results:
* there are no error messages or warnings in 1st terminl
Actual results:
* there are several error messages and warnings:
(caja:14755): Gtk-WARNING **: 22:55:26.070: Failed to register client:
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
client
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in
import apt_pkg
ImportError:
/usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_ValueError
Original exception was:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-apt 1.9.5
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 13 22:52:33 2020
InstallationDate: Installed on 2020-02-11 (1 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64
(20200211)
SourcePackage: python-apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1863164/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
Same issue, downloaded & installed iso, fractional scaling was working, it stopped working after an update, I also installed drivers for the Wifi - Broadcom BCM4352 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860428] Re: Software sources are behaving strangely when an app is available as Snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1860428 Title: Software sources are behaving strangely when an app is available as Snap Status in gnome-software package in Ubuntu: Confirmed Bug description: This happens on the latest GNOME Software 3.34.2 on Ubuntu Focal. When an app is (also) available in Snap Store, its sources showed in the "Sources" drop-down list in window header on app details page are behaving strangely: - When an app is available both in the Ubuntu repository and in Snap, default source displayed is "Ubuntu" although the actual details page displayed is for Snap version. - When clicking the drop-down list and selecting a Snap source, the Ubuntu source disappears. - When clicking the drop-down list and selecting an Ubuntu source, the whole drop-down list (so basically all Snap sources) disappears. - Default source is displayed as "Ubuntu" even for apps that are not available in Ubuntu repositories, only in Snap Store (for example the powershell). This was in GS log, however I am not sure if it is related to this issue: 12:23:31:0206 GLib g_str_has_prefix: assertion 'str != NULL' failed 12:23:31:0215 GLib g_variant_new_variant: assertion 'value != NULL' failed 12:23:31:0215 GLib g_variant_new_variant: assertion 'value != NULL' failed 12:23:31:0215 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 12:23:31:0270 Gs not handling error failed for action refine: Invalid string value converting to GVariant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869598] Re: Gnome software find only snap packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869598 Title: Gnome software find only snap packages Status in gnome-software package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 installed gnome-software 3.35.91 click on the magnify glass, enter gnome-tweaks -> no application found. Same for synaptic and gparted. gnome software is missing installing from Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) corrado@corrado-x5-ff-0329:~$ inxi -Fx System:Host: corrado-x5-ff-0329 Kernel: 5.4.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.36.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 802 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.7 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.2 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:5 Sound Server: ALSA v: k5.4.0-18-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 6.17 GiB (0.3%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 6.16 GiB (19.7%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 45.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 214 Uptime: 1h 45m Memory: 7.49 GiB used: 1.37 GiB (18.3%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.16 inxi: 3.0.38 corrado@corrado-x5-ff-0329:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 18:49:57 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-03-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873611] [NEW] format --> character menu has font preview ovelapping
Public bug reported: To reproduce open a new presentation in libreoffice impress on Lubuntu 20.04. Then in the menu open Format --> Character then for liberation sans the default font has the letters all overlapping in the font preview. I expected the letters in the font preview to not be overlapping. Instead the letters all appear overlapping in the preview but do not appear that way in the main window of libreoffice impress. libreoffice-impress: Installed: 1:6.4.2-0ubuntu3 Candidate: 1:6.4.2-0ubuntu3 Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-impress 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sat Apr 18 16:57:54 2020 InstallationDate: Installed on 2020-02-05 (73 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "impress-overlapping.png" https://bugs.launchpad.net/bugs/1873611/+attachment/5356618/+files/impress-overlapping.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1873611 Title: format --> character menu has font preview ovelapping Status in libreoffice package in Ubuntu: New Bug description: To reproduce open a new presentation in libreoffice impress on Lubuntu 20.04. Then in the menu open Format --> Character then for liberation sans the default font has the letters all overlapping in the font preview. I expected the letters in the font preview to not be overlapping. Instead the letters all appear overlapping in the preview but do not appear that way in the main window of libreoffice impress. libreoffice-impress: Installed: 1:6.4.2-0ubuntu3 Candidate: 1:6.4.2-0ubuntu3 Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-impress 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sat Apr 18 16:57:54 2020 InstallationDate: Installed on 2020-02-05 (73 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1873611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be
Ok, removing the packages works too. One thing that will happen is that if you open Language Support, it will prompt you to install those packages (which you can choose not to, of course). OTOH, I suppose you don't have a reason to open Language Support very often. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1026869 Title: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this behavior Status in Mozilla Firefox: New Status in Hunspell: New Status in myspell: New Status in firefox package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Bug description: I've been searching for the solution to this bug for a long time. Firefox's spell-check, despite my locale being en-US, sets itself to en-GB, en-ZA or something en_US, which isn't even correct. The problem, it seems, is that Firefox uses whatever spell-checking backends you have installed - aspell, myspell, and hunspell. The result is that Firefox chooses, en-GB as the default spell checker more-often than not. So I uninstalled myspell, hunspell, and a package called firefox-locale-en and now everything is correct - only one spell checker is installed in Firefox. The language selector, however, always prompts to reinstall these backends whenever it is loaded. This Firefox add-on can assist, it gives you a list of dictionaries installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary- switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1026869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Changed in: dash-to-dock Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in Dash to dock: New Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
** Also affects: pulseaudio (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
I checked on Sane supported drivers, and your device is well supported (pixma backend): http://www.sane-project.org/sane-backends.html#S-PIXMA "i-SENSYS MF240 Series Flatbed and ADF scan. All resolutions supported (up to 600DPI, ADF up to 300DPI). 216mm image width buggy, restricted to 215mm." Please install xsane and check if you could reproduce this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw Status in simple-scan package in Ubuntu: Incomplete Bug description: Hello, When scanning multiple pages from a Canon mf244dw via the LAN I only get the first page scanned, then an error message. Running "simple-scan -d" and looking at the output I see the following: [+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) -> (SANE_STATUS_CANCELLED, 0) [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: Operation was cancelled [+123.87s] DEBUG: scanner.vala:768: sane_cancel () [+123.87s] DEBUG: scanner.vala:771: sane_close () I do notice that the scanner is already feeding in the second page before the first page has completely rendered on screen - perhaps it's going too fast? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
i've just begun seeing this in debian 5.5.0-2 (linux 5.5.17-1) and 5.5.0-1 (5.5.13-1) pulseaudio -k fixes it for a while, and all i see that's relevant in the logs/dmesg is snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 0 booting back into 5.4.0-4 (5.4.19-1) and i have no problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be
Yes, that fixes it! I did this: sudo apt-get remove hunspell-en-au hunspell-en-gb hunspell-en-za -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1026869 Title: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this behavior Status in Mozilla Firefox: New Status in Hunspell: New Status in myspell: New Status in firefox package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Bug description: I've been searching for the solution to this bug for a long time. Firefox's spell-check, despite my locale being en-US, sets itself to en-GB, en-ZA or something en_US, which isn't even correct. The problem, it seems, is that Firefox uses whatever spell-checking backends you have installed - aspell, myspell, and hunspell. The result is that Firefox chooses, en-GB as the default spell checker more-often than not. So I uninstalled myspell, hunspell, and a package called firefox-locale-en and now everything is correct - only one spell checker is installed in Firefox. The language selector, however, always prompts to reinstall these backends whenever it is loaded. This Firefox add-on can assist, it gives you a list of dictionaries installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary- switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1026869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873321] Re: The Show Applications button is unclickable in the corner and along its bottom edge
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button is unclickable in the corner and along its bottom edge Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
To @kfunk @axet @troyready: That worked perfectly for me. Thank you so much!!! For those like me for whom these are all magical incantations, here's my sequence aggregated from advice above: Press the Ubuntu/Super key and type "Software" and pick the one that is called "Software & Updates". On the first tab, make sure "source code" is checked. Then, open a terminal and paste the following (line by line up to the apt line, then the rest can go together): ``` apt-get build-dep snapd TMPDIR=$(mktemp -d) cd $TMPDIR apt-get -y source snapd sed -i 's/"http", "https", "mailto", "snap", "help"/"http", "https", "mailto", "snap", "help", "apt", "zoommtg", "slack"/' snapd-*/usersession/userd/launcher.go sed -i 's/!osutil.GetenvBool(reExecKey, true)/true/' snapd-*/cmd/cmd_linux.go cd snapd-* && dch -l$(hostname) fix_missing_app_types cd .. cd snapd-* && DEB_BUILD_OPTIONS=nocheck debuild -b -uc -us cd .. sudo dpkg -i snapd_*.deb sudo service snapd restart killall snap ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
** Also affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work with secondary keyboard layout Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864274] Re: [iris regression] gfx corruption
This bug was fixed in the package mesa - 20.0.4-2ubuntu1
---
mesa (20.0.4-2ubuntu1) focal; urgency=medium
* Merge from Debian.
* disable-intel-ccs-compression.diff: Dropped, we use iris by default.
(LP: #1863874)
* Don't build with llvm-10 until ppc64el ftbfs is fixed.
mesa (20.0.4-2) unstable; urgency=medium
* fix-build-with-llvm-10.diff: Add a patch to fix build with Polly,
and build with llvm-10 again. (Closes: #956004)
* iris-drop-cache-coherent-cpu-mapping.diff: Fix corruption with iris
(Closes: #954311) (LP: #1864274)
* gallium-fix-bob-compute-shaders.diff: Fix vaapi with bob
deinterlacing. (LP: #1867188)
-- Timo Aaltonen Thu, 16 Apr 2020 09:22:34 +0300
** Changed in: mesa (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1864274
Title:
[iris regression] gfx corruption
Status in Mesa:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1863874] Re: Backport GetFB2 ioctl, re-enable CCS compression for intel
This bug was fixed in the package mesa - 20.0.4-2ubuntu1 --- mesa (20.0.4-2ubuntu1) focal; urgency=medium * Merge from Debian. * disable-intel-ccs-compression.diff: Dropped, we use iris by default. (LP: #1863874) * Don't build with llvm-10 until ppc64el ftbfs is fixed. mesa (20.0.4-2) unstable; urgency=medium * fix-build-with-llvm-10.diff: Add a patch to fix build with Polly, and build with llvm-10 again. (Closes: #956004) * iris-drop-cache-coherent-cpu-mapping.diff: Fix corruption with iris (Closes: #954311) (LP: #1864274) * gallium-fix-bob-compute-shaders.diff: Fix vaapi with bob deinterlacing. (LP: #1867188) -- Timo Aaltonen Thu, 16 Apr 2020 09:22:34 +0300 ** Changed in: mesa (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1863874 Title: Backport GetFB2 ioctl, re-enable CCS compression for intel Status in XServer: New Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Status in libdrm source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in mesa source package in Focal: Fix Released Status in xorg-server source package in Focal: Won't Fix Bug description: We need this in order to re-enable intel CCS compression, which was originally disabled in mesa to fix this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776 GetFB2 was recently added to drm-misc, and should get upstream in 5.7, but would be best to have it in focal and unstable kernel so that the userland parts can be added. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver/+bug/1863874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
This bug was fixed in the package mesa - 20.0.4-2ubuntu1 --- mesa (20.0.4-2ubuntu1) focal; urgency=medium * Merge from Debian. * disable-intel-ccs-compression.diff: Dropped, we use iris by default. (LP: #1863874) * Don't build with llvm-10 until ppc64el ftbfs is fixed. mesa (20.0.4-2) unstable; urgency=medium * fix-build-with-llvm-10.diff: Add a patch to fix build with Polly, and build with llvm-10 again. (Closes: #956004) * iris-drop-cache-coherent-cpu-mapping.diff: Fix corruption with iris (Closes: #954311) (LP: #1864274) * gallium-fix-bob-compute-shaders.diff: Fix vaapi with bob deinterlacing. (LP: #1867188) -- Timo Aaltonen Thu, 16 Apr 2020 09:22:34 +0300 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: Fix Released Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
System:Host: mint Kernel: 5.0.0-32-generic x86_64 bits: 64 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia Machine: Type: Desktop System: FUJITSU SIEMENS product: D2030-A1 v: N/A serial: Mobo: FUJITSU SIEMENS model: D2030-A1 v: S26361-D2030-A1 serial: BIOS: FUJITSU SIEMENS // Phoenix v: 5.00 R1.07.2030.A1 date: 04/21/2006 CPU: Dual Core: AMD Athlon 64 X2 4400+ type: MCP speed: 1000 MHz min/max: 1000/2200 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] driver: radeon v: kernel Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz OpenGL: renderer: llvmpipe (LLVM 8.0 128 bits) v: 3.3 Mesa 19.0.8 Network: Device-1: Realtek RTL8169 PCI Gigabit Ethernet driver: r8169 Device-2: Qualcomm Atheros AR9227 Wireless Network Adapter driver: ath9k Drives:Local Storage: total: 506.77 GiB used: 263.8 MiB (0.1%) Info: Processes: 170 Uptime: 7h 03m Memory: 3.91 GiB used: 2.25 GiB (57.6%) Shell: bash inxi: 3.0.32 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon] Call Trace: radeon_gpu_reset+0xc3/0x2f0 [radeon] radeon_flip_work_func+0x1f3/0x250 [radeon] ? __schedule+0x2e0/0x760 process_one_work+0x1b5/0x370 worker_thread+0x50/0x3d0 kthread+0x104/0x140 ? process_one_work+0x370/0x370 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 or: BUG: unable to handle page fault for address: c03901000ffc ... Oops: [#1] SMP PTI CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon] Call Trace: radeon_gpu_reset+0xb9/0x340 [radeon] ? dma_fence_wait_timeout+0x48/0x110 ? reservation_object_wait_timeout_rcu+0x19d/0x340 radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon] radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] drm_ioctl_kernel+0xb0/0x100 [drm] drm_ioctl+0x389/0x450 [drm] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 radeon_drm_ioctl+0x4f/0x80 [radeon] do_vfs_ioctl+0xa9/0x640 ? __schedule+0x2b0/0x670 ksys_ioctl+0x75/0x80 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 I've tried both 5.3.0-28-generic and
[Desktop-packages] [Bug 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
This bug was fixed in the package atk1.0 - 2.35.1-1ubuntu2 --- atk1.0 (2.35.1-1ubuntu2) focal; urgency=medium * control, gbp.conf: Update for ubuntu/master branch * Revert "atksocket: make get_extents return parent extents by default" This reverts upstream commit 4b5ed8630c5ae9ef37884c4199da8463b7e5a127. This commit causes an infinite loop and a crash in the Ubuntu installer. (LP: #1870508) -- Iain Lane Fri, 17 Apr 2020 15:29:42 +0100 ** Changed in: atk1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to atk1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1870508 Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a() Status in atk1.0 package in Ubuntu: Fix Released Bug description: == Test Case == 1. Boot to ubiquity-dm 2. Enable the screenreader (Alt+Super+S) 3. Select "Install Ubuntu" 4. Proceed with all the steps of the installer = Actual Result = During installation, when the slideshow is running, this crash occurs. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 10:55:58 2020 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity ExecutableTimestamp: 1585729537 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only ProcCwd: / ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SegvAnalysis: Segfault happened at: 0x7fbd15f8f16a : mov%rax,-0x20(%rsp) PC (0x7fbd15f8f16a) ok source "%rax" ok destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: ubiquity StacktraceTop: g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0 atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0 Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1870508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873604] [NEW] nvidia-340 should prune 'splash' from grub.cfg
Public bug reported: Currently the Nvidia driver packages break the autologin feature of gdm3 whenever the 'splash' option is present on GRUB_CMDLINE_LINUX_DEFAULT in /etc/config/grub. https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801 This breakage can be avoided by removing 'splash' from GRUB_CMDLINE_LINUX_DEFAULT in /etc/config/grub, regenerating /boot/grub/grub.cfg with 'sudo update-grub' and then regenerating the initrd.img files such that the Nvidia drivers aren't loaded prior to gdm3. The nvidia-340 package should be modified to prune 'splash' from /etc/config/grub and regenerate /boot/grub/grub.cfg prior to building the Nvidia kernel modules. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1873604 Title: nvidia-340 should prune 'splash' from grub.cfg Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Currently the Nvidia driver packages break the autologin feature of gdm3 whenever the 'splash' option is present on GRUB_CMDLINE_LINUX_DEFAULT in /etc/config/grub. https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801 This breakage can be avoided by removing 'splash' from GRUB_CMDLINE_LINUX_DEFAULT in /etc/config/grub, regenerating /boot/grub/grub.cfg with 'sudo update-grub' and then regenerating the initrd.img files such that the Nvidia drivers aren't loaded prior to gdm3. The nvidia-340 package should be modified to prune 'splash' from /etc/config/grub and regenerate /boot/grub/grub.cfg prior to building the Nvidia kernel modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1873604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
It also has nothing to do with display server. This is ubuntu wayland session, same bug. ** Attachment added: "Screencast from 04-19-2020 12:17:48 AM.webm" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+attachment/5356587/+files/Screencast%20from%2004-19-2020%2012%3A17%3A48%20AM.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in firefox package in Ubuntu: Confirmed Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868872] Re: Nautilus Cant open files in shared folders
Yes. It solves the problem. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: Incomplete Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 20:13:33 2020 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
This bug was fixed in the package evolution-data-server - 3.36.1-2 --- evolution-data-server (3.36.1-2) unstable; urgency=medium * debian/patches/git_stable_bugfixes.patch: - backport upstream fixes for webdav and goa calendar issues (lp: #1871019) -- Sebastien Bacher Wed, 15 Apr 2020 09:38:29 +0200 ** Changed in: evolution-data-server (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in evolution-data-server package in Ubuntu: Fix Released Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868108]
(In reply to Mark Lam from comment #79) > We should not change RELEASE_ALERT_WITH_MESSAGE() to unconditionally print > its message. You probably want to look at bug #204399 ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1868108 Title: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure Status in Webkit: Fix Released Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Focal: Fix Released Bug description: ruby-gnome/3.4.1-2* package fails with: 2020-03-19T13:29:50+00:00: Running test for /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk Loaded suite test Started (run-test.rb:9142): dbind-WARNING **: 13:29:51.769: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ..[2020-03-19 13:29:52] INFO WEBrick 1.6.0 [2020-03-19 13:29:52] INFO ruby 2.7.0 (2019-12-25) [powerpc64le-linux-gnu] [2020-03-19 13:29:52] INFO WEBrick::HTTPServer#start: pid=9142 port=37651 (WebKitWebProcess:9153): dbind-WARNING **: 13:29:52.607: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files F === Failure: test: #load_uri(TestWebKit2GtkWebView::#load_uri): expected but was /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk/test/test-webkit2-gtk-web-view.rb:106:in `block (2 levels) in ' 103: @view.load_uri(http_url) 104: loop.run 105: => 106: assert_true(loaded) 107: end 108: end 109: end ===[2020-03-19 13:30:22] INFO going to shutdown ... [2020-03-19 13:30:22] INFO WEBrick::HTTPServer#start done. .. Finished in 30.95292437 seconds. --- 9 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 88.8889% passed --- 0.29 tests/s, 0.29 assertions/s Failed to run test: webkit2-gtk Failed targets: webkit2-gtk Gdk-Message: 13:30:22.622: WebKitWebProcess: Fatal IO error 2 (No such file or directory) on X server :99. autopkgtest [13:30:22]: test run-test: ---] run-test FAIL non-zero exit status 1 autopkgtest [13:30:23]: test run-test: - - - - - - - - - - results - - - - - - - - - - autopkgtest [13:30:23]: summary run-test FAIL non-zero exit status 1 Exit request sent. When running in ppc64el. This is likely due a timeout in glib main loop for that architecture but can't know for sure. I'm opening this bug so I can blacklist that particular test. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1868108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868108]
Comment on attachment 394269 Patch View in context: https://bugs.webkit.org/attachment.cgi?id=394269=review > Source/WTF/ChangeLog:11 > +will be even easier to detect if we change > RELEASE_ASSERT_WITH_MESSAGE() to actually print We should not change RELEASE_ALERT_WITH_MESSAGE() to unconditionally print its message. That message is only meant to be used in debug builds. But if you really want a message in a release build, you can always check the condition first and print your message before doing the RELEASE_ASSERT. I do not recommend doing this in the general case (for performance reasons), but in your implementation here, it’ll only be executed once. So checking and printing that error message won’t hurt much. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1868108 Title: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure Status in Webkit: Fix Released Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Focal: Fix Released Bug description: ruby-gnome/3.4.1-2* package fails with: 2020-03-19T13:29:50+00:00: Running test for /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk Loaded suite test Started (run-test.rb:9142): dbind-WARNING **: 13:29:51.769: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ..[2020-03-19 13:29:52] INFO WEBrick 1.6.0 [2020-03-19 13:29:52] INFO ruby 2.7.0 (2019-12-25) [powerpc64le-linux-gnu] [2020-03-19 13:29:52] INFO WEBrick::HTTPServer#start: pid=9142 port=37651 (WebKitWebProcess:9153): dbind-WARNING **: 13:29:52.607: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files F === Failure: test: #load_uri(TestWebKit2GtkWebView::#load_uri): expected but was /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk/test/test-webkit2-gtk-web-view.rb:106:in `block (2 levels) in ' 103: @view.load_uri(http_url) 104: loop.run 105: => 106: assert_true(loaded) 107: end 108: end 109: end ===[2020-03-19 13:30:22] INFO going to shutdown ... [2020-03-19 13:30:22] INFO WEBrick::HTTPServer#start done. .. Finished in 30.95292437 seconds. --- 9 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 88.8889% passed --- 0.29 tests/s, 0.29 assertions/s Failed to run test: webkit2-gtk Failed targets: webkit2-gtk Gdk-Message: 13:30:22.622: WebKitWebProcess: Fatal IO error 2 (No such file or directory) on X server :99. autopkgtest [13:30:22]: test run-test: ---] run-test FAIL non-zero exit status 1 autopkgtest [13:30:23]: test run-test: - - - - - - - - - - results - - - - - - - - - - autopkgtest [13:30:23]: summary run-test FAIL non-zero exit status 1 Exit request sent. When running in ppc64el. This is likely due a timeout in glib main loop for that architecture but can't know for sure. I'm opening this bug so I can blacklist that particular test. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1868108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3 --- pulseaudio (1:13.99.1-1ubuntu3) focal; urgency=medium * debian/patches/git_cherrypick_fixes.patch: - cherry pick pending commits from git, we are on a rc version but it looks like the stable isn't going to be rolled before focal is out so let's include the pending fixes in our package. - fixes for sound not working on Bay and Cherry trail (lp: #1872970) - remove git_ucm_assert.patch which was an individual cherrypick -- Sebastien Bacher Thu, 16 Apr 2020 10:07:10 +0200 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1872970 Title: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio package in Fedora: Unknown Bug description: I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 sound card. downgrade pulseaudio_13.0-1ubuntu1.1 sound work. https://bugzilla.redhat.com/show_bug.cgi?id=1818883 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/ please build next pulseaudio include patch, ucm: fix the port / ucm device activation on boot alsa sink/source: fix the mixer initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873578] Re: Autorotation works but is backwards
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1873578 Title: Autorotation works but is backwards Status in xorg package in Ubuntu: New Bug description: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 737615] Re: Can't save changes in "Edit Connections..." for Wi-Fi networks to which one doesn't have the password
** This bug is no longer a duplicate of bug 1409866 Will not find network after connection info is edited -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/737615 Title: Can't save changes in "Edit Connections..." for Wi-Fi networks to which one doesn't have the password Status in Linux: Unknown Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: New Bug description: Binary package hint: network-manager Steps to reproduce: 1) Right-click on Network Manager's tray icon 2) select "edit connections" 3) go to the "wireless" tab 4) select any connection in the list, except the one you are currently connected to 5) Click "Edit" 5) Change some settings Expected: there should be some way to save those changes Observed: the "Apply" button is greyed out. There is no "Save" button. If you hit Cancel, obviously the changes are discarded. If you edit the network you are connected to, the Apply button works, but why on earth are'n you allowed to save changes to a network you are not connected to? And if there was a reason why you can't, then why are you allowed to edit in the first place? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: network-manager 0.8-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13 Uname: Linux 2.6.32-29-generic i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Mar 18 14:47:06 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) IpRoute: 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.105 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.2.1 dev wlan0 proto static Keyfiles: Error: [Errno 2] No such file or directory ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/737615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver
@Daniel Thank you, will see where I get with sudo modprobe ath10k_core btcoex_enable=1 bt_ant_diversity=1 as seems to have been suggested under the related bug. Will try 5GHz and disabling WiFi, but the latter can obviously only be a temporary diagnostics step. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873578] [NEW] Autorotation works but is backwards
You have been subscribed to a public bug: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Autorotation works but is backwards https://bugs.launchpad.net/bugs/1873578 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver
** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356583/+files/lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver
Adding lsusb output. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356582/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873086 Title: sound stutters when playing on a bluetooth receiver Status in pulseaudio package in Ubuntu: Incomplete Bug description: I can play via bluetooth from my laptop or my mobile phone. I have a set of bluetooth headphones and bluetooth speakers. Any combination of output with the smartphone as the player works, which is as it should be. Any combination of output with the laptop as the player is miserable: sound stutters, sometimes randomly, sometimes seemingly when I touch the laptop or come close to it...had similar or identical problems with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape. $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 laptop Dell XPS 9370 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tna2174 F pulseaudio /dev/snd/pcmC0D0p: tna2174 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 22:55:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (706 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
** No longer affects: hundredpapercuts ** No longer affects: chrome-gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Move gnome-shell-extension-prefs to universe and add chrome- gnome-shell to its recommends Status in gnome-shell package in Ubuntu: New Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Couldn't the nvidia packages all be modified to prune 'splash' from /boot/grub/grub.cfg prior to rebuilding its kernel modules and thus regenerating the initrd.img files? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This bug is definitely triggered by the built kernel image loading the nvidia drivers. The autologin failures and associated hangs on restarts can be suppressed as follows... 1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT 2) Regenerate /boot/grub/grub.cfg with 'sudo update-grub' 3) Regenerate the initrd.img files by using 'sudo apt-get --reinstall install' to reinstall the currently installed kernel packages. After rebooting, the autologin feature in gdm3 can be reselected and on the next reboot, it will autologin as expected. No loading the nvidia module through initrd.img also eliminates the hangs on restarting while autologin is enabled. I suspect the folks who thought removing splash from grub.cfg didn't work had failed to rebuild the initrd.img files after regenerating grub.cfg. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
https://bugs.documentfoundation.org/show_bug.cgi?id=62196 https://bugs.documentfoundation.org/show_bug.cgi?id=128714 ** Bug watch added: Document Foundation Bugzilla #62196 https://bugs.documentfoundation.org/show_bug.cgi?id=62196 ** Bug watch added: Document Foundation Bugzilla #128714 https://bugs.documentfoundation.org/show_bug.cgi?id=128714 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in codeblocks package in Ubuntu: Confirmed Status in codelite package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in codeblocks source package in Eoan: Confirmed Status in codelite source package in Eoan: Confirmed Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in codeblocks source package in Focal: Confirmed Status in codelite source package in Focal: Confirmed Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be
@Timur: Does it make a difference if you go to /usr/share/hunspell and brutally remove the en_CA and en_GB dicts? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1026869 Title: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this behavior Status in Mozilla Firefox: New Status in Hunspell: New Status in myspell: New Status in firefox package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Bug description: I've been searching for the solution to this bug for a long time. Firefox's spell-check, despite my locale being en-US, sets itself to en-GB, en-ZA or something en_US, which isn't even correct. The problem, it seems, is that Firefox uses whatever spell-checking backends you have installed - aspell, myspell, and hunspell. The result is that Firefox chooses, en-GB as the default spell checker more-often than not. So I uninstalled myspell, hunspell, and a package called firefox-locale-en and now everything is correct - only one spell checker is installed in Firefox. The language selector, however, always prompts to reinstall these backends whenever it is loaded. This Firefox add-on can assist, it gives you a list of dictionaries installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary- switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1026869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872153] Re: SIGSEGV in g_source_set_ready_time()
This bug was fixed in the package glib2.0 - 2.64.2-1~fakesync1 --- glib2.0 (2.64.2-1~fakesync1) focal; urgency=medium [ Simon McVittie ] * Add Breaks on older versions of gimp, which used a syntactically invalid property name in a plugin, and would crash when GObject rejects syntactically invalid property names [ Sebastien Bacher ] * New upstream release * debian/patches/git_gsource_segfault.patch: - backport an upstream git change to fix a signal handler disconnect segfault situation (lp: #1872153) -- Sebastien Bacher Wed, 15 Apr 2020 23:01:50 +0200 ** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872153 Title: SIGSEGV in g_source_set_ready_time() Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: cuando abro software ubuntu ma aparece tramsparente sin fondo iconos solos ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 19:48:54 2020 ExecutablePath: /usr/libexec/gsd-usb-protection InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/gsd-usb-protection ProcEnviron: LANG=es_AR.UTF-8 LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7faa5f4a2bf3 : cmp 0x10(%rax),%rbp PC (0x7faa5f4a2bf3) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873511] Re: Sync libreoffice-dictionaries 1:6.4.3-1 (main) from Debian unstable (main)
@Mattia: Cool! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1873511 Title: Sync libreoffice-dictionaries 1:6.4.3-1 (main) from Debian unstable (main) Status in libreoffice-dictionaries package in Ubuntu: Fix Committed Bug description: Please sync libreoffice-dictionaries 1:6.4.3-1 (main) from Debian unstable (main) It's a bug-fix release targetting the libreoffice 6.4.x branch in focal. Changelog entries since current focal version 1:6.4.0~rc2-1: libreoffice-dictionaries (1:6.4.3-1) unstable; urgency=medium * New upstream version 6.4.3 -- Rene Engelhard Tue, 14 Apr 2020 16:22:54 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1873511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1409866] Re: Will not find network after connection info is edited
** No longer affects: linux-lowlatency -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1409866 Title: Will not find network after connection info is edited Status in GNOME Shell: New Status in Linux: Unknown Status in Network Manager Applet: New Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Network manager fails to connect after editing my connection information and rebooting. This becomes a real hassle when I need to use a different DNS server than what my ISP provides me by default. After reboot, if I want to try connecting to my old network connection setup by removing the auto-generated (default) one during that boot and then clicking on my connection in the applet, my computer instantly gives me an error message "connection not found". ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager-gnome 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.16.0-29.39-lowlatency 3.16.7-ckt2 Uname: Linux 3.16.0-29-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 12 13:58:36 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-11-08 (65 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.11 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1a611b55f-0934-43e9-91d5-ab32d4b0cd67 802-3-ethernet1421088678 Mon 12 Jan 2015 01:51:18 PM ESTyes no /org/freedesktop/NetworkManager/Settings/2 KCS96 47fa8aac-d4c7-48ab-83bf-59f4aa4da740 802-11-wireless 1421089059 Mon 12 Jan 2015 01:57:39 PM ESTyes no /org/freedesktop/NetworkManager/Settings/6 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1409866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be
I have installed the en-us language pack in Firefox, and I've tried many of the "fixes" I found on the Internet, but this problem remains for me. For instance, "honor" is flagged but "honour" is not flagged. The "English (US) Language Pack" add-on is installed. One interesting observation: when I go under Preferences->Language, I see that en-us is selected as the default. When I click on Set Alternatives, but the drop-down also shows en-gb and en-ca. I can click on Canada and UK and remove them, and they show as removed. However, after I restart, those two languages come back. So there appears to be no way to actually remove those languages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1026869 Title: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this behavior Status in Mozilla Firefox: New Status in Hunspell: New Status in myspell: New Status in firefox package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Bug description: I've been searching for the solution to this bug for a long time. Firefox's spell-check, despite my locale being en-US, sets itself to en-GB, en-ZA or something en_US, which isn't even correct. The problem, it seems, is that Firefox uses whatever spell-checking backends you have installed - aspell, myspell, and hunspell. The result is that Firefox chooses, en-GB as the default spell checker more-often than not. So I uninstalled myspell, hunspell, and a package called firefox-locale-en and now everything is correct - only one spell checker is installed in Firefox. The language selector, however, always prompts to reinstall these backends whenever it is loaded. This Firefox add-on can assist, it gives you a list of dictionaries installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary- switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1026869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873582] [NEW] Unable to launch applications by clicking on desktop-files inside /usr/share/applications
Public bug reported: Steps to reproduce: 1. Install Ubuntu 20.04 LTS 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Click on any desktop-file Expected results: * Nautilus launched the application from selected desktop-file Actual results: * Nautilus opened desktop-file in the text editor, the application is not launched ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Apr 18 20:32:33 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan focal ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873582 Title: Unable to launch applications by clicking on desktop-files inside /usr/share/applications Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 20.04 LTS 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Click on any desktop-file Expected results: * Nautilus launched the application from selected desktop-file Actual results: * Nautilus opened desktop-file in the text editor, the application is not launched ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Apr 18 20:32:33 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873557] Re: Nautilus don't respond when i try to restore a folder
*** This bug is a duplicate of bug 1839380 *** https://bugs.launchpad.net/bugs/1839380 ** This bug has been marked a duplicate of bug 1839380 Nautilus freezes when restoring files and a copy already exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873557 Title: Nautilus don't respond when i try to restore a folder Status in nautilus package in Ubuntu: New Bug description: Nautilus don't respond when i try to restore a folder from the trash because the original location is taken by another folder with the same name. Using Ubuntu 20.04 LTS focal fossa with GNOME/Nautilus 3.36.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 11:59:14 2020 InstallationDate: Installed on 2020-04-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
seems to be very similar: https://gitlab.freedesktop.org/drm/amd/issues/773 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon] Call Trace: radeon_gpu_reset+0xc3/0x2f0 [radeon] radeon_flip_work_func+0x1f3/0x250 [radeon] ? __schedule+0x2e0/0x760 process_one_work+0x1b5/0x370 worker_thread+0x50/0x3d0 kthread+0x104/0x140 ? process_one_work+0x370/0x370 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 or: BUG: unable to handle page fault for address: c03901000ffc ... Oops: [#1] SMP PTI CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon] Call Trace: radeon_gpu_reset+0xb9/0x340 [radeon] ? dma_fence_wait_timeout+0x48/0x110 ? reservation_object_wait_timeout_rcu+0x19d/0x340 radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon] radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] drm_ioctl_kernel+0xb0/0x100 [drm] drm_ioctl+0x389/0x450 [drm] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 radeon_drm_ioctl+0x4f/0x80 [radeon] do_vfs_ioctl+0xa9/0x640 ? __schedule+0x2b0/0x670 ksys_ioctl+0x75/0x80 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel- ppa but that made no difference. It appears to be a bug in radeon. Nothing specific makes this happen, just regular usage with a compositing window manager. I'm not playing games or particularly exercising the GPU. The last two times I was just reading in web browser. It's also happened in the middle of the night while I was asleep. Sometimes I have a few days uptime, sometimes it happens in less than 24 hours from boot. This never happened before the radeon update mentioned on the first line. I'll attach two files of dmesg output. As per https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and started apport for next time it happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
I have very old siemens computer. The affected it after I upgraded ram from 2 to 4 GB. I found some rumours that the bug was introduced with kernel 4.10. I'm not able to debug the problem. Anyhow I attached dmesg log maybe it help to fix this annoying bug. ** Attachment added: "dmesg_drm.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5356490/+files/dmesg_drm.txt ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #773 https://gitlab.freedesktop.org/drm/amd/issues/773 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon] Call Trace: radeon_gpu_reset+0xc3/0x2f0 [radeon] radeon_flip_work_func+0x1f3/0x250 [radeon] ? __schedule+0x2e0/0x760 process_one_work+0x1b5/0x370 worker_thread+0x50/0x3d0 kthread+0x104/0x140 ? process_one_work+0x370/0x370 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 or: BUG: unable to handle page fault for address: c03901000ffc ... Oops: [#1] SMP PTI CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon] Call Trace: radeon_gpu_reset+0xb9/0x340 [radeon] ? dma_fence_wait_timeout+0x48/0x110 ? reservation_object_wait_timeout_rcu+0x19d/0x340 radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon] radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] drm_ioctl_kernel+0xb0/0x100 [drm] drm_ioctl+0x389/0x450 [drm] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 radeon_drm_ioctl+0x4f/0x80 [radeon] do_vfs_ioctl+0xa9/0x640 ? __schedule+0x2b0/0x670 ksys_ioctl+0x75/0x80 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel- ppa but that made no difference. It appears to be a bug in radeon. Nothing specific makes this happen, just regular usage with a compositing window manager. I'm not playing games or particularly exercising the GPU. The last two times I was just reading in web browser. It's also happened in the middle of the night while I was asleep. Sometimes I have a few days uptime, sometimes it happens in less than 24 hours from boot. This never happened before the radeon update mentioned on the first line. I'll attach two files of dmesg output. As per
[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
Ubuntu 19.10, I want to delete words with Ctrl + backspace from Trello board name, but it loses focus. - trello.com. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in Mutter: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
Attached as a file the full output for "simple-scan 3.34.1" when scanning 2 pages from the feeder, which still has this bug. Final few lines are here: [+53.69s] DEBUG: scanner.vala:1345: sane_read (15300) -> (SANE_STATUS_GOOD, 15300) [+55.00s] DEBUG: scanner.vala:1345: sane_read (15300) -> (SANE_STATUS_GOOD, 7649) [+55.00s] DEBUG: scanner.vala:1345: sane_read (15301) -> (SANE_STATUS_EOF, 0) [+55.00s] DEBUG: scanner.vala:1241: sane_start (page=1, pass=0) -> SANE_STATUS_GOOD [+55.00s] DEBUG: scanner.vala:1258: sane_get_parameters () -> SANE_STATUS_GOOD [+55.00s] DEBUG: scanner.vala:1270: Parameters: format=SANE_FRAME_RGB last_frame=SANE_TRUE bytes_per_line=7650 pixels_per_line=2550 lines=3300 depth=8 [+55.00s] DEBUG: autosave-manager.vala:349: Autosaving page pixels to /home/test-machine/.cache/simple-scan/autosaves/496152848.pixels [+55.02s] DEBUG: autosave-manager.vala:281: Autosaving book information [+55.02s] DEBUG: autosave-manager.vala:298: Autosaving page page-0 [+55.02s] CRITICAL: page_finish: assertion 'self != NULL' failed [+55.02s] DEBUG: simple-scan.vala:350: Page is 2550 pixels wide, 3300 pixels high, 8 bits per pixel [+55.03s] DEBUG: simple-scan.vala:284: Getting color profile for device pixma:MF240_canon-mfc.lan [+55.04s] DEBUG: simple-scan.vala:304: Unable to find colord device pixma:MF240_canon-mfc.lan: property match 'Serial'='sane:pixma:MF240_canon-mfc.lan' does not exist [+56.00s] DEBUG: scanner.vala:1345: sane_read (7651) -> (SANE_STATUS_NO_DOCS, 0) [+56.00s] DEBUG: scanner.vala:1214: sane_cancel () ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+attachment/5356478/+files/output.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw Status in simple-scan package in Ubuntu: Incomplete Bug description: Hello, When scanning multiple pages from a Canon mf244dw via the LAN I only get the first page scanned, then an error message. Running "simple-scan -d" and looking at the output I see the following: [+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) -> (SANE_STATUS_CANCELLED, 0) [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: Operation was cancelled [+123.87s] DEBUG: scanner.vala:768: sane_cancel () [+123.87s] DEBUG: scanner.vala:771: sane_close () I do notice that the scanner is already feeding in the second page before the first page has completely rendered on screen - perhaps it's going too fast? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873511] Re: Sync libreoffice-dictionaries 1:6.4.3-1 (main) from Debian unstable (main)
I just synced it. I'm going to leave a line in #ubuntu-release, I think that should be enough. ** Changed in: libreoffice-dictionaries (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1873511 Title: Sync libreoffice-dictionaries 1:6.4.3-1 (main) from Debian unstable (main) Status in libreoffice-dictionaries package in Ubuntu: Fix Committed Bug description: Please sync libreoffice-dictionaries 1:6.4.3-1 (main) from Debian unstable (main) It's a bug-fix release targetting the libreoffice 6.4.x branch in focal. Changelog entries since current focal version 1:6.4.0~rc2-1: libreoffice-dictionaries (1:6.4.3-1) unstable; urgency=medium * New upstream version 6.4.3 -- Rene Engelhard Tue, 14 Apr 2020 16:22:54 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1873511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
After 14 months waiting for a fix, I left Ubuntu and switched to a distro that works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834058] Re: Keyboard layout indicator vanishes after Suspend or Screenlock
After 8 months waiting for a fix, I left Ubuntu and switched to a distro that works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1834058 Title: Keyboard layout indicator vanishes after Suspend or Screenlock Status in gnome-shell package in Ubuntu: New Bug description: Related to bug 1812266. lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 apt-cache policy gnome-shell gnome-shell: installed: 3.28.4-0ubuntu18.04.1 After Suspend or Screenlock ... What you expected to happen: Keyboard layout indicator should be visible all the time. What happened instead: not visible anymore Current manual fix: Press SUPER give search field the focus Press SUPER+Spacebar several times until current keyboard layout is selected. Keyboard layout indicator is visible again with current layout. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 24 17:40:12 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-20 (339 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I have exactly same problem, I've tried both 440, and 435 Nvidia drivers. the results of: $ xrandr --verbose --output HDMI-0 --scale 2x2 screen 0: 6880x2880 1820x762 mm 96.00dpi crtc 0:3440x1440 59.97 +0+0 "HDMI-0" xrandr: Configure crtc 0 failed crtc 0: disable crtc 1: disable crtc 2: disable crtc 3: disable crtc 4: disable crtc 5: disable crtc 6: disable screen 0: revert crtc 0: revert crtc 1: revert X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 21 (RRSetCrtcConfig) Value in failed request: 0x0 Serial number of failed request: 72 Current serial number in output stream: 72 $ xrandr --verbose --output HDMI-0 --scale 1.25x1.25 screen 0: 4300x1800 1137x476 mm 96.00dpi crtc 0:3440x1440 59.97 +0+0 "HDMI-0" xrandr: Configure crtc 0 failed crtc 0: disable crtc 1: disable crtc 2: disable crtc 3: disable crtc 4: disable crtc 5: disable crtc 6: disable screen 0: revert crtc 0: revert crtc 1: revert X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 21 (RRSetCrtcConfig) Value in failed request: 0x0 Serial number of failed request: 72 Current serial number in output stream: 72 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873564] [NEW] Nautilus scrolling is stuttery in 20.04
Public bug reported: Scrolling in nautilus using the touchpad of my laptop (Dell XPS 13) is stuttery, sometimes very stuttery. Compared to scrolling in gnome- settings for example where the scrolling effect is very smooth, the difference is night and day. I don't remember to have this problem in 19.10. The extent of the issue seems a bit random. Sometimes it is a bit stuttery, sometimes it is very choppy. It is never as smooth as gnome- settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 10:46:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'248' b'org.gnome.nautilus.window-state' b'initial-size' b'(932, 931)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-02-23 (784 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873564 Title: Nautilus scrolling is stuttery in 20.04 Status in nautilus package in Ubuntu: New Bug description: Scrolling in nautilus using the touchpad of my laptop (Dell XPS 13) is stuttery, sometimes very stuttery. Compared to scrolling in gnome- settings for example where the scrolling effect is very smooth, the difference is night and day. I don't remember to have this problem in 19.10. The extent of the issue seems a bit random. Sometimes it is a bit stuttery, sometimes it is very choppy. It is never as smooth as gnome- settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 10:46:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'248' b'org.gnome.nautilus.window-state' b'initial-size' b'(932, 931)' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-02-23 (784 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
It is not firefox-specific bug, it has nothing to do with ff! See my webm, there is a chrome alongside ff and it's also affected. VLC is also affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in firefox package in Ubuntu: Confirmed Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873562] [NEW] package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before inst
Public bug reported: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1873562 Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux- gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error Status in mesa package in Ubuntu: New Bug description: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error
[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
I just noticed hundreds of chromium.launcher processes running on my machine with `sleep 60` and found that it's because of this fix. Looks like this background process is started but nerver stopped? nor does it checks if it's already running. This is especially visible in my case because I'm running automated tests starting chrome using capybara, and it'll be the same for everybody doing integration tests with chrome I guess. Maybe a good fix would be to check if this background process is already running to not start it again? https://user-images.githubusercontent.com/201687/79634864-773b1300-816d- 11ea-98f5-1a677aca60dd.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Committed Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
Still a problem on Ubuntu 20.04 beta, which prevent smooth scrolling in Firefox. This bug is not present in some other major distribution, like Fedora. As reported in https://bugzilla.mozilla.org/show_bug.cgi?id=1207700 "Fedora enables XInput2 by default and we don't have any user complains." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860547] Re: cupsd high memory consumption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1860547 Title: cupsd high memory consumption Status in cups package in Ubuntu: Confirmed Bug description: Ubuntu version: 19.10 cups version: 2.2.12-2ubuntu1 cupsd process slowly increases memory consumption. The /var/log/cups/error_log is full of errors below: E [22/Jan/2020:11:06:17 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:19 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:20 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:21 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:22 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:24 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:25 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:26 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:28 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:29 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:30 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:32 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. E [22/Jan/2020:11:06:33 +0100] [Client 6] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/HP_LaserJet_Professional_P1606dn) from localhost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1860547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870788] Re: Sound randomly stops working for individual programs
Update I have found a work around so that I don't have to restart my computer as often but the bug is still live and kicking. I use "indicator-sound-switcher" https://github.com/yktoo/indicator-sound-switcher When the sound breaks I can use the indicator in the top bar to select "Starship/Matisse HD Audio Controller -line out". If I select this twice then the sound comes back. In Youtube if I pause, skip or watch a new video the sound cuts out and I have to select the option again two times for it to come back. This bug does however make Skype completely unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1870788 Title: Sound randomly stops working for individual programs Status in alsa-driver package in Ubuntu: New Bug description: The sound for an individual program will randomly stop working. For example I am listening to music on youtube using firefox right now but VLC will not play sound. Randomly firefox will stop playing sound but other programs will work. The only way to fix it is to restart my computer every 45 minutes to 1.5 hours. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cortana3089 F pulseaudio /dev/snd/pcmC1D0p: cortana3089 F...m pulseaudio /dev/snd/controlC0: cortana3089 F pulseaudio /dev/snd/timer: cortana3089 f pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:59:21 2020 InstallationDate: Installed on 2018-11-10 (511 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Apr 04 13:46:12 Cortana-U dbus-daemon[1845]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.35' (uid=121 pid=2196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 04 13:46:13 Cortana-U dbus-daemon[1845]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.40' (uid=121 pid=2196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 04 13:46:25 Cortana-U systemd[2165]: pulseaudio.service: Succeeded. Apr 04 13:46:35 Cortana-U systemd[2165]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] fails after a while UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago) dmi.bios.date: 09/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5220 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5220:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873558] [NEW] Nautilus hangs while deleting files in ~/Desktop
Public bug reported:
Steps to reproduce:
1. Within Nautilus ("Files"), navigate to ~/Desktop.
2. Delete a file, either via the Delete key or "Move to trash" context menu
entry.
3. Observe a noticeable freeze that does not occur when deleting files in any
other directory.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 18 12:31:20 2020
InstallationDate: Installed on 2018-04-10 (738 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-04-17 (1 days ago)
usr_lib_nautilus:
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1873558
Title:
Nautilus hangs while deleting files in ~/Desktop
Status in nautilus package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Within Nautilus ("Files"), navigate to ~/Desktop.
2. Delete a file, either via the Delete key or "Move to trash" context menu
entry.
3. Observe a noticeable freeze that does not occur when deleting files in any
other directory.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 18 12:31:20 2020
InstallationDate: Installed on 2018-04-10 (738 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-04-17 (1 days ago)
usr_lib_nautilus:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873558/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873557] [NEW] Nautilus don't respond when i try to restore a folder
Public bug reported: Nautilus don't respond when i try to restore a folder from the trash because the original location is taken by another folder with the same name. Using Ubuntu 20.04 LTS focal fossa with GNOME/Nautilus 3.36.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 11:59:14 2020 InstallationDate: Installed on 2020-04-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873557 Title: Nautilus don't respond when i try to restore a folder Status in nautilus package in Ubuntu: New Bug description: Nautilus don't respond when i try to restore a folder from the trash because the original location is taken by another folder with the same name. Using Ubuntu 20.04 LTS focal fossa with GNOME/Nautilus 3.36.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 11:59:14 2020 InstallationDate: Installed on 2020-04-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
** Attachment added: "Here's the alsa-info output for this system, in case it helps." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5356402/+files/alsa-info.txt.QsoAGgtfAU -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
With the -1ubuntu2 package, I no longer get a crash dump, but the audio is still not working. pulseaudio is aborting. Here is what is in syslog from bootup: Apr 18 01:13:09 shh dbus-daemon[1218]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=122 pid=1443 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") ... Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:10 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:10 shh systemd[1432]: Dependency failed for GNOME Sound sample caching handling. Apr 18 01:13:10 shh systemd[1432]: gsd-sound.target: Job gsd-sound.target/start failed with result 'dependency'. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 1. ... Apr 18 01:13:10 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:10 shh systemd[1432]: Starting Sound Service... ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:12 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:12 shh systemd[1432]: Startup finished in 2.727s. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Apr 18 01:13:12 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:12 shh systemd[1432]: Starting Sound Service... Apr 18 01:13:12 shh rtkit-daemon[1539]: Successfully made thread 1864 of process 1864 owned by '122' high priority at nice level -11. Apr 18 01:13:12 shh rtkit-daemon[1539]: Supervising 1 threads of 1 processes of 1 users. Apr 18 01:13:12 shh pulseaudio[1864]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
Commented upstream: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/2234#note_773177 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
Makes sense -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in Dash to dock: Unknown Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873541] Re: black screen with cursor on dual nouveau + i915
Please also run: lspci -k > lspcik.txt dmesg > dmesg.txt on the system and attach the resulting text files here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873541 Title: black screen with cursor on dual nouveau + i915 Status in mutter package in Ubuntu: Incomplete Bug description: This bug should be able to be reproduced on any computer with both an nvidia (stock nouveau) and intel igpu (stock i915), booting to stock gdm3 (wayland by default). My main example is a MacBookPro6,2 with the infamous GT 330m on 20.04 with -proposed enabled and booting with the following grub manipulations to set gmux to the integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine-- the only thing broken is the LVDS connection to the internal panel. I disable it with video=LVDS-2:d. --> NOTE: This mod is only for the convenience of not having to deal with a phantom second screen once booted (both GPU's have the LVDS and edid of the internal screen hooked up). The computer boots fine and the bug reproduces exactly the same with or without it. I tested with all these modifications disabled, and this still occurred - it's not specific to my configuration. A user booting stock Ubuntu on this laptop, or as I discovered later, any nouveau + i915 hardware combination will run into this as well. Anyways, I'm keeping the 330m enabled to use DRI_PRIME to run applications on the 330m for good reason- it supports OpenGL 3.3 while HD Graphics (arrandale aka Ironlake) is the only HD Graphics iGPU stuck on OpenGL 2.1, thus otherwise vastly restricting the modern graphics workloads of the system. When explicitly booting with gdm3 WaylandEnable=false (login and desktop both xorg), everything works as expected - single screen driven by the i915's KMS, nouveau with DRI_PRIME working, returning NVA5 stats and functional with OpenGL 3 apps as well. On GDM3 wayland, however (the default-- which is why I think this bug is rather important), gdm3 starts to a black screen with cursor. The login screen and shell still seem to be running-- I can type my password blindly and press enter and the cursor freezes briefly as it does during a non-broken login. After a few seconds, I can press the volume up/down keys and I hear the volume sound. Pressing the app grid shortcut makes the cursor lag, just as it does when I disable the nvidia at the pcie link level and rendering works on i915. Backlight control also works on the login screen and once logged in. It's as if everything except the actual rendering to the screen is working. The minute I pass nouveau.modeset=0 in cmdline, or cut the power to the 330m at the hardware level with outb 0x750, Wayland starts working again. The issue has something to do with GDM3's handling of a KMS- enabled nouveau GPU, whether it is headless or not (no difference with video=LVDS-2:d or not). To confirm my suspicions that it is not specific to the macbook pro line, this exact same issue (Xorg works wayland doesn't) also occurred on a desktop dual-gpu setup, with a GTX 760 (kepler) on nouveau tandem with a Haswell HD Graphics G3258-- with any combination of displays, all on the Intel, mixed on nvidia and intel, or all on nvidia, as long as both cards were present and modesetting, a black screen with cursor but blindly working gnome followed. This bug has existed since at least 19.04, if not earlier-- I replaced the nvidia gpu in that system with a Radeon 7870 when it ran that release due to this bug, as a matter of fact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
Yeah that's been done before but it's better to fix issues properly upstream in gnome-shell such that downstream themes don't run into them and don't have to work around them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873541] Re: black screen with cursor on dual nouveau + i915
'disco' is no longer supported so let's drop that. Next please run this command on the affected system so we can find out more about it: apport-collect 1873541 ** Tags removed: disco ** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873541 Title: black screen with cursor on dual nouveau + i915 Status in mutter package in Ubuntu: Incomplete Bug description: This bug should be able to be reproduced on any computer with both an nvidia (stock nouveau) and intel igpu (stock i915), booting to stock gdm3 (wayland by default). My main example is a MacBookPro6,2 with the infamous GT 330m on 20.04 with -proposed enabled and booting with the following grub manipulations to set gmux to the integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine-- the only thing broken is the LVDS connection to the internal panel. I disable it with video=LVDS-2:d. --> NOTE: This mod is only for the convenience of not having to deal with a phantom second screen once booted (both GPU's have the LVDS and edid of the internal screen hooked up). The computer boots fine and the bug reproduces exactly the same with or without it. I tested with all these modifications disabled, and this still occurred - it's not specific to my configuration. A user booting stock Ubuntu on this laptop, or as I discovered later, any nouveau + i915 hardware combination will run into this as well. Anyways, I'm keeping the 330m enabled to use DRI_PRIME to run applications on the 330m for good reason- it supports OpenGL 3.3 while HD Graphics (arrandale aka Ironlake) is the only HD Graphics iGPU stuck on OpenGL 2.1, thus otherwise vastly restricting the modern graphics workloads of the system. When explicitly booting with gdm3 WaylandEnable=false (login and desktop both xorg), everything works as expected - single screen driven by the i915's KMS, nouveau with DRI_PRIME working, returning NVA5 stats and functional with OpenGL 3 apps as well. On GDM3 wayland, however (the default-- which is why I think this bug is rather important), gdm3 starts to a black screen with cursor. The login screen and shell still seem to be running-- I can type my password blindly and press enter and the cursor freezes briefly as it does during a non-broken login. After a few seconds, I can press the volume up/down keys and I hear the volume sound. Pressing the app grid shortcut makes the cursor lag, just as it does when I disable the nvidia at the pcie link level and rendering works on i915. Backlight control also works on the login screen and once logged in. It's as if everything except the actual rendering to the screen is working. The minute I pass nouveau.modeset=0 in cmdline, or cut the power to the 330m at the hardware level with outb 0x750, Wayland starts working again. The issue has something to do with GDM3's handling of a KMS- enabled nouveau GPU, whether it is headless or not (no difference with video=LVDS-2:d or not). To confirm my suspicions that it is not specific to the macbook pro line, this exact same issue (Xorg works wayland doesn't) also occurred on a desktop dual-gpu setup, with a GTX 760 (kepler) on nouveau tandem with a Haswell HD Graphics G3258-- with any combination of displays, all on the Intel, mixed on nvidia and intel, or all on nvidia, as long as both cards were present and modesetting, a black screen with cursor but blindly working gnome followed. This bug has existed since at least 19.04, if not earlier-- I replaced the nvidia gpu in that system with a Radeon 7870 when it ran that release due to this bug, as a matter of fact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
This could be fixed by a design choice in Yaru to style differently. Yes, you're right, for other themes the decision can be made upstream. But, the way CSS works, Yaru could have this fixed with a few lines of CSS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871320] Re: Switching alert sound will not take effect unless you switch to Default alert first
@Sebastien, I didn't understand what "g-t sound" means. But after you replied, I downloaded April 17th build again and I tested there. The behavior is same. Am I missing anything here. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871320 Title: Switching alert sound will not take effect unless you switch to Default alert first Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I installed April 5th's nightly build, of Ubuntu Focal Fossa (development branch). Description: Ubuntu Focal Fossa (development branch) Release: 20.04 The issue is, Whichever the notification sound we choose after default, only that sound will take effect. Directly changing to another type of alert sound will not take effect. To reproduce the problem, 1. Open terminal, 2. Open sound settings, initially it will be "default". Change that to some other alert sound, say, "Drip". 3. Switch to terminal and press backspace, you will hear "Drip". 4. Switch to sound settings, this time select "Glass". 5. Switch to terminal and press backspace, here is the issue. You will not hear "Glass". You will still hear "Drip". 6. Switch to sound settings, now select default first and then select "Glass". 7. Switch to terminal and press backspace, now you will hear "Glass". So to summarize, if you want to change the alert sound, first you have to switch back to "Default" and then only whichever other alert sound you select, will take effect. Since the release time is near, I thought it would be helpful to fix this before release. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873510] Re: Blank screen when hotplugging monitors connected through DisplayPort dock
It kind if sounds like the system is in partial sleep mode, or trying to get there. And that would make sense because when the bug occurs the lid is closed and you've disconnected the only other screen. So you're kind of asking for screen hotplugging (or switching back to it on the KVM) to wake the system. When you put it that way it's kind of not a bug, if the theory is right... Can you please run 'gnome-tweaks' and check that: Gnome Tweaks > Power > Suspend when laptop lid is closed = OFF ? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1873510 Title: Blank screen when hotplugging monitors connected through DisplayPort dock Status in Ubuntu: Incomplete Bug description: Hi, I run Ubuntu 18.04 on a Dell Precision 7540. Most of the time I use this through a Dell WD19DC dock. The dock is connected to a Trendnet TK-240DP KVM Switch. If I have the laptop clamshell closed, like I normally do, and switch my KVM to the other computer, and then switch back, my monitors stay enter power saving mode. Most of the time, I am able to recover the screens by pressing Control-Alt-F3, waiting a few seconds, and then pressing Control-Alt-F2. The problem does not happen if the clamshell is left open. Part of the problem is that this is a cheaper KVM, and from the laptop's perspective the screens are disconnected when the computer is switched. Changing a few small things makes the problem not occur: * Opening the clamshell when switching the KVM. Interestingly, if the clamshell is open during either the switch away OR the switch back, the screen recovers. * Manually removing the displays one at a time does not reliably trigger the problem. Though I have witnessed the problem occur once or twice when removing a single display. I am attaching three nvidia bug report logs: 1. nvidia-bug-report-before.log.gz is after a clean boot when I have not used the KVM. 2. nvidia-bug-report-blank.log.gz is after switching the KVM to the other computer and back. During this time, both screens are black. The log was taken over ssh. 3. nvidia-bug-report-workaround.log.gz is after I have recovered the screen after using Ctrl-Alt-F3 followed by Ctrl-Alt-F2. This problem happens when prime-select is set to intel or nvidia. These logs are when it was set to intel. Any advice would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.5.0-050500rc6-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 17 13:57:43 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 440.82, 4.15.0-1079-oem, x86_64: installed nvidia, 440.82, 5.0.0-1047-oem-osp1, x86_64: installed nvidia, 440.82, 5.5.0-050500rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0926] NVIDIA Corporation Device [10de:1f36] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0926] InstallationDate: Installed on 2020-01-03 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Precision 7540 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.5.0-050500rc6-generic root=UUID=7f01cb01-e7df-4259-9d7a-ae37a19f363b ro quiet splash dis_ucode_ldr vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1873164] Re: [Lenovo Ideapad D330] [bmc150] Problem with g sensor and screen orientation
I expect that part isn't working, and isn't easily fixable... This is a tablet and some tablets commonly have a native screen orientation of portrait so that's probably what Plymouth is using. When the gnome-shell login screen starts it detects the correct orientation and automatically rotates to landscape. So the issue sounds like Plymouth not supporting sensors/screen rotation. Not a very common issue... ** Changed in: plymouth (Ubuntu) Status: Incomplete => New ** No longer affects: linux (Ubuntu) ** No longer affects: iio-sensor-proxy (Ubuntu) ** Summary changed: - [Lenovo Ideapad D330] [bmc150] Problem with g sensor and screen orientation + Tablet (plugged into a folding keyboard) boots in portrait mode and doesn't rotate correctly to landscape until the login screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1873164 Title: Tablet (plugged into a folding keyboard) boots in portrait mode and doesn't rotate correctly to landscape until the login screen Status in plymouth package in Ubuntu: Triaged Bug description: I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD Graphics 600. and its a touchscreen laptop. The Problem is i'm facing with g sensor and screen orientation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:08:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 605 [17aa:39ff] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 81H3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 8NCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad D330-10IGM dmi.modalias: dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM: dmi.product.family: ideapad D330-10IGM dmi.product.name: 81H3 dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM dmi.product.version: Lenovo ideapad D330-10IGM dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1873164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873401] Re: xorg lock-up on GPU hotplug
Alright. Please first ensure you have followed all the steps in comment #3. Then if there's still no evidence of a crash we can assume it's a freeze. The next thing to try then is to force it to dump core during the freeze (from an ssh login) by sending some signal to the process like: kill -USR2 PID Then we would be able to analyse it as a crash (assuming the automated crash reporting picks it up). But if you want to do the debugging locally yourself then feel free. Just paste the stack trace you find here so we can see what you see. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873401 Title: xorg lock-up on GPU hotplug Status in mutter package in Ubuntu: Incomplete Bug description: Discovered when testing EVDI-backed screen (https://github.com/DisplayLink/evdi). While adding new device /dev/dri/cardX xorg locks, it can be observed by the cursors that stop blinking or menus not responding. Sometimes it is just a short (1-2 sec.) pause, but sometimes (hard to state the exact reproduction rate, rather rarely) the screen stops completely. Interestingly enough, if using HW cursor, it moves fine. Keyboard is at least partially functional, as it's possible to "bail out" to tty with C-A-Fx and kill the session. Anything else is difficult to check, as nothing really happens on the screen, it just remains frozen. When adding 4 GPUs at once (e.g. via config in /etc/modprobe.d according to https://support.displaylink.com/knowledgebase/articles/1843660-screen-freezes-after-opening-an-application-only). Haven't checked other numbers yet, to be done soon. The problem occurs, when adding the devices, not enabling their associated screens/reading EDID or anything like that. Also, to be checked with UDL, similar behaviour is expected, but due to the fact that it adds only a single device at a time reproducing "complete" freeze might be difficult. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 09:24:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415) MachineType: Dell Inc. Dell Precision M3800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=e0a7aba8-1c09-4367-9d6b-c74b73017fb4 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
I'm only trying to determine if this is a gnome-shell bug right now or a bug belonging to some other component. Since your setup only uses gnome-shell in the host and not the guest it should be fairly simple to remove gnome-shell from the equation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for title bar
Got it thanks! I was using 'Ubuntu on Wayland' where the bug does not occur. ** Summary changed: - Changing theme Light<->Standard preserves theme for title bar + Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) ** Changed in: firefox (Ubuntu) Status: Incomplete => Confirmed ** No longer affects: gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in firefox package in Ubuntu: Confirmed Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
We don't do the design for it here. I suggest keeping the conversation upstream where those decisions are made: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2234 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867406] Re: When the dock is located at the bottom of the screen it is difficult to rearrange the icons within it
*** This bug is a duplicate of bug 1867613 *** https://bugs.launchpad.net/bugs/1867613 Yes we should have used this bug since it's older. But bug 1867613 is already done so let's use that. ** This bug has been marked a duplicate of bug 1867613 Ubuntu dock does not allow drag and move icons at bottom of screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867406 Title: When the dock is located at the bottom of the screen it is difficult to rearrange the icons within it Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
^^^ That looks like a different bug. Please report it by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: [ Description ] Intellij and other java apps can cause GNOME shell to crash [ Test case ] 1) Run this test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/956 2) Windows should appear and close correctly while Gnome shell must not crash [ Regression potential ] Parent-child relationship on some windows might be broken. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: mutter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1136 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in Dash to dock: Unknown Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873394] Re: Terminal does not respond to theme changes
** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Won't Fix ** Changed in: yaru-theme (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873394 Title: Terminal does not respond to theme changes Status in gnome-terminal package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Won't Fix Bug description: Terminal does not respond to theme changes. In the Settings app > Appearance > Window theme, I can select Light, Standard or Dark. Changing this setting seems to affect all other apps but not Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
