[Desktop-packages] [Bug 1853894] Re: Strange Hang with old SWT Apps
I have also tried to see if this issue arises on PopOS, which it does in the versions after the last LTS. The current PopOS LTS does not have the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1853894 Title: Strange Hang with old SWT Apps Status in gtk+2.0 package in Ubuntu: New Bug description: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1853894/+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 1551949]
One issue here is that the output is deceptive. The document is rendered such that the links look like links: they are rendered in blue, and underlined. I was fooled by this and sent a document to someone without actually trying the links. If you're not going to make it work, the least you could do is not fake the appearance, you know? Would it be difficult to pop up a dialog box or something? "this document contains hyperlinks; these will not work [Save PDF Anyway] [Cancel]" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1551949 Title: Printing to PDF file loses URLs/links Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. File -> Print... 2. Select "Print to File". 3. Enter the file name. 4. Enter the save-to folder. 5. Leave the output format as-is, or select PDF if it's not the default. 6. Hit the Print button. 7. Open the resulting PDF in any PDF viewer. Actual results: The URLs within the document are not actually hyperlinks. They are simply text, coloured blue and underlined. Expected results: Any clickable links on the original e-mail message should be retained when converting the document to PDF format. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: thunderbird 1:38.5.1+build2-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colan 2383 F pulseaudio /dev/snd/controlC0: colan 2383 F pulseaudio BuildID: 20160106101030 Channel: Unavailable CurrentDesktop: Unity Date: Tue Mar 1 15:53:53 2016 EcryptfsInUse: Yes ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.140 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-1abc004a-043e-4a15-bdc0-45ade2150908 Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/zsh Profiles: Profile0 (Default) - LastVersion=38.5.1/20160106101030 (In use) RelatedPackageVersions: google-talkplugin 5.41.0.0-1 rhythmbox-mozilla 3.2.1-1ubuntu3.1 adobe-flashplugin 1:20160209.1-0ubuntu0.15.10.1 RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-1abc004a-043e-4a15-bdc0-45ade2150908 bp-c8c94f9f-0c39-42d2-97ac-f2c7d2150713 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to wily on 2015-11-30 (92 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1551949/+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 1010683] Re: ATI Resume from Suspend leads into black screen (VGA_Switcheroo)
** Changed in: xserver-xorg-driver-ati Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #227 https://gitlab.freedesktop.org/drm/amd/issues/227 -- 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/1010683 Title: ATI Resume from Suspend leads into black screen (VGA_Switcheroo) Status in Linux: Confirmed Status in xserver-xorg-driver-ati: Unknown Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have a HP Touchsmart 2 (tm2). This Notebook has 2 Graphiccars: Intel (DIS) and ATI (IGD): # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] If i use the Intel-Graphiccard, everything works well, i can suspend and resume as often as i'd like. Edit: As soon as I switched (switch to ATI and back to Intel, the below problem happens on Intel-GPU too). If i use the ATI-Graphiccard i can suspend (wich takes a longer time than with the Intel one) however I can't resume. I get a blank/black screen and can't change brightness. Plus I can't switch to any tty. I've tried this instructions to find an error: https://wiki.ubuntu.com/DebuggingKernelSuspend but it dosn't seem to bring relevant informations (however, I'll add the dmesg.txt to this bugreport) PS: to switch between graphiccards, I use "vga_switcheroo" and i have "vanilla"-ubuntu, no third party software. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.317 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Jun 8 20:54:43 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1486] Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU (Mobility Radeon HD 5450) [103c:1486] LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1486 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.1A dmi.chassis.asset.tag: CNU0250216 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP TouchSmart tm2 Notebook PC dmi.product.version: 048920252A2000122 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1010683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists
[Desktop-packages] [Bug 1010683]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/227. -- 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/1010683 Title: ATI Resume from Suspend leads into black screen (VGA_Switcheroo) Status in Linux: Confirmed Status in xserver-xorg-driver-ati: Unknown Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have a HP Touchsmart 2 (tm2). This Notebook has 2 Graphiccars: Intel (DIS) and ATI (IGD): # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] If i use the Intel-Graphiccard, everything works well, i can suspend and resume as often as i'd like. Edit: As soon as I switched (switch to ATI and back to Intel, the below problem happens on Intel-GPU too). If i use the ATI-Graphiccard i can suspend (wich takes a longer time than with the Intel one) however I can't resume. I get a blank/black screen and can't change brightness. Plus I can't switch to any tty. I've tried this instructions to find an error: https://wiki.ubuntu.com/DebuggingKernelSuspend but it dosn't seem to bring relevant informations (however, I'll add the dmesg.txt to this bugreport) PS: to switch between graphiccards, I use "vga_switcheroo" and i have "vanilla"-ubuntu, no third party software. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.317 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Jun 8 20:54:43 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1486] Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU (Mobility Radeon HD 5450) [103c:1486] LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1486 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.1A dmi.chassis.asset.tag: CNU0250216 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP TouchSmart tm2 Notebook PC dmi.product.version: 048920252A2000122 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/10106
[Desktop-packages] [Bug 1853961] [NEW] Nautilus segfaults while transferring files via SFTP
Public bug reported: Every time I try to transfer a large file (or several small files) via Nautilus/SFTP, it ends up failing after a minute or so (connection closed). For example, I tried the same transfer twice, and got the following log: [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000] [505587.786958] Code: Bad RIP value. [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 7fa35323bc04 sp 7ffc3f4d7d90 error 4 in libc-2.30.so[7fa3531c8000+178000] [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85 If I try the same transfer using Filezilla, it completes flawlessly. Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems with the same server either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 26 07:48:38 2019 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'209' b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)' InstallationDate: Installed on 2018-05-14 (560 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - Everytime I try to transfer a bug file via Nautilus/SFTP, it ends up + Every time I try to transfer a file via Nautilus/SFTP, it ends up failing after a minute or so (connection closed). For example, I tried the same transfer twice, and got the following log: [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000] [505587.786958] Code: Bad RIP value. [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 7fa35323bc04 sp 7ffc3f4d7d90 error 4 in libc-2.30.so[7fa3531c8000+178000] [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85 If I try the same transfer using Filezilla, it completes flawlessly. + Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems + with the same server either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 26 07:48:38 2019 GsettingsChanges: - b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" - b'org.gnome.nautilus.window-state' b'sidebar-width' b'209' - b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)' + b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'209' + b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)' InstallationDate: Installed on 2018-05-14 (560 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago) usr_lib_nautilus: ** Description changed: - Every time I try to transfer a file via Nautilus/SFTP, it ends up + Every time I try to transfer a large file via Nautilus/SFTP, it ends up failing after a minute or so (connection closed). For example, I tried the same transfer twice, and got the following log: [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000] [505587.786958] Code: Bad RIP value. [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 7fa35323bc04 sp 7ffc3f4d7d90 error 4 in libc-2.30.so[7fa3531c8000+178000] [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85 If I try the same transfer using Filezilla, it
[Desktop-packages] [Bug 377322] Re: Nautilus sftp connection breaks spontaneously after a while, needing re-login to fix it
Seems like the bug is back in Nautilus 3.34 and Ubuntu 19.10 :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/377322 Title: Nautilus sftp connection breaks spontaneously after a while, needing re-login to fix it Status in gvfs: Expired Status in gvfs package in Ubuntu: Fix Released Bug description: When I have used an sftp connection for a while - started from Places/Connect to Server or from a bookmark - it breaks, typically after an hour or so. The only way to get an sftp connection to that server again is to re login to my computer. The error message I get is Could not open location 'sftp://..' DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken Sometimes when this happens, my computer freezes for about 60 seconds. I have Ubuntu 9.04 64 bits - error happened on Hardy also - on a computer with an AMD64 processor. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/377322/+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.
Sadly, I am not having Nvidia drivers installed and the fix about GRUB_CMDLINE_LINUX_DEFAULT="" doesn't work either for me. The only way I was able to suspend the login loop was to uninstall gdm3 and switch back to lightdm. I think it is not useful that I open up a new issue therefore I am posting my comment here. To sum it up: If I like to use gdm3 I am unable to login. Note: This is an upgraded laptop from 19.04 -> 19.10. -- 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: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Incomplete Status in gnome-session source package in Eoan: Incomplete Status in gnome-shell source package in Eoan: Incomplete 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
[Desktop-packages] [Bug 1723678] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1723678/+attachment/5307862/+files/Dependencies.txt -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1723678/+attachment/5307867/+files/monitors.xml.txt -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1723678/+attachment/5307866/+files/ShellJournal.txt -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1723678/+attachment/5307865/+files/ProcEnviron.txt -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1723678/+attachment/5307863/+files/GsettingsChanges.txt -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1723678/+attachment/5307864/+files/ProcCpuinfoMinimal.txt -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standar
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-02-21 (277 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-06 (19 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected eoan -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standar
I'm getting this in 19.10, could you revisit the won't fix? -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Same problem here. bluez 5.50, pulseaudio 13.0. Sony WH-1000XM3. Fiddling with the buttons on the headset makes it show up as a HCI device, after which it can be switched to A2DP. @Daniel van Vugt: could you reopen this and reassign it to either bluez or pulseaudio? At the very last it has nothing to do with alsa. I spoke with the pulseaudio maintainer, who thinks it's likely a bluez issue. -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
pavucontrol works good, I will try to backport this package to bionic, thanks. -- 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/1853584 Title: [18.04]Not able to adjust Audio input UI volume after connecting headset Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+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 1773207] Re: symbol lookup error: /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0: undefined symbol: sqlite3_bind_pointer
Output of ldd and dpkg is attached ** Attachment added: "dpkg-ldd.tar" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1773207/+attachment/5307849/+files/dpkg-ldd.tar -- 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/1773207 Title: symbol lookup error: /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker- data.so.0: undefined symbol: sqlite3_bind_pointer Status in nautilus package in Ubuntu: Incomplete Bug description: Just completed a do-release-ugrade from artful to bionic. Now nautilus does not launch any more. Following error message is displayed: symbol lookup error: /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker- data.so.0: undefined symbol: sqlite3_bind_pointer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.15.0-041500rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 24 17:46:39 2018 InstallationDate: Installed on 2015-11-05 (931 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-05-24 (0 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1773207/+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 1853732] Re: Gamepad HTML5 Button Input Unbuffered (get button down) from Unity WEbGL
You can grab a local copy at Github https://github.com/Crazykingjammy/PTP_WEBGL.git x10 may not be reliable enough. It may give a loading error. -- 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/1853732 Title: Gamepad HTML5 Button Input Unbuffered (get button down) from Unity WEbGL Status in chromium-browser package in Ubuntu: New Bug description: Description: The Gamepad HTML5 input is unbuffered. I am able to hold down the button and trigger constant event messages for button down. These is while checking for the values of Joystick Button 0-3; Check the build out here if you want : hippouniversity.x10host.com This bug is not present in other versions of Chrome tested on other devices I did not test on other versions of Bionic Chrome with the Jetson Nano. This bug is not present when using the Firefox browser for the same build. Device: NVIDIA Jetson Nano Description: Ubuntu 18.04.3 LTS Release: 18.04 chromium-browser: Installed: 78.0.3904.108-0ubuntu0.18.04.1 Candidate: 78.0.3904.108-0ubuntu0.18.04.1 Version table: *** 78.0.3904.108-0ubuntu0.18.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 Packages 500 http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu bionic/main arm64 Packages 100 /var/lib/dpkg/status 65.0.3325.181-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853732/+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 1773114] Re: Cannot copy file using 'cp' on a gvfs mount
As of 18.04 and still as at 19.10, this is all over the place. Errors left, right and centre. nautilus gives "Software caused connection abort" copying a file (but pressing F5 to refresh shows that the copy seemingly worked). gedit fails intermittently with the same error (possibly only on larger files, 32KB? not that 32KB is large). cp gives the error as reported initially above. I was copying using cp from one gio mount (smb) to another (sftp). Even gio copy was not a workaround. The only viable workaround that I found was to gio copy from the smb location to ~ and then copy from ~ to the sftp location. I was lucky that the file was not very big. (LibreOffice has its own problems with this setup.) Virtualisation of file systems is good functionality and I use it a lot but from 18.04 until now, taking the system as a whole, it has been badly broken. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1773114 Title: Cannot copy file using 'cp' on a gvfs mount Status in gvfs package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04, I can't anymore copy a file using the 'cp' command on a gvfs smb mount. For example, If I try to copy the file test.odp on a SMB shared folder, like this: cp -v test.odp /run/user/1000/gvfs/smb- share:domain=X,server=x,share=xxx,user=x/ I get the following error: cp: cannot fstat '/run/user/1000/gvfs/smb- share:domain=X,server=x,share=xxx,user=x//test.odp': Invalid argument A file 'test.odp' is created, but with size 0. I can delete any file on the shared folder using the 'rm' command. If I copy the file using the command 'gio copy', then it works as expected. This used to work in Ubuntu 16.04. Of course, I don't know if the problem is in the gvfs package or in some underlying component... System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit Kernel: 4.15.0-22-generic x86_64 Package: gvfs 1.36.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773114/+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 1792668] Re: gnome-calendar fails to sync, update, or cache
18.04, for me, the native Calendar app synced in Online Accounts > Nextcloud after syncing it does not removed deleted events that were part of a recurring series. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1792668 Title: gnome-calendar fails to sync, update, or cache Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Not sure if this is three different bugs or three symptoms of the same problem, but I am observing three different problematic behaviors on a fresh 18.04.1 install with latest updates: 1. Failure to sync: I have all my online google accounts active, but the calendar does not seem to grab new events from the online database. Nor does it transmit new events to the online database. Nor does it do any of these things when manually selecting the "synchronize" option under the menu. 2. Failure to update: I cannot manually add new events to the calendar. Although the app appears fully interactive, none of my interactions (e.g., adding an event) seem to actually get entered into the calendar, even locally. 3. Failure to cache: I have many local calendars displayed that the calendar app has appeared to pick up from other applications' data. I try to manually remove them by opening the calendars display, clicking on the calendar and clicking "remove." This appears to remove the calendar from this menu, but it doesn't remove it from being displayable. When I close and re-open the application, the local calendars have reappeared. Also, I cannot permanently rename calendars. When I close the app and re-open it, the calendar name has reverted to its original state. This might be related in part to another issue, where I have my UbuntuOne account active, but still get prompted regularly for my username and password from various programs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 15 15:06:10 2018 InstallationDate: Installed on 2018-09-12 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1792668/+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 1781428] Re: please enable snap mediation support
Installing 1:8.0-0ubuntu3.11 from xenial-proposed, the test plan and James' addition for mediation is preserved across snapd restart all works as expected. Marking as verification done. ** Description changed: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in- snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio-playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-interface- deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes + + $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface PlugSlot Notes audio-playback test-snapd-audio-record:audio-playback :audio-playback - audio-recordtest-snapd-audio-record:audio-record-- $ test-snapd-audio-record.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio- record/common/ $ test-snapd-audio-record.play
[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support
Installing 1:11.1-1ubuntu7.5 from bionic-proposed, the test plan and James' addition for mediation is preserved across snapd restart all works as expected. Marking as verification done. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface Plug
[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support
** Description changed: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in- snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio-playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-interface- deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For strict snaps with pulseaudio: - $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap + $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 - $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap + $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface PlugSlot Notes audio-playback test-snapd-audio-record:audio-playback :audio-playback - audio-recordtest-snapd-audio-record:audio-record-- $ test-snapd-audio-record.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio- record/common/ $ test-snapd-audio-record.play /var/snap/test-snapd-audio-record/common/Noise.wav && echo yes xcb_connection
[Desktop-packages] [Bug 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards
==3259== Invalid read of size 8 ==3259==at 0x77821D0: g_string_free (gstring.c:217) ==3259==by 0x1AD33072: poppler_attachment_finalize(_GObject*) (poppler-attachment.cc:88) ==3259==by 0x74D5011: g_object_unref (gobject.c:3340) ==3259==by 0x1AAE825D: ??? (ev-poppler.cc:3924) ==3259==by 0x5093B79: ev_job_attachments_run (ev-jobs.c:473) ==3259==by 0x5095C01: ev_job_thread (ev-job-scheduler.c:184) ==3259==by 0x5095C01: ev_job_thread_proxy (ev-job-scheduler.c:217) ==3259==by 0x7788194: g_thread_proxy (gthread.c:784) ==3259==by 0x7DD06DA: start_thread (pthread_create.c:463) ==3259==by 0x810988E: clone (clone.S:95) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards Status in evince package in Ubuntu: Fix Released Bug description: When trying to display the PDF file rfc8655.pdf from https://tools.ietf.org/pdf/rfc8655.pdf evince crashes: $ evince rfc8655.pdf Segmentation fault (core dumped) I would have expected the PDF file to be displayed. Instead, evince crashed and did not display the document. The built-in PDF renderer of Firefox 70.0 does display the PDF correctly. Since the segmentation fault hints at a memory management error triggered by external input this may have security implications. I did not investigate this any further. I do not set the "This bug is a security vulnerability" flag because I do not know if it really is (it probably is, but I have no proof) and I do not want this bug report to be private. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ evince --version GNOME Document Viewer 3.28.4 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" This is a fresh install of Ubuntu 18.04 LTS on x86-64 (the upgrade from 16.04 resulted in a non-booting system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+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 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards
Closing for the current serie since it works in 19.10, could be a candidate for a SRU to bionic if someone figures out the fix to backport ** Changed in: evince (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards Status in evince package in Ubuntu: Fix Released Bug description: When trying to display the PDF file rfc8655.pdf from https://tools.ietf.org/pdf/rfc8655.pdf evince crashes: $ evince rfc8655.pdf Segmentation fault (core dumped) I would have expected the PDF file to be displayed. Instead, evince crashed and did not display the document. The built-in PDF renderer of Firefox 70.0 does display the PDF correctly. Since the segmentation fault hints at a memory management error triggered by external input this may have security implications. I did not investigate this any further. I do not set the "This bug is a security vulnerability" flag because I do not know if it really is (it probably is, but I have no proof) and I do not want this bug report to be private. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ evince --version GNOME Document Viewer 3.28.4 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" This is a fresh install of Ubuntu 18.04 LTS on x86-64 (the upgrade from 16.04 resulted in a non-booting system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+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 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards
It seems fixed in newer serie but on bionic 0x7f7f6afb41d0 in g_string_free (string=0x, free_segment=free_segment@entry=1) at ../../../../glib/gstring.c:217 217 ../../../../glib/gstring.c: Aucun fichier ou dossier de ce type. (gdb) bt #0 0x7f7f6afb41d0 in g_string_free (string=0x, free_segment=free_segment@entry=1) at ../../../../glib/gstring.c:217 #1 0x7f7f58156073 in poppler_attachment_finalize(GObject*) (obj=0x5598f02eae90 [PopplerAttachment]) at ./glib/poppler-attachment.cc:88 #2 0x7f7f6b272012 in g_object_unref (_object=0x5598f02eae90) at ../../../../gobject/gobject.c:3340 #3 0x7f7f5839525e in pdf_document_attachments_get_attachments(EvDocumentAttachments*) (document=) at ev-poppler.cc:3924 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards Status in evince package in Ubuntu: Fix Released Bug description: When trying to display the PDF file rfc8655.pdf from https://tools.ietf.org/pdf/rfc8655.pdf evince crashes: $ evince rfc8655.pdf Segmentation fault (core dumped) I would have expected the PDF file to be displayed. Instead, evince crashed and did not display the document. The built-in PDF renderer of Firefox 70.0 does display the PDF correctly. Since the segmentation fault hints at a memory management error triggered by external input this may have security implications. I did not investigate this any further. I do not set the "This bug is a security vulnerability" flag because I do not know if it really is (it probably is, but I have no proof) and I do not want this bug report to be private. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ evince --version GNOME Document Viewer 3.28.4 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" This is a fresh install of Ubuntu 18.04 LTS on x86-64 (the upgrade from 16.04 resulted in a non-booting system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+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 1849888] Re: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1849888 Title: evince crashes (segmentation fault) when opening file rfc8655.pdf and other new-format Internet standards Status in evince package in Ubuntu: Incomplete Bug description: When trying to display the PDF file rfc8655.pdf from https://tools.ietf.org/pdf/rfc8655.pdf evince crashes: $ evince rfc8655.pdf Segmentation fault (core dumped) I would have expected the PDF file to be displayed. Instead, evince crashed and did not display the document. The built-in PDF renderer of Firefox 70.0 does display the PDF correctly. Since the segmentation fault hints at a memory management error triggered by external input this may have security implications. I did not investigate this any further. I do not set the "This bug is a security vulnerability" flag because I do not know if it really is (it probably is, but I have no proof) and I do not want this bug report to be private. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ evince --version GNOME Document Viewer 3.28.4 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" This is a fresh install of Ubuntu 18.04 LTS on x86-64 (the upgrade from 16.04 resulted in a non-booting system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1849888/+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.
Today, after an `apt upgrade' that brought me an updated grub, the problem came back. I logged on the second virtual console, edited /etc/default/grub, and found a new instance of the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" I commented it out, typed `sudo update-grub`, then `sudo reboot', and everything seems fine again. Why did this line ever come back after I removed it? I grepped my way around the system files in search for an answer and found a likely culprit to be `/var/lib/dpkg/info/grub-pc.postinst'. I don't quite understand what this post-installation script does, but it kind of looks like it is putting into /etc/default/grub some settings that come from debconf. I then ran `sudo dpkg-reconfigure grub-pc' and, when prompted from the default Linux command line, the text field was pre-filled with "quiet splash". I emptied it and left the other settings untouched. Now, my /etc/default/grub contains the line: GRUB_CMDLINE_LINUX_DEFAULT="" I hope the fix is definitive now. We'll see on the next upgrade of the grub packages. -- 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: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Incomplete Status in gnome-session source package in Eoan: Incomplete Status in gnome-shell source package in Eoan: Incomplete 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: n
[Desktop-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
Ubuntu Server 18.04.3 fresh install. Ethernet Unmanaged in Network Manager. SOLVED. FIXED, etc. - I created file /etc/netplan/01-network-manager-all.yaml Within I entered: # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager -- I edited /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg Within I ensured it only say: network: {config: disabled} --- I edit /etc/netplan/01-network-manager-all.yaml (If you don't nave then create) within it I entered: # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager rebooted - Wooho, It works! Thanks -- 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/1676547 Title: No network connectivity (NIC unmanaged) after upgrade Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety or zesty 3.5) Enable -proposed and download the new version of n-m "apt-get download network-manager" 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed and then reboot you should have a network connection. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install nplan, configure to set up static network on an ethernet device using nplan. 4) Upgrade to yakkety or zesty 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
This bug was fixed in the package mesa - 19.2.4-1ubuntu1 --- mesa (19.2.4-1ubuntu1) focal; urgency=medium * Merge from Debian. * revert-set-full-thread-affinity.diff: Dropped, qemu is fixed now in eoan and up. (LP: #1815889) -- Timo Aaltonen Wed, 20 Nov 2019 20:17:00 +0200 ** Changed in: mesa (Ubuntu) Status: In Progress => 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Won't Fix Status in QEMU: Fix Released Status in mesa package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Invalid Status in mesa source package in Disco: Fix Released Status in mesa source package in Eoan: Won't Fix Status in qemu source package in Eoan: Fix Released Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1853894] [NEW] Strange Hang with old SWT Apps
Public bug reported: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1853894 Title: Strange Hang with old SWT Apps Status in gtk+2.0 package in Ubuntu: New Bug description: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1853894/+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 1853893] [NEW] Firefox maximized CSD using double space on Plasma with "global menu" widget
Public bug reported: Kubuntu 19.10 Firefox 70.0.1+build1-0ubuntu0.19.10.1 Using Firefox's CSD on KDE Plasma and using KDE's "global menu" widget in a panel, Firefox takes useless space for the "title bar". Screenshot here: https://pasteboard.co/IImEuh3.png By right clicking on the empty space in the "title bar", this space disappears for a few seconds giving this: https://pasteboard.co/IImFha5.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: KDE Date: Mon Nov 25 19:57:39 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox InstallationDate: Installed on 2019-11-14 (11 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1853893 Title: Firefox maximized CSD using double space on Plasma with "global menu" widget Status in firefox package in Ubuntu: New Bug description: Kubuntu 19.10 Firefox 70.0.1+build1-0ubuntu0.19.10.1 Using Firefox's CSD on KDE Plasma and using KDE's "global menu" widget in a panel, Firefox takes useless space for the "title bar". Screenshot here: https://pasteboard.co/IImEuh3.png By right clicking on the empty space in the "title bar", this space disappears for a few seconds giving this: https://pasteboard.co/IImFha5.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: KDE Date: Mon Nov 25 19:57:39 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox InstallationDate: Installed on 2019-11-14 (11 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1853893/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 I tried all these suggestion, no joy. Why won't dev fix? Please at least tell us what we're doing wrong. I may have to install Desktop version because KVM/QEMU isn't playing nice with seeing the network connection. Now what, reinstall every server manually that I use on my hosts so those KVMs work. I was hoping to avoid using VBox. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
Just verified that 2-sided portrait (long edge) printing does indeed work on this printer in 19.04, so this is a regression. I'm not sure which of the three drivers it's using. Let me know if you want me to attach any files from 19.04. -- 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/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: New Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1853880] Re: package libxcb-present0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1853880 Title: package libxcb-present0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxcb package in Ubuntu: New Bug description: Installation failed during upgradation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxcb-present0:i386 1.11.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 25 22:39:15 2019 DistUpgraded: 2017-03-19 23:16:17,380 WARNING no activity on terminal for 300 seconds (Preparing to configure libapt-inst2.0 (amd64)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libxcb-present0:i386:1.11.1-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0569] InstallationDate: Installed on 2012-07-20 (2683 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 MachineType: Dell Inc. Inspiron 5520 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-96-generic root=UUID=c6f93b82-e3c9-42f0-9e0c-05438c56139b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: libxcb Title: package libxcb-present0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2017-03-19 (980 days ago) dmi.bios.date: 05/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0Y0X1K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/17/2012:svnDellInc.:pnInspiron5520:pvrA07:rvnDellInc.:rn0Y0X1K:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5520 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Nov 25 22:03:45 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1853880/+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 1853879] [NEW] Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
Public bug reported: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.localDell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: New Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-lon
[Desktop-packages] [Bug 1853880] [NEW] package libxcb-present0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Public bug reported: Installation failed during upgradation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxcb-present0:i386 1.11.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 25 22:39:15 2019 DistUpgraded: 2017-03-19 23:16:17,380 WARNING no activity on terminal for 300 seconds (Preparing to configure libapt-inst2.0 (amd64)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libxcb-present0:i386:1.11.1-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0569] InstallationDate: Installed on 2012-07-20 (2683 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 MachineType: Dell Inc. Inspiron 5520 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-96-generic root=UUID=c6f93b82-e3c9-42f0-9e0c-05438c56139b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: libxcb Title: package libxcb-present0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2017-03-19 (980 days ago) dmi.bios.date: 05/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0Y0X1K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/17/2012:svnDellInc.:pnInspiron5520:pvrA07:rvnDellInc.:rn0Y0X1K:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5520 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Nov 25 22:03:45 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1853880 Title: package libxcb-present0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxcb package in Ubuntu: New Bug description: Installation failed during upgradation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxcb-present0:i386 1.11.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 25 22:39:15 2019 DistUpgraded: 2017-03-19 23:16:17,380 WARNING no activity on terminal for 300 seconds (Preparing to configure libapt-inst2.0 (amd64)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubunt
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Thanks Olivier! Do we/you need to consider any process improvements to avoid this happening again in future? -- 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/1851936 Title: User profile won't load after upgrade - prompt to create new profile Status in firefox package in Ubuntu: Fix Committed Bug description: Did upgrade to focal fossa from standard Ubuntu 19.10. Existing firefox profile won't load on starting, instead application wants new default profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 70.0.1+build1-0ubuntu2 Uname: Linux 5.3.9-050309-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1861 F pulseaudio /dev/snd/controlC0: stefan 1861 F pulseaudio BuildID: 20191031000133 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 14:49:28 2019 DefaultProfileIncompatibleExtensions: Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org 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} DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfilePrefSources: prefs.js ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-05-02 (190 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.178.1 dev enp30s0 proto dhcp metric 100 169.254.0.0/16 dev enp30s0 scope link metric 1000 192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44 metric 100 MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=70.0.1/20191031000133 (In use) Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date) RunningIncompatibleAddons: True SourcePackage: firefox SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317 UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.80 dmi.board.name: AB350M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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
If I log out the first user, the second user suddenly has sound. And it didn't do this on Friday, when the same programs were running before the user switch. -- 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: Incomplete 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 1851931] Re: [snap] regression: OSK does not appear automatically when selecting some text fields
It worked with the 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/1851931 Title: [snap] regression: OSK does not appear automatically when selecting some text fields Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Committed -- 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/1851936 Title: User profile won't load after upgrade - prompt to create new profile Status in firefox package in Ubuntu: Fix Committed Bug description: Did upgrade to focal fossa from standard Ubuntu 19.10. Existing firefox profile won't load on starting, instead application wants new default profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 70.0.1+build1-0ubuntu2 Uname: Linux 5.3.9-050309-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1861 F pulseaudio /dev/snd/controlC0: stefan 1861 F pulseaudio BuildID: 20191031000133 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 14:49:28 2019 DefaultProfileIncompatibleExtensions: Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org 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} DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfilePrefSources: prefs.js ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-05-02 (190 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.178.1 dev enp30s0 proto dhcp metric 100 169.254.0.0/16 dev enp30s0 scope link metric 1000 192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44 metric 100 MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=70.0.1/20191031000133 (In use) Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date) RunningIncompatibleAddons: True SourcePackage: firefox SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317 UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.80 dmi.board.name: AB350M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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
Yes, it seems to be a 'multiple users logged in' thing. Use the sound in one user, then - at some seemingly random point that's NOT while something is actually playing - discover that the sound system is disabled. It's possible that both users have it not working, or one to work and one not to. Attached is the logs for a second - not using the GP107GL chipset - PC where it's just happened. Sound was working fine in one user (and still is) and disabled in the second. They logged in at about 16:30... ** Attachment added: "logs" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5307739/+files/logs -- 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: Incomplete 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 1853870] Re: Nautilus says "Preparing" when it is emptying the trash and does not update its status until the Trash is done being emptied.
Thank you for your bug report. Could you give some details on the content of the trash at the time you emptied it? Do you have enough data for it to take a while, is that on a local partition? It's likely an upstream issue and would be good to report to them on https://gitlab.gnome.org/GNOME/nautilus/issues/ ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1853870 Title: Nautilus says "Preparing" when it is emptying the trash and does not update its status until the Trash is done being emptied. Status in nautilus package in Ubuntu: New Bug description: When emptying the trash (I used the "Empty Deleted Items" button at the top of the file list in Nautilus) a dialog pops up with a progress bar at 0% saying "Preparing". It stays at 0% for the duration of the empty and then disappears when it's done instead of updating. Steps to Reproduce: 1. Put items in the trash 2. Empty the trash by selecting "Empty" 3. Notice the progress bar is stuck at 0% saying "Preparing" Expected Results: Progress Bar updates as items are thrown away. Actual Results: Nautilus says "Preparing" until the trash is finished being emptied. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 11:14:06 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853870/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Dan, you're right, the focal version was built before the eoan version. I have uploaded firefox 70.0.1+build1-0ubuntu3 to focal to work around the problem. -- 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/1851936 Title: User profile won't load after upgrade - prompt to create new profile Status in firefox package in Ubuntu: Confirmed Bug description: Did upgrade to focal fossa from standard Ubuntu 19.10. Existing firefox profile won't load on starting, instead application wants new default profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 70.0.1+build1-0ubuntu2 Uname: Linux 5.3.9-050309-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1861 F pulseaudio /dev/snd/controlC0: stefan 1861 F pulseaudio BuildID: 20191031000133 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 14:49:28 2019 DefaultProfileIncompatibleExtensions: Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org 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} DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfilePrefSources: prefs.js ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-05-02 (190 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.178.1 dev enp30s0 proto dhcp metric 100 169.254.0.0/16 dev enp30s0 scope link metric 1000 192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44 metric 100 MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=70.0.1/20191031000133 (In use) Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date) RunningIncompatibleAddons: True SourcePackage: firefox SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317 UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.80 dmi.board.name: AB350M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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 1832787] Re: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome
Any chance fontconfig 2.13 could be backported to bionic? This is a seriously annoying issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1832787 Title: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome Status in fontconfig package in Ubuntu: Confirmed Bug description: fontconfig version: 2.12.6-0ubuntu2 Related: https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu- usage-for-30-seconds-when-launching-chromium https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 https://bugzilla.mozilla.org/show_bug.cgi?id=1411338 Steps to reproduce: 1) Launch firefox, open a few tabs 2) Launch chrome 3) Go back to firefox, and notice it starts being very slow, switching tabs do nothing (the content area remains blank). 4) Backport fontconfig 2.13 from cosmic to bionic 5) Try to reproduce 1-3, be happy because it is now working fine! I backported 2.13.0-5ubuntu3 from cosmic to bionic, if that helps. I don't have the right setup right now to do a bisect from upstream or from debian patches sadly. ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1832787/+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 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan
Ok, so that's a regression, probably caused by the deb->snap transition. I'll remove the duplicate status then. ** This bug is no longer a duplicate of bug 1697641 Chromium doesn't open OSK under GNOME Shell ** Summary changed: - On-screen keyboard does not appear automatically when selecting some text fields on Eoan + [snap] regression: OSK does not appear automatically when selecting some text fields ** Tags added: sanp ** Tags removed: sanp ** Tags added: 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/1851931 Title: [snap] regression: OSK does not appear automatically when selecting some text fields Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1853870] [NEW] Nautilus says "Preparing" when it is emptying the trash and does not update its status until the Trash is done being emptied.
Public bug reported: When emptying the trash (I used the "Empty Deleted Items" button at the top of the file list in Nautilus) a dialog pops up with a progress bar at 0% saying "Preparing". It stays at 0% for the duration of the empty and then disappears when it's done instead of updating. Steps to Reproduce: 1. Put items in the trash 2. Empty the trash by selecting "Empty" 3. Notice the progress bar is stuck at 0% saying "Preparing" Expected Results: Progress Bar updates as items are thrown away. Actual Results: Nautilus says "Preparing" until the trash is finished being emptied. Description:Ubuntu 19.10 Release:19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 11:14:06 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Image of Nautilus when it is stuck on "Preparing"" https://bugs.launchpad.net/bugs/1853870/+attachment/5307731/+files/Screenshot%20from%202019-11-25%2011-13-59.png -- 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/1853870 Title: Nautilus says "Preparing" when it is emptying the trash and does not update its status until the Trash is done being emptied. Status in nautilus package in Ubuntu: New Bug description: When emptying the trash (I used the "Empty Deleted Items" button at the top of the file list in Nautilus) a dialog pops up with a progress bar at 0% saying "Preparing". It stays at 0% for the duration of the empty and then disappears when it's done instead of updating. Steps to Reproduce: 1. Put items in the trash 2. Empty the trash by selecting "Empty" 3. Notice the progress bar is stuck at 0% saying "Preparing" Expected Results: Progress Bar updates as items are thrown away. Actual Results: Nautilus says "Preparing" until the trash is finished being emptied. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 11:14:06 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853870/+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 1845795] Re: authentication window got stuck over other windows at top left
@Sebastien Bacher - sure, tonight. How should I do this? (should I wait for the next occurance, or is it still there?) -- 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/1845795 Title: authentication window got stuck over other windows at top left Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845795/+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 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan
*** This bug is a duplicate of bug 1697641 *** https://bugs.launchpad.net/bugs/1697641 No it doesn't. It worked in disco. -- 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/1851931 Title: On-screen keyboard does not appear automatically when selecting some text fields on Eoan Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1852645] Profile3Prefs.txt
apport information ** Attachment added: "Profile3Prefs.txt" https://bugs.launchpad.net/bugs/1852645/+attachment/5307729/+files/Profile3Prefs.txt -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-09 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: usr/share/applications/firefox.desktop] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=70.0.1/20191030021342 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) Profile2 - LastVersion=72.0a1/20191114055112 (Out of date) Tags: eoan Uname: Linux 5.3.0-23-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/firefox/+bug/1852645/+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 1852645] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1852645/+attachment/5307727/+files/ProcCpuinfoMinimal.txt -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-09 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: usr/share/applications/firefox.desktop] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=70.0.1/20191030021342 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) Profile2 - LastVersion=72.0a1/20191114055112 (Out of date) Tags: eoan Uname: Linux 5.3.0-23-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/firefox/+bug/1852645/+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 1852645] HookError_source_firefox.txt
apport information ** Attachment added: "HookError_source_firefox.txt" https://bugs.launchpad.net/bugs/1852645/+attachment/5307726/+files/HookError_source_firefox.txt -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-09 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: usr/share/applications/firefox.desktop] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=70.0.1/20191030021342 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) Profile2 - LastVersion=72.0a1/20191114055112 (Out of date) Tags: eoan Uname: Linux 5.3.0-23-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/firefox/+bug/1852645/+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 1852645] Re: WebAudio API does not behave as expected (Cannot mute videos)
apport information ** Tags added: apport-collected eoan ** Description changed: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + BuildID: 20191031091608 + CurrentDesktop: ubuntu:GNOME + DefaultProfileExtensions: extensions.sqlite corrupt or missing + DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + DefaultProfileLocales: extensions.sqlite corrupt or missing + DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 + DefaultProfileThemes: extensions.sqlite corrupt or missing + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-11-09 (16 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: usr/share/applications/firefox.desktop] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 + Profile3Extensions: extensions.sqlite corrupt or missing + Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + Profile3Locales: extensions.sqlite corrupt or missing + Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 + Profile3PrefSources: prefs.js + Profile3Themes: extensions.sqlite corrupt or missing + Profiles: + Profile3 - LastVersion=70.0.1/20191030021342 (Out of date) + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=70.0.1/20191031091608 (In use) + Profile2 - LastVersion=72.0a1/20191114055112 (Out of date) + Tags: eoan + Uname: Linux 5.3.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1852645/+attachment/5307725/+files/Dependencies.txt -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing
[Desktop-packages] [Bug 1852645] Re: WebAudio API does not behave as expected (Cannot mute videos)
Very strangely, I can no longer reproduce this bug either. -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-09 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: usr/share/applications/firefox.desktop] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=70.0.1/20191030021342 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) Profile2 - LastVersion=72.0a1/20191114055112 (Out of date) Tags: eoan Uname: Linux 5.3.0-23-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/firefox/+bug/1852645/+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 1852645] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1852645/+attachment/5307728/+files/ProcEnviron.txt -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-09 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: usr/share/applications/firefox.desktop] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=70.0.1/20191030021342 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) Profile2 - LastVersion=72.0a1/20191114055112 (Out of date) Tags: eoan Uname: Linux 5.3.0-23-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/firefox/+bug/1852645/+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 1852645] Re: WebAudio API does not behave as expected (Cannot mute videos)
I cannot observe the problem here. I tested in virtual machines, 18.04 and 19.10, version 70.0.1 from the Ubuntu archive in both, and played with different values for the gain in your JSFiddle. When setting the value to 0 there is no sound to be heard. Can you please run "apport-collect 1852645" ? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1852645 Title: WebAudio API does not behave as expected (Cannot mute videos) Status in firefox package in Ubuntu: Incomplete Bug description: I initially posted this bug to the Firefox issue tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined it was specific to the Ubuntu package. When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the behavior in the Firefox 70 build that you can get from Mozilla's website. However, with the Ubuntu build, audio is still heard. --- Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1 via the Ubuntu update manager. Firefox package version: firefox: Installed: 70.0.1+build1-0ubuntu0.19.10.1 Candidate: 70.0.1+build1-0ubuntu0.19.10.1 Version table: *** 70.0.1+build1-0ubuntu0.19.10.1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1852645/+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 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan
*** This bug is a duplicate of bug 1697641 *** https://bugs.launchpad.net/bugs/1697641 @Efthimios: does it work if you do the following: export ACCESSIBILITY_ENABLED=1 chromium --force-renderer-accessibility ** This bug has been marked a duplicate of bug 1697641 Chromium doesn't open OSK under GNOME Shell -- 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/1851931 Title: On-screen keyboard does not appear automatically when selecting some text fields on Eoan Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1853860] Re: Nautilus will show two paritions as mounted for a USB even after that USB had a new image written to it.
Thank you for your bug report, that looks like an upstream. Could you report it to them on https://gitlab.gnome.org/GNOME/nautilus/issues/ ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1853860 Title: Nautilus will show two paritions as mounted for a USB even after that USB had a new image written to it. Status in nautilus package in Ubuntu: New Bug description: When the startup disk creator writes a new image to the disk, it still displays the partitions of the USB prior to the image being written, which is problematic because after the image is written, nautilus changes all of the partitions on the sidebar to the first partition on the USB, and attempting to click on any mounted drive other than the first one listed causes nautilus to give a disk error saying there may be a bad superblock as the drive could not be opened. Steps to Reproduce: 1. Insert a USB Drive with multiple partitions 2. Mount two of those partitions 3. Write an image to the USB drive via Startup Disk Creator 4. Notice how Nautilus shows the drives as accessible 5. Wait until the image writing is complete 6. Go back to Nautilus 7. Notice how there are two entries for the USB with the new image on it 8. Click on the second entry Expected Results: 1. Nautilus should not show USB drives that are having its entire contents formatted and repartitioned 2. Even if 1. was intended behavior, nautilus should only have the first partition of the usb with the new image written open 3. There should be no superblock error, as nautilus should not have gotten to the point in which it reports the error in the first place. Actual Results: Nautilus says it is unable to access the 2nd partition even though it is not even mounted because it displayed the partitions of the usb prior to the ubuntu image being written to the USB and did not update its UI to show the USB has a new name and only has one partition mounted (the first one with the OS info on it). Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status 10:1 This issue occurred on November 25, 2019, at around 10:10 - 10:15 AM, EDT. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 09:58:04 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853860/+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 1780678] Re: [snap] Chromium cannot use WebUSB
@Erik: I just published an updated version of the chromium snap with the additional raw-usb plug in the candidate/raw-usb channel. Can you please test and report whether this gives you access to your USB device? snap refresh chromium --channel=candidate/raw-usb snap connect chromium:raw-usb If it doesn't, can you please share the output of "journalctl -f | grep DEN" running in another terminal window while observing the problem? -- 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/1780678 Title: [snap] Chromium cannot use WebUSB Status in chromium-browser package in Ubuntu: New Bug description: We're running into a weird bug on Ubuntu : WebUSB works on Chrome but doesn't on Chromium! Here's our udev rule: https://workshop.numworks.com/files/drivers/linux/50-numworks- calculator.rules It uses the uaccess tag which adds an ACL to the created file in /dev/ so that the current logged-in user has RW access to the corresponding /dev/bus/usb/** device. Apparently that's the way to go, since relying on groups is fragile (not all distros use the "plugdev" group for example). That udev rules works just fine. When using a command-line utility such as "dfu-tool", the USB device is seen and can be read from and written to. It also works just fine on Chrome. But Chromium gives us an "access denied" error. It lists the device, we do get the pop-up, but we cannot communicate. On Chromium, chrome://device-log says : Failed to open /dev/bus/usb/001/011: Operation not permitted (1) Here are the infos on said file: user@virtualbox:~$ ls -l /dev/bus/usb/001/011 crw-rw-r--+ 1 root root 189, 10 Jul 3 11:35 /dev/bus/usb/001/011 As you can see, the file is owned root/root, but has an ACL (as shown by the "+" symbol) user@virtualbox:~$ getfacl /dev/bus/usb/001/011 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/011 # owner: root # group: root user::rw- user:user:rw- group::rw- mask::rw- other::r-- Here the ACL supposedely gives RW access to "user" who is indeed the current logged-in user, and the user running Chromium and Chrome. For reference : - Latest stable Ubuntu (18.04) - Using the Chromium that ships with Ubuntu (from the Ubuntu Software app. attached chrome://version page) - And using latest stable Chrome from google.com (attached chrome://version page) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1780678/+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 1853784] Re: Format button has no effect when I right click a USB and select Format
It does not work better in Xorg. -- 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/1853784 Title: Format button has no effect when I right click a USB and select Format Status in Nautilus: New Status in nautilus package in Ubuntu: Incomplete Bug description: Whenever I boot up ubuntu and attempt to format a plugged-in or mounted USB, the Format button has no effect when clicked on; not even an error message. If there is an error, Ubuntu should let me know or not allow me to format by disabling to format option. Steps to Reproduce: 1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this will be the USB to attempt to format) 2. Log in and open Files 3. Right-click the USB and select "Format" Expected Results: Either the Format menu appears, an error message appears if I am unable to format the disk, or the Format button is disabled. Actual Results: Files allows the format button to be clicked, but nothing happens when it is clicked on. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:22:27 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1853784/+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 1853860] [NEW] Nautilus will show two paritions as mounted for a USB even after that USB had a new image written to it.
Public bug reported: When the startup disk creator writes a new image to the disk, it still displays the partitions of the USB prior to the image being written, which is problematic because after the image is written, nautilus changes all of the partitions on the sidebar to the first partition on the USB, and attempting to click on any mounted drive other than the first one listed causes nautilus to give a disk error saying there may be a bad superblock as the drive could not be opened. Steps to Reproduce: 1. Insert a USB Drive with multiple partitions 2. Mount two of those partitions 3. Write an image to the USB drive via Startup Disk Creator 4. Notice how Nautilus shows the drives as accessible 5. Wait until the image writing is complete 6. Go back to Nautilus 7. Notice how there are two entries for the USB with the new image on it 8. Click on the second entry Expected Results: 1. Nautilus should not show USB drives that are having its entire contents formatted and repartitioned 2. Even if 1. was intended behavior, nautilus should only have the first partition of the usb with the new image written open 3. There should be no superblock error, as nautilus should not have gotten to the point in which it reports the error in the first place. Actual Results: Nautilus says it is unable to access the 2nd partition even though it is not even mounted because it displayed the partitions of the usb prior to the ubuntu image being written to the USB and did not update its UI to show the USB has a new name and only has one partition mounted (the first one with the OS info on it). Description:Ubuntu 19.10 Release:19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status 10:1 This issue occurred on November 25, 2019, at around 10:10 - 10:15 AM, EDT. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 09:58:04 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1853860 Title: Nautilus will show two paritions as mounted for a USB even after that USB had a new image written to it. Status in nautilus package in Ubuntu: New Bug description: When the startup disk creator writes a new image to the disk, it still displays the partitions of the USB prior to the image being written, which is problematic because after the image is written, nautilus changes all of the partitions on the sidebar to the first partition on the USB, and attempting to click on any mounted drive other than the first one listed causes nautilus to give a disk error saying there may be a bad superblock as the drive could not be opened. Steps to Reproduce: 1. Insert a USB Drive with multiple partitions 2. Mount two of those partitions 3. Write an image to the USB drive via Startup Disk Creator 4. Notice how Nautilus shows the drives as accessible 5. Wait until the image writing is complete 6. Go back to Nautilus 7. Notice how there are two entries for the USB with the new image on it 8. Click on the second entry Expected Results: 1. Nautilus should not show USB drives that are having its entire contents formatted and repartitioned 2. Even if 1. was intended behavior, nautilus should only have the first partition of the usb with the new image written open 3. There should be no superblock error, as nautilus should not have gotten to the point in which it reports the error in the first place. Actual Results: Nautilus says it is unable to access the 2nd partition even though it is not even mounted because it displayed the partitions of the usb prior to the ubuntu image being written to the USB and did not update its UI to show the USB has a new name and only has one partition mounted (the first one with the OS info on it). Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubun
[Desktop-packages] [Bug 1850893] Re: chromium-browser does not resolve any names
The key to the problem likely lies in the following: « Regarding the DNS setup: YES my DNS setup is not the default. I have disabled the systemd DNS crap and fallen back on /etc/resolv.conf - in that way it is non-default. » Can you run "journalctl -f | grep DEN" in a terminal, then run chromium, observe how it fails to resolve names, and share the output of the journalctl command? -- 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/1850893 Title: chromium-browser does not resolve any names Status in chromium-browser package in Ubuntu: Incomplete Bug description: OS: === Description: Ubuntu 19.10 Release: 19.10 Chromium Browser: = Version 78.0.3904.70 (Official Build) snap (64-bit) DNS resolution does not work in Chromium Browser since Ubuntu updated from 18.04 -> 19.10 and chromium moved from package to SNAP. DNS works in Mozilla Firefox (being used to submit this bug report) as well as in Google Chrome (Version 78.0.3904.87 (Official Build) (64-bit)) See attached screenshots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLSwNV1BaQhYdAQOANB14KlKVpVZUnSUOUFS7jACzAIHAgQCBgJUAqcABAQEBAjqAGHE4LUBYLEUACSUhAAAe/QAySB5REQAKICAgICAg/ABDMjRGMzkwCiAgICAg/wBINFpNNTAwMTE1CiAgAVMCAxrxRpAEHxMSAyMJBweDAQAAZgMMABAAgAEdALxS0B4guChVQAklIQAAHowK0JAgQDEgDEBVAAklIQAAGIwK0Iog4C0QED6WAAklIQAAGAAAyQ== modes: 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1440x900 1280x800 1280x720 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAJ5fgGAAEaAQSlHRB4AviQnllVnCYaUFQBAQEBAQEBAQEBAQEBAQEBPhxWoFAAFjAwIDYAJaUQAAAanhZWoFAAFjAwIDYAJaUQAAAaAgARQ/8PPOZBRjrmAAM= modes: 1366x768 1366x768 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/shoor-home xfs194G 171G 24G 88% /home tmpfs tmpfs 7.8G 186M 7.6G 3% /dev/shm /dev/mapper/shoor-home xfs194G 171G 24G 88% /home DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-05-02 (558 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP ProBook 430 G5 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=2dbdc9ef-f608-4d62-83ff-348f47118c15 ro resume=UUID=ff6eebb5-8c92-4fad-af15-00ccb0e08484 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.97 (021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}) Snap.ChromiumVersion: Chromium 78.0.3904.97 snap Tags: eoan snap Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo tty vboxusers _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.01.07 dmi.board.name: 8377 dmi.board.vendor: HP dmi.board.version: KBC Version 02.21.00 dmi.chassis.asset.tag: 5CD750DHFQ dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook430G5:pvr:rvnHP:rn8377:rvrKBCVersion02.21.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 430 G5 dmi.product.sku: 3EB74PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850893/+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 1853784] Re: Format button has no effect when I right click a USB and select Format
** Changed in: nautilus Status: Unknown => New -- 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/1853784 Title: Format button has no effect when I right click a USB and select Format Status in Nautilus: New Status in nautilus package in Ubuntu: Incomplete Bug description: Whenever I boot up ubuntu and attempt to format a plugged-in or mounted USB, the Format button has no effect when clicked on; not even an error message. If there is an error, Ubuntu should let me know or not allow me to format by disabling to format option. Steps to Reproduce: 1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this will be the USB to attempt to format) 2. Log in and open Files 3. Right-click the USB and select "Format" Expected Results: Either the Format menu appears, an error message appears if I am unable to format the disk, or the Format button is disabled. Actual Results: Files allows the format button to be clicked, but nothing happens when it is clicked on. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:22:27 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1853784/+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 1853784] Re: Format button has no effect when I right click a USB and select Format
Upstream https://gitlab.gnome.org/GNOME/nautilus/issues/1265 does looks similar ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1265 https://gitlab.gnome.org/GNOME/nautilus/issues/1265 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1265 Importance: Unknown Status: Unknown -- 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/1853784 Title: Format button has no effect when I right click a USB and select Format Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Incomplete Bug description: Whenever I boot up ubuntu and attempt to format a plugged-in or mounted USB, the Format button has no effect when clicked on; not even an error message. If there is an error, Ubuntu should let me know or not allow me to format by disabling to format option. Steps to Reproduce: 1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this will be the USB to attempt to format) 2. Log in and open Files 3. Right-click the USB and select "Format" Expected Results: Either the Format menu appears, an error message appears if I am unable to format the disk, or the Format button is disabled. Actual Results: Files allows the format button to be clicked, but nothing happens when it is clicked on. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:22:27 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1853784/+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 1853850] Re: nautilus crashed with signal 5 whenever I attempt to format a USB
** Information type changed from Private to Public -- 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/1853850 Title: nautilus crashed with signal 5 whenever I attempt to format a USB Status in nautilus package in Ubuntu: New Bug description: Whenever I attempt to format a USB I previous used for a live install back into a regular FAT disk, nautilus reports "gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Trace/breakpoint trap (core dumped)" and then crashes. I ran "ubuntu-bug nautilus" right after I clicked the Format button, right before the crash itself. To reproduce the issue: 1. Insert an ubuntu live usb 2. Open Files 3. Right-click on the USB 4. Select Format 5. If the format menu appears, click the red format button Expected Results: Either the USB partitions are cleared and the entire disk is formatted to be FAT (preferred), or if that is not an option, Files should warn me it has a partition table and close instead of opening the Format Menu and then crashing later. Actual Results: Gnome-Disks alerts the USB cannot be formatted, and then nautilus crashes. Description: Ubuntu 19.10 Release: 19.10 nautilus nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:04:09 2019 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1570456987 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: nautilus ProcCwd: /home/edwin/Downloads/llvm-project-llvmorg-8.0.1/build ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853850/+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
Re: [Desktop-packages] [Bug 1853739] Re: normal usage then all apps stopped and UI dropped to desktop
Thanks for the clarification. On Mon, Nov 25, 2019 at 11:36 AM Sebastien Bacher wrote: > Looks like the xserver hit an error > BUG: triggered 'if (axnum >= dev->valuator->numAxes)' > BUG: ../../Xi/exevents.c:2103 in InitValuatorAxisStruct() > > ** Summary changed: > > - normal usage then all apps stopped and UI dropped to desktop > + BUG: triggered 'if (axnum >= dev->valuator->numAxes)' > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1853739 > > Title: > BUG: triggered 'if (axnum >= dev->valuator->numAxes)' > > Status in xorg package in Ubuntu: > New > > Bug description: > UI stopped responding > ctrl +alt +f3 to htop > 1 of the cpus at 100% > > I see whoopsie is at 100% > then another app > > ctrl +alt +f2 > back to desktop > > no apps are running > terminal > apport-bug xorg > > I know running apport-bug xorg from terminal will FAIL > > ubuntu 19.1 is crashing 5X per week at minimum! > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 > Uname: Linux 5.3.0-23-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Nov 24 12:13:45 2019 > DistUpgraded: 2019-10-23 09:33:56,809 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistroCodename: eoan > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 2nd Generation Core Processor Family Integrated > Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family > Integrated Graphics Controller [1043:84ca] > InstallationDate: Installed on 2015-08-23 (1553 days ago) > InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 > (20150805) > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic > root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: Upgraded to eoan on 2019-10-23 (32 days ago) > dmi.bios.date: 07/21/2014 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2501 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: P8Z77-V LX > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Asset-1234567890 > dmi.chassis.type: 3 > dmi.chassis.vendor: Chassis Manufacture > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: > 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 > version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 > version.libdrm2: libdrm2 2.4.99-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core > 2:1.20.5+git20191008-0ubuntu1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 > 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 > xserver.bootTime: Mon Aug 20 17:24:57 2018 > xserver.configfile: default > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > > xserver.version: 2:1.18.4-0ubuntu0.7 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853739/+subscriptions > -- 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/1853739 Title: BUG: triggered 'if (axnum >= dev->valuator->numAxes)' Status in xorg package in Ubuntu: New Bug description: UI stopped responding ctrl +alt +f3 to htop 1 of the cpus at 100% I see whoopsie is at 100% then another app ctrl +alt +f2 back to desktop no apps are running terminal apport-bug xorg I know running apport-bug xorg from terminal will FAIL ubuntu 19.1 is crashing 5X per week at minimum! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersio
[Desktop-packages] [Bug 1851944] Re: Connection problem with account 'laposte.net'
@No: are you still seeing this problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1851944 Title: Connection problem with account 'laposte.net' Status in thunderbird package in Ubuntu: Incomplete Bug description: IMAP access to laposte.net is wrong : mails are not downloaded to my computer (time-out), neither new mails, nor content for already downloaded mails. Nevertheless I'm still able to sent mail via SMTP on Thunderbird. The webmail on laposte is OK, though. Mails from my Microsoft account are downloaded smouthly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: norb 3642 F pulseaudio /dev/snd/controlC1: norb 3642 F pulseaudio /dev/snd/controlC2: norb 3642 F pulseaudio /dev/snd/controlC0: norb 3642 F pulseaudio BuildID: 20191007090452 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 17:04:52 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-07-12 (1214 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090452 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.G0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING PRO (MS-7984) 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.:bvr1.G0:bd06/16/2018:svnMSI:pnMS-7984:pvr1.0:rvnMSI:rnZ170AGAMINGPRO(MS-7984):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7984 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1851944/+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 1311195] Re: [touchscreen] Cannot move window by dragging title bar with default gtk decoration
Thanks for the confirmation Alexander. This sounds like an upstream bug. Could you please report it at https://chromiumbugs.appspot.com/, and share the link to the upstream bug here? -- 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/1311195 Title: [touchscreen] Cannot move window by dragging title bar with default gtk decoration Status in chromium-browser package in Ubuntu: Confirmed Bug description: With the default GTK decoration, it is not possible to drag the title bar of Chromium to move the window. When the setting is changed to "system" it works fine as any other window. Expected: By default chromium should be configured with system decorations. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 22 17:58:18 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 455G 4,0G 427G 1% /\nnone tmpfs 4,0K 0 4,0K 0% /sys/fs/cgroup\nudev devtmpfs 1,9G 4,0K 1,9G 1% /dev\ntmpfs tmpfs 384M 1,1M 383M 1% /run\nnone tmpfs 5,0M 0 5,0M 0% /run/lock\nnone tmpfs 1,9G 8,0M 1,9G 1% /run/shm\nnone tmpfs 100M 44K 100M 1% /run/user\n/dev/sda1 vfat 511M 3,4M 508M 1% /boot/efi\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda2 29M 187K 29M1% /\nnone 480K 2 480K1% /sys/fs/cgroup\nudev 477K 502 477K1% /dev\ntmpfs 480K 490 479K1% /run\nnone 480K 3 480K1% /run/lock\nnone 480K12 480K1% /run/shm\nnone 480K27 480K1% /run/user\n/dev/sda1 0 0 0 - /boot/efi\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2014-04-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1311195/+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 1853784] Re: Format button has no effect when I right click a USB and select Format
Does it work better under Xorg? -- 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/1853784 Title: Format button has no effect when I right click a USB and select Format Status in nautilus package in Ubuntu: Incomplete Bug description: Whenever I boot up ubuntu and attempt to format a plugged-in or mounted USB, the Format button has no effect when clicked on; not even an error message. If there is an error, Ubuntu should let me know or not allow me to format by disabling to format option. Steps to Reproduce: 1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this will be the USB to attempt to format) 2. Log in and open Files 3. Right-click the USB and select "Format" Expected Results: Either the Format menu appears, an error message appears if I am unable to format the disk, or the Format button is disabled. Actual Results: Files allows the format button to be clicked, but nothing happens when it is clicked on. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:22:27 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853784/+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 1265898] Re: thunderbird doesn't remember maximized window state in Ubuntu Gnome
** Bug watch added: Mozilla Bugzilla #1593578 https://bugzilla.mozilla.org/show_bug.cgi?id=1593578 ** Changed in: thunderbird Importance: Medium => Unknown ** Changed in: thunderbird Status: Fix Released => Unknown ** Changed in: thunderbird Remote watch: Mozilla Bugzilla #732812 => Mozilla Bugzilla #1593578 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1265898 Title: thunderbird doesn't remember maximized window state in Ubuntu Gnome Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: Not sure if this is thunderbird or gnome-shell related issue. Steps to reproduce: 1. Run thunderbird. 2. Maximize thunderbird window. 3. Close thunderbird. 4. Run thunderbird again. 5. Notice that thunderbird window is not maximized - maximized window state was not saved during closing. Expected behaviour: In 5. thudnderbird window is open in maximized state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:24.2.0+build1-0ubuntu1 Uname: Linux 3.13.0-031300rc6-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dotnokato 1431 F pulseaudio /dev/snd/pcmC0D0p: dotnokato 1431 F...m pulseaudio BuildID: 20131206222054 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Jan 3 21:02:28 2014 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-15 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) IpRoute: default via 10.100.10.1 dev eth0 proto static 10.100.10.0/24 dev eth0 proto kernel scope link src 10.100.10.8 metric 1 10.100.10.0/24 dev wlan0 proto kernel scope link src 10.100.10.12 metric 9 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) PrefSources: prefs.js [Profile]/extensions/gnomeintegrat...@davidmartinez.net/defaults/preferences/gnomeintegration.js Profiles: Profile0 (Default) - LastVersion=24.2.0/20131206222054 (In use) RelatedPackageVersions: rhythmbox-mozilla 3.0.1-1ubuntu8 gnome-shell 3.8.4-0ubuntu6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to trusty on 2013-11-05 (59 days ago) dmi.bios.date: 05/08/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68TT2 Ver. F.07 dmi.board.name: 30B0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.15 dmi.chassis.asset.tag: CNU7110B09 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6325 (EY349EA#AKD) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1265898/+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 1852024] Re: firefox won't start
Sorry for the lack of a timely response Connor. Is the problem still present? If so, can you check whether there are crash files for firefox in /var/crash/ ? And can you run the following commands in a terminal: sudo apt install firefox-dbg # this will prompt for your admin password firefox -g then when you see the "(gdb) " prompt, type "r" and the return key. Wait for firefox to crash, and at the gdb prompt, type "t a a bt" then return key. Press return while the "type to continue" message is displayed, and then copy the contents of the terminal window and share them here. Thanks! ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1852024 Title: firefox won't start Status in firefox package in Ubuntu: Incomplete Bug description: After prompting me to restart for updates, Firefox no longer starts. If started from terminal, I am told it has segfaulted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 70.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: connor25333 F pulseaudio /dev/snd/controlC0: connor25333 F pulseaudio BuildID: 20191031085722 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 14:35:26 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-06-02 (526 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.0.0.1 dev enp5s0 proto dhcp metric 100 10.0.0.0/24 dev enp5s0 proto kernel scope link src 10.0.0.211 metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-0c16553c-f03b-44b9-b951-47a9a1180602 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh Profiles: Profile0 (Default) - LastVersion=70.0.1/20191031085722 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-0c16553c-f03b-44b9-b951-47a9a1180602 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS Gaming 7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/31/2017:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS Gaming 7 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1852024/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
I have the same issue with PL BackBeat PRO in 19.10 -- 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/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845046/+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 1853783] Re: Nautilus crashes whenever I attempt to format a USB with a partition table
*** This bug is a duplicate of bug 1853850 *** https://bugs.launchpad.net/bugs/1853850 Thanks! ** This bug has been marked a duplicate of private bug 1853850 -- 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/1853783 Title: Nautilus crashes whenever I attempt to format a USB with a partition table Status in nautilus package in Ubuntu: Invalid Bug description: Whenever I attempt to format a USB I previous used for a live install back into a regular FAT disk, nautilus reports "gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Trace/breakpoint trap (core dumped)" and then crashes. I ran "ubuntu-bug nautilus" right after I clicked the Format button, right before the crash itself. To reproduce the issue: 1. Insert an ubuntu live usb 2. Open Files 3. Right-click on the USB 4. Select Format 5. If the format menu appears, click the red format button Expected Results: Either the USB partitions are cleared and the entire disk is formatted to be FAT (preferred), or if that is not an option, Files should warn me it has a partition table and close instead of opening the Format Menu and then crashing later. Actual Results: Gnome-Disks alerts the USB cannot be formatted, and then nautilus crashes. Description: Ubuntu 19.10 Release: 19.10 nautilus nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:05:22 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/1853783/+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 1853784] Re: Format button has no effect when I right click a USB and select Format
You click on the Format button on the Nautilus sidebar. In addition, I am using Wayland. -- 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/1853784 Title: Format button has no effect when I right click a USB and select Format Status in nautilus package in Ubuntu: Incomplete Bug description: Whenever I boot up ubuntu and attempt to format a plugged-in or mounted USB, the Format button has no effect when clicked on; not even an error message. If there is an error, Ubuntu should let me know or not allow me to format by disabling to format option. Steps to Reproduce: 1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this will be the USB to attempt to format) 2. Log in and open Files 3. Right-click the USB and select "Format" Expected Results: Either the Format menu appears, an error message appears if I am unable to format the disk, or the Format button is disabled. Actual Results: Files allows the format button to be clicked, but nothing happens when it is clicked on. Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:22:27 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1853784/+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 1849693] Re: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings
Ah, good catch, thanks for following up Gert. The implementation of the profile importer assumes the profile will always be called 'Default', which is probably true in 99% of the cases, but not always. Given that there is no UI to manage profiles, nor any official instructions on how to create new ones (https://www.chromium.org/developers/creating-and-using-profiles), the assumption is probably safe enough, but let's keep the bug open to eventually address it. ** Summary changed: - [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings + [snap] Profile importer assumes the profile is called 'Default' ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low -- 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/1849693 Title: [snap] Profile importer assumes the profile is called 'Default' Status in chromium-browser package in Ubuntu: Triaged Bug description: I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser for the first time, it should have imported all former settings. But it did not. E.g. all bookmarks and saved passwords are gone. Is there a way to start the config import afterwards? The workaround mentioned under the following link did not help in my case: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAVw4UjAQEBAQIXAQOANCF46vkVo1RQnicSUFShCACpQIGAgUCzAIHAAQEBAQEBKDyAoHCwI0AwIDYAB0QhAAAa/wA0NTE3NDAxMwogICAg/QA7PR9MEQAKICAgICAg/ABFVjI0MzZXCiAgICAgALk= modes: 1920x1200 1600x1200 1680x1050 1280x1024 1280x960 1280x720 1024x768 800x600 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda5 ext4 394G 48G 327G 13% /home tmpfs tmpfs 3,9G 19M 3,9G 1% /dev/shm /dev/sda5 ext4 394G 48G 327G 13% /home DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-11-24 (334 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Gigabyte Technology Co., Ltd. Z68X-UD3H-B3 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c2336ec0-2c4e-4cf0-a475-ea8727cc3ac8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70 (edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800}) Snap.ChromiumVersion: Chromium 78.0.3904.70 snap Tags: eoan snap Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-24 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 05/02/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: Z68X-UD3H-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd05/02/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68X-UD3H-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68X-UD3H-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+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 1851942] Re: Bus error when updating from 79.0.3941.4 dev channel
Can you please run the following command in a terminal? apport-collect 1851942 Are you able to install other packages using apt, or do you get this bus error for all packages? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1851942 Title: Bus error when updating from 79.0.3941.4 dev channel Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ sudo apt install chromium-browser Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: chromium-browser-l10n chromium-codecs-ffmpeg-extra Suggested packages: webaccounts-chromium-extension unity-chromium-extension adobe-flashplugin The following packages will be upgraded: chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra 3 upgraded, 0 newly installed, 0 to remove and 662 not upgraded. Need to get 0 B/69.1 MB of archives. After this operation, 1388 kB of additional disk space will be used. Do you want to continue? [Y/n] Bus error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851942/+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 1853783] Re: Nautilus crashes whenever I attempt to format a USB with a partition table
I did. The new ID is 1853850 -- 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/1853783 Title: Nautilus crashes whenever I attempt to format a USB with a partition table Status in nautilus package in Ubuntu: Invalid Bug description: Whenever I attempt to format a USB I previous used for a live install back into a regular FAT disk, nautilus reports "gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Trace/breakpoint trap (core dumped)" and then crashes. I ran "ubuntu-bug nautilus" right after I clicked the Format button, right before the crash itself. To reproduce the issue: 1. Insert an ubuntu live usb 2. Open Files 3. Right-click on the USB 4. Select Format 5. If the format menu appears, click the red format button Expected Results: Either the USB partitions are cleared and the entire disk is formatted to be FAT (preferred), or if that is not an option, Files should warn me it has a partition table and close instead of opening the Format Menu and then crashing later. Actual Results: Gnome-Disks alerts the USB cannot be formatted, and then nautilus crashes. Description: Ubuntu 19.10 Release: 19.10 nautilus nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 24 17:05:22 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-11-20 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/1853783/+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 1813441] Re: Can no longer drag and drop files between desktop and applications
Being able to move Applications from the Menu to the desktop or move documents from the file manager to the desktop is a function that is required by many users, it is a feature that any OS and Linux Desktop has, for years that I use my PC for the first time. it's such a limit, and only GNOME-Shell has it. Is there anyone working on it or is there a plan to get it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1851698] Re: firefox crash when opened
*** This bug is a duplicate of bug 1838129 *** https://bugs.launchpad.net/bugs/1838129 This looks very similar to bug #1838129. Marking as duplicate. ** This bug has been marked a duplicate of bug 1838129 Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap -- 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/1851698 Title: firefox crash when opened Status in firefox package in Ubuntu: Incomplete Bug description: i was using "mailspring", and confirming a subscription to tfir by clicking the confirm link in the email they sent. upon clicking the confirm link, firefox opened. then after clicking the "verify humanity" button and hitting confirm (on the page now open in firefox), that is when the crash happened. I then ran "sudo ubuntu-bug firefox" i i can provide any more information, please let me know. dps ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 70.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BuildID: 20191021054351 Date: Thu Nov 7 13:22:45 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-10-23 (15 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20191021054351 SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BuildID: 20191031085722 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-10-23 (16 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NonfreeKernelModules: nvidia_modeset nvidia wl Package: firefox 70.0.1+build1-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031085722 (In use) Tags: bionic Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851698/+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 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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 1851885] Re: [snap] Icons missing after automatic snap refresh
*** This bug is a duplicate of bug 1616650 *** https://bugs.launchpad.net/bugs/1616650 Thanks for the report Alberto. This is a symptom of a known problem, namely that snaps shouldn't auto-refresh if there's one of the apps currently running. This is being addressed by https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736. Until this is live for everyone, I'd suggest running: snap set core experimental.refresh-app-awareness=true ** This bug has been marked a duplicate of bug 1616650 snap refresh while command is running may cause issues -- 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/1851885 Title: [snap] Icons missing after automatic snap refresh Status in chromium-browser package in Ubuntu: New Bug description: I had my browser running for a long time, noticed that when saving a page or downloading a file, icons in the save dialog are missing (see attached screenshot). Checking "snap info chromium", it seems the snap has been recently refreshed, so I still had the older version of the app running. Restarting the browser fixed it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851885/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
And from duplicate bug #1853835, the KeePassXC-Browser extension (https://chrome.google.com/webstore/detail/keepassxc- browser/oboonakemofpalcgghocfoadofidjkkk) doesn't work for the same reason: https://github.com/keepassxreboot/keepassxc-browser/issues/405. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
It's been reported that the GooPG extension doesn't work because it uses native messaging (https://discourse.ubuntu.com/t/call-for-testing- chromium-browser-deb-to-snap-transition/11179/207). ** Bug watch added: github.com/keepassxreboot/keepassxc-browser/issues #405 https://github.com/keepassxreboot/keepassxc-browser/issues/405 -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1853835] Re: [snap] keepassxc browser integration does not work with chromium installed as a snap
*** This bug is a duplicate of bug 1741074 *** https://bugs.launchpad.net/bugs/1741074 ** This bug has been marked a duplicate of bug 1741074 [snap] chrome-gnome-shell extension fails to detect native host connector -- 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/1853835 Title: [snap] keepassxc browser integration does not work with chromium installed as a snap Status in chromium-browser package in Ubuntu: New Bug description: After migrating to snap version of chromium in Ubuntu 19.10, I can no longer use KeePassXC-Browser extension: https://chrome.google.com/webstore/detail/keepassxc- browser/oboonakemofpalcgghocfoadofidjkkk Problem is described here: https://github.com/keepassxreboot /keepassxc-browser/issues/405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853835/+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 1853838] Re: gnome-control-center crashes with SIGSEGV when selecting display
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/1853838 Title: gnome-control-center crashes with SIGSEGV when selecting display Status in gnome-control-center package in Ubuntu: Invalid Bug description: Ubuntu eoan gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I have a DELL XPS 13 9370 and I have it connected to two monitors through a Dell Thunderbolt Dock. Only one monitor is active. When I try to activate the other one 1. What I expected to happen I am able to select the second external monitor (or the built-in display for that matter) and change its settings. 2. What happened instead gnome-control-center disappears I have attached lshw output and the gdb backtrace and would be grateful for any help with this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+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 1853838] Re: gnome-control-center crashes with SIGSEGV when selecting display
** Attachment added: "lshw.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+attachment/5307689/+files/lshw.txt -- 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/1853838 Title: gnome-control-center crashes with SIGSEGV when selecting display Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu eoan gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I have a DELL XPS 13 9370 and I have it connected to two monitors through a Dell Thunderbolt Dock. Only one monitor is active. When I try to activate the other one 1. What I expected to happen I am able to select the second external monitor (or the built-in display for that matter) and change its settings. 2. What happened instead gnome-control-center disappears I have attached lshw output and the gdb backtrace and would be grateful for any help with this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+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 1853838] [NEW] gnome-control-center crashes with SIGSEGV when selecting display
Public bug reported: Ubuntu eoan gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I have a DELL XPS 13 9370 and I have it connected to two monitors through a Dell Thunderbolt Dock. Only one monitor is active. When I try to activate the other one 1. What I expected to happen I am able to select the second external monitor (or the built-in display for that matter) and change its settings. 2. What happened instead gnome-control-center disappears I have attached lshw output and the gdb backtrace and would be grateful for any help with this. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gdb backtrace" https://bugs.launchpad.net/bugs/1853838/+attachment/5307688/+files/gnome-control-center_backtrace.txt -- 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/1853838 Title: gnome-control-center crashes with SIGSEGV when selecting display Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu eoan gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I have a DELL XPS 13 9370 and I have it connected to two monitors through a Dell Thunderbolt Dock. Only one monitor is active. When I try to activate the other one 1. What I expected to happen I am able to select the second external monitor (or the built-in display for that matter) and change its settings. 2. What happened instead gnome-control-center disappears I have attached lshw output and the gdb backtrace and would be grateful for any help with this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1853838/+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 1853837] Re: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hp
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1853837 Title: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 Status in hplip package in Ubuntu: New Bug description: Printer Not Found ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: Date: Mon Nov 25 12:50:00 2019 DuplicateSignature: package:libsane-hpaio:3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] Unpacking libsane-hpaio:i386 (3.19.6+dfsg0-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-uY0A9Z/36-libsane-hpaio_3.19.6+dfsg0-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2019-10-29 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for DeskJet-3630-series: hp:/usb/DeskJet_3630_series?serial=CN73J4N1DQ067P device for HP_DeskJet_3630_series_ADB89F_: implicitclass://HP_DeskJet_3630_series_ADB89F_/ MachineType: Acer Aspire XC-885 Papersize: a4 PpdFiles: DeskJet-3630-series: HP Deskjet 3630 Series, hpcups 3.19.6 HP_DeskJet_3630_series_ADB89F_: DeskJet 3630 series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=b52db822-2ce2-4628-8952-db3d3e0f8dcb ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: hplip Title: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-B3 dmi.board.name: Aspire XC-885(DCH) dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-B3:bd01/16/2019:svnAcer:pnAspireXC-885:pvr:rvnAcer:rnAspireXC-885(DCH):rvrV1.1:cvnAcer:ct3:cvr: dmi.product.family: Aspire X dmi.product.name: Aspire XC-885 dmi.product.sku: dmi.sys.vendor: Acer mtime.conffile..etc.hp.hplip.conf: 2019-11-11T11:22:18.102400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1853837/+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 1853837] [NEW] package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/
Public bug reported: Printer Not Found ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: Date: Mon Nov 25 12:50:00 2019 DuplicateSignature: package:libsane-hpaio:3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] Unpacking libsane-hpaio:i386 (3.19.6+dfsg0-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-uY0A9Z/36-libsane-hpaio_3.19.6+dfsg0-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2019-10-29 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for DeskJet-3630-series: hp:/usb/DeskJet_3630_series?serial=CN73J4N1DQ067P device for HP_DeskJet_3630_series_ADB89F_: implicitclass://HP_DeskJet_3630_series_ADB89F_/ MachineType: Acer Aspire XC-885 Papersize: a4 PpdFiles: DeskJet-3630-series: HP Deskjet 3630 Series, hpcups 3.19.6 HP_DeskJet_3630_series_ADB89F_: DeskJet 3630 series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=b52db822-2ce2-4628-8952-db3d3e0f8dcb ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: hplip Title: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-B3 dmi.board.name: Aspire XC-885(DCH) dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-B3:bd01/16/2019:svnAcer:pnAspireXC-885:pvr:rvnAcer:rnAspireXC-885(DCH):rvrV1.1:cvnAcer:ct3:cvr: dmi.product.family: Aspire X dmi.product.name: Aspire XC-885 dmi.product.sku: dmi.sys.vendor: Acer mtime.conffile..etc.hp.hplip.conf: 2019-11-11T11:22:18.102400 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1853837 Title: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 Status in hplip package in Ubuntu: New Bug description: Printer Not Found ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: Date: Mon Nov 25 12:50:00 2019 DuplicateSignature: package:libsane-hpaio:3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] Unpacking libsane-hpaio:i386 (3.19.6+dfsg0-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-uY0A9Z/36-libsane-hpaio_3.19.6+dfsg0-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2019-10-29 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for DeskJet-3630-series: hp:/usb/DeskJet_3630_series?serial=CN73J4N1DQ067P device for HP_DeskJet_3630_series_ADB89F_: implicitclass://HP_DeskJet_3630_series_ADB89F_/ MachineType: Acer Aspire XC-885 Papersize: a4 PpdFiles: DeskJet-3630-series: HP Deskjet 3630 Series, hpcups 3.19.6 HP_DeskJet_3630_series_ADB89F_: DeskJet 3630 series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=b52db822-2ce2-4628-8952-db3d3e0f8dcb ro quiet splash
[Desktop-packages] [Bug 1853835] [NEW] [snap] keepassxc browser integration does not work with chromium installed as a snap
Public bug reported: After migrating to snap version of chromium in Ubuntu 19.10, I can no longer use KeePassXC-Browser extension: https://chrome.google.com/webstore/detail/keepassxc- browser/oboonakemofpalcgghocfoadofidjkkk Problem is described here: https://github.com/keepassxreboot/keepassxc- browser/issues/405 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [snap] keepassxc browser integration does not with chromium installed as a snap + [snap] keepassxc browser integration does not work with chromium installed as a 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/1853835 Title: [snap] keepassxc browser integration does not work with chromium installed as a snap Status in chromium-browser package in Ubuntu: New Bug description: After migrating to snap version of chromium in Ubuntu 19.10, I can no longer use KeePassXC-Browser extension: https://chrome.google.com/webstore/detail/keepassxc- browser/oboonakemofpalcgghocfoadofidjkkk Problem is described here: https://github.com/keepassxreboot /keepassxc-browser/issues/405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853835/+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 1853420] Re: [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium
English (US) to Russian: en -> ru. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- 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/1853420 Title: [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium Status in chromium-browser package in Ubuntu: New Bug description: Unable to switch an input method from English in chromium by changing it via ibus. ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan ➜ ~ snap list chromium Name Version Rev Tracking Publisher Notes chromium 79.0.3945.29 939 beta canonical✓ - # when switching the input method switching languages journalctl -f ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). ноя 21 10:37:15 blade gnome-shell[7048]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed # when chromium is launched: journalctl -f ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade audit[2323]: USER_AVC pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade kernel: audit: type=1107 audit(1574321861.798:169): pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade chromium_chromium.desktop[7048]: [13821:13821:1121/103741.914544:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. ноя 21 10:37:41 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:170): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:171): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered ноя
[Desktop-packages] [Bug 1853015] Re: nvidia-340 fails to build against linux 5.3.0-23-generic
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.107-0ubuntu0.18.04.4 --- nvidia-graphics-drivers-340 (340.107-0ubuntu0.18.04.4) bionic; urgency=medium * debian/templates/dkms_nvidia.conf.in: debian/patches/buildfix_kernel_5.3.patch: - Backport kernel compatibility fixes (LP: #1853015). -- Alberto Milone Mon, 18 Nov 2019 16:11:16 +0100 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1853015 Title: nvidia-340 fails to build against linux 5.3.0-23-generic Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Bug description: nvidia-340 fails to build against linux 5.3.0-23-generic. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.4). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1853015/+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 1853015] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-340 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853015 Title: nvidia-340 fails to build against linux 5.3.0-23-generic Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Bug description: nvidia-340 fails to build against linux 5.3.0-23-generic. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.4). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1853015/+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 1853828] [NEW] [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all
Public bug reported: As soon as I've booted my ubuntu 19.10, I've plugged my headphones and got some clicking sound, but then there was no sound at all afterwards. The device shows on Settings > Output and it's detected by alsamixer also. The headphone works normally on my phone. This is the first time I've booted ubuntu since I've updated it (not considering when you have to do so for the installing process). Sound worked normally back then. Only sound I hear is the clicking sound whenever I plug it in and off. Headphone is at maximum gain on alsamixer. HW info shows at title. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tadeu 1556 F pulseaudio tadeu 5159 F alsamixer /dev/snd/pcmC0D0p: tadeu 1556 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 07:51:05 2019 InstallationDate: Installed on 2019-03-27 (242 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tadeu 1556 F pulseaudio tadeu 5159 F alsamixer /dev/snd/pcmC0D0p: tadeu 1556 F...m pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to eoan on 2019-11-22 (3 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.2 dmi.board.name: 0JP3NX dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.2:bd08/09/2018:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0JP3NX:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.product.sku: 07A3 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1853828 Title: [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: As soon as I've booted my ubuntu 19.10, I've plugged my headphones and got some clicking sound, but then there was no sound at all afterwards. The device shows on Settings > Output and it's detected by alsamixer also. The headphone works normally on my phone. This is the first time I've booted ubuntu since I've updated it (not considering when you have to do so for the installing process). Sound worked normally back then. Only sound I hear is the clicking sound whenever I plug it in and off. Headphone is at maximum gain on alsamixer. HW info shows at title. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tadeu 1556 F pulseaudio tadeu 5159 F alsamixer /dev/snd/pcmC0D0p: tadeu 1556 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 07:51:05 2019 InstallationDate: Installed on 2019-03-27 (242 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tadeu 1556 F pulseaudio tadeu 5159 F alsamixer /dev/snd/pcmC0D0p: tadeu 1556 F...m pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to eoan on 2019-11-22 (3 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.2 dmi.board.name: 0JP3NX dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.2:bd08/09/2018:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0JP3NX:rvrA01:cvnDellInc
[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google
** Description changed: + [Impact] + + A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. + This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. + + + [Test Case] + + In a clean environment, launch thunderbird and add an existing gmail account. + Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. + + [Regression Potential] + + Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). + The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. + + + [Original Bug Description] + When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO ** Summary changed: - Authentication constantly re-requested for Google + [SRU] Authentication constantly re-requested for Google ** Changed in: thunderbird (Ubuntu Disco) Status: Fix Committed => In Progress ** Changed in: thunderbird (Ubuntu Xenial) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubu
[Desktop-packages] [Bug 1853273] Re: --force-dark-mode flag in init file does not get recognized
Thanks for the clarification. I'm not seeing --force-dark-mode work on the google-chrome deb either. So it doesn't seem to be a snap-specific problem. Has this ever worked on linux? When searching for "--force- dark-mode" I'm seeing lots of references to the feature on windows/mac, not linux. -- 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/1853273 Title: --force-dark-mode flag in init file does not get recognized Status in chromium-browser package in Ubuntu: Incomplete Bug description: When creating a init file at ~/.chromium-browser.init chromium is supposed to read flags from there. However these do not work correctly. What I expected to happen: Starting chromium with the --force-dark-mode flag in the init file should make it use a dark UI (as long as the GTK theme option in the settings is not used) What happened instead: Starting chromium with above configuration correctly echoes CHROMIUM_FLAGS="--force-dark-mode" to the terminal and it also appears under chrome://version but a normal non-dark UI is used. What does work: Starting chromium with the above flag as an argument from the terminal makes it use a dark UI (apparently not for everyone https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/comments/5) What also does not work: This may affect all flags - so far I have tested the above and "--enable-features=WebUIDarkMode" Version: chromium version: 78.0.3904.97 rev: 937 tracking: stable --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAw5DgFAAAaAQSVIhN46qHFlFlXjycgUFQBAQEBAQEBAQEBAQEBAQEBLjaAoHA4H0AwIDUAWMIQAAAatiyA9HA4FkAwIDUAWMIQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE1NldGNi1TUEs0AJw= modes: 1920x1080 1920x1080 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/ubuntu--vg-root ext4 233G 188G 34G 85% / tmpfs tmpfs 3,9G 99M 3,8G 3% /dev/shm /dev/mapper/ubuntu--vg-root ext4 233G 188G 34G 85% / DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-04-30 (204 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 003: ID 04f2:b5c0 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20H5006VGE Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 [modified: usr/share/applications/chromium-browser.desktop] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.97 (021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}) Snap.ChromiumVersion: CHROMIUM_FLAGS="--force-dark-mode --enable-features=WebUIDarkMode" Chromium 78.0.3904.97 snap Tags: wayland-session eoan snap Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 10/30/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0DET88W (1.88 ) dmi.board.asset.tag: Not Available dmi.board.name: 20H5006VGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0DET88W(1.88):bd10/30/2017:svnLENOVO:pn20H5006VGE:pvrThinkPadE570:rvnLENOVO:rn20H5006VGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E570 dmi.product.name: 20H5006VGE dmi.product.sku: LENOVO_MT_20H5_BU_Think_FM_ThinkPad E570 dmi.product.version: ThinkPad E570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions -- Mailing list: https://launc
[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
** Changed in: glib2.0 (Ubuntu Focal) 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/1844853 Title: IBus no longer works in Qt applications after upgrade Status in GLib: Fix Released Status in ibus: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Fix Committed Status in glib2.0 source package in Bionic: Fix Committed Status in glib2.0 source package in Disco: Fix Committed Status in glib2.0 source package in Eoan: Fix Committed Status in glib2.0 source package in Focal: Fix Released Status in ibus source package in Focal: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [Impact] IBus was broken for Qt applications as a regression due to the fix of CVE-2019-14822. As a result the IBus patch was disabled temporarily, which fixed IBus from a usability POV. The real fix has been made in glib2.0, and the updates in -proposed will allow the IBus patch to be re-enabled. [Test Case] * On a standard Ubuntu {eoan,disco,bionic,xenial} installation - Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed - Upgrade the ibus packages from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa - Install some IBus input method, e.g. ibus-libpinyin - Install some Qt application, e.g. Kate * Relogin (maybe reboot) * Add the input method to the input sources * Open the Qt app and try to input something using the IBus IM => Find that the transliteration works as expected [Regression Potential] The applicable patches origin from glib upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 Consequently the changes have been reviewed by the glib maintainer, but also tested by the IBus maintainer, by me (gunnarhj), and - of course - the author Simon McVittie. The changes have been in Debian unstable since 2019-10-30. [Original description] Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1844853/+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 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor
I manually rebuilt and installed the 5.4.0 kernel from git and can confirm that the cursor issues are resolved. -- 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/1851340 Title: Ubuntu 19.10 upgrade results in invisible mouse cursor Status in xorg package in Ubuntu: Confirmed Bug description: Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible cursor with my Gnone desktop. I have found the same problem when upgrading 2 machines from Ubuntu 19.04 -> 19.10. Reproducing problem is easy: 1. Open Ubuntu Update Window 2. Select "Upgrade" 3. On completion of update (after reboot) cursor is no longer visible. 4. This applies to display connected to VGA port on host with USB Keyboard + Mouse While the connected display has no visible cursor and so is usable, I have always used X11VNC Server to provide network GUI access. On the remote X11VNC display I see and can use the cursor. This bug report is being sent via Remote X11VNC window, as I cannot use the main VGA display window (due to lack of visible cursor) I have done search online and thought that maybe issue was with my USB Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same result, no visible mouse cursor. I have done: "grep usb /var/log/syslog" and can see many USB events, including both Apple and Logitech mouse detection events. NOTE: Due to compatibility issue with X11VNC, I have disable Wayland on both machines by adding the following option to: /etc/gdm3/custom.conf WaylandEnable=false Regards, John Hartley. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 18:25:23 2019 DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo G200eR2 [1d49:0a01] InstallationDate: Installed on 2018-12-17 (322 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO System x3650 M5: -[8871AC1]- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5: -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/xorg/+bug/1851340/+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 1850775] Re: DNS info is not loaded by dhclient
DNS setting is correct with updated systemd package 242-7ubuntu3 from -proposed. -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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