[Desktop-packages] [Bug 1856276] [NEW] Alternating colors on odd and even rows on the Music screen.
Public bug reported: 1) Ubuntu 19.10 2) 3.4.3-2ubuntu1 3) On the music screen, odd and even rows should have different colors. Allow a user to set a color for odd rows and a color for even rows. 4) The horizontal rows are all the same color. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1856276 Title: Alternating colors on odd and even rows on the Music screen. Status in rhythmbox package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.4.3-2ubuntu1 3) On the music screen, odd and even rows should have different colors. Allow a user to set a color for odd rows and a color for even rows. 4) The horizontal rows are all the same color. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1856276/+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 1855546] Re: Desktop freezes a while than logs out
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. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. 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-shell (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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
Not quite released yet, just worked around in the xenial 71.0 update that was
just published.
The next major update has a proper fix though.
** Changed in: firefox (Ubuntu)
Status: Fix Released => 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 1855546] Re: Desktop freezes a while than logs out
Sounds like gnome-shell if frozen then get killed. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1856270] [NEW] links not responding to any mouse clicks
Public bug reported: On this specific page: https://www.paypal.com/hk/smarthelp/contact-us All the links are not responding to any clicks. But it works on Windows Chrome (auto updated to ver. 79). I've tried to use "reset settings" in chrome://settings/reset to disable all extensions, but still the same. And enable logging with log-level and enable-logging shows nothing special. I also tested on another 18.04 desktop running on physical hardware. Results also the same. So I think it is not virtualbox problem. Would be glad if any knowledgeable devs knows what's wrong or is it a bug. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 78.0.3904.108-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: MATE DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBYWAAAgAfkAwEAAQOAAAB47u6Ro1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBOy2ABnDkBjACAgIC/QAAyADIZAAKICAgICAg/ABWQk9YIG1vbml0b3IKEAAKICAgICAgICAgICAgAHc= modes: 1920x996 2560x1600 2560x1600 1920x1440 1856x1392 1792x1344 2048x1152 1920x1200 1920x1200 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050 1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768 1280x800 1280x800 1280x768 1280x768 1280x720 1024x768 800x600 800x600 848x480 640x480 Date: Fri Dec 13 11:59:35 2019 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2019-07-04 (162 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: Load-Avg-1min: 0.67 Load-Processes-Running-Percent: 0.3% Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=c25e5973-ac55-421b-9f3e-40e376afd3aa ro quiet splash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1856270 Title: links not responding to any mouse clicks Status in chromium-browser package in Ubuntu: New Bug description: On this specific page: https://www.paypal.com/hk/smarthelp/contact-us All the links are not responding to any clicks. But it works on Windows Chrome (auto updated to ver. 79). I've tried to use "reset settings" in chrome://settings/reset to disable all extensions, but still the same. And enable logging with log-level and enable-logging shows nothing special. I also tested on another 18.04 desktop running on physical hardware. Results also the same. So I think it is not virtualbox problem. Would be glad if any knowledgeable devs knows what's wrong or is it a bug. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 78.0.3904.108-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: MATE DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBYWAAAgAfkAwEAAQOAAAB47u6Ro1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBOy2ABnDkBjACAgIC/QAAyADIZAAKICAgICAg/ABWQk9YIG1vbml0b3IKEAAKICAgICAgICAgICAgAHc= modes: 1920x996 2560x1600 2560x1600 1920x1440 1856x1392 1792x1344 2048x1152 1920x1200 1920x1200 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050 1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768 1280x800 1280x800 1280x768 1280x768 1280x720 1024x768 800x600 800x600 848x480 640x480 Date: Fri Dec 13 11:59:35 2019 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env:
[Desktop-packages] [Bug 1856196] Re: Lower the snapd recommends to a suggests
This bug was fixed in the package snapd-glib - 1.54-0ubuntu2 --- snapd-glib (1.54-0ubuntu2) focal; urgency=medium * debian/control: - Change snapd recommends to suggests (LP: #1856196) -- Robert Ancell Fri, 13 Dec 2019 13:26:36 +1300 ** Changed in: snapd-glib (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1856196 Title: Lower the snapd recommends to a suggests Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Disco: Fix Committed Status in snapd-glib source package in Eoan: Fix Committed Status in snapd-glib source package in Focal: Fix Released Bug description: * Impact libsnapd-glib is a small library used to talk to snapd. It's currently used by gnome-software but has been added to pulseaudio in bug #1781428. It currently recommends snapd but the library works fine without it and there is no reason to pull snapd from library clients. * Test case $ sudo apt install libsnapd-glib1 -> snapd shouldn't be pulled in * Regression potential That's only a depends change, snapd isn't going to be pulled in when installing the library anymore but that's wanted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+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 1856179] Re: WINE .desktop files are not grouped into a folder on the app screen.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2021 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2021 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2021 Importance: Unknown Status: Unknown -- 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/1856179 Title: WINE .desktop files are not grouped into a folder on the app screen. Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop app icons should be automatically grouped into a folder on the app screen. I am not able to manually group them. I can group other app icons. 4) WINE. desktop apps were NOT grouped into a folder on the app screen. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856179/+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 1855711] Re: Add arrow key navigation to top bar/Dock/desktop.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Confirmed -- 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/1855711 Title: Add arrow key navigation to top bar/Dock/desktop. Status in Ubuntu UX: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: Pressing tab does not allow the user to select UI elements. If tab is pressed "Activities" should be selected. Left or right arrow to select items on Activities bar. If tab is pressed again, select top icon on Dock. Press down arrow to navigate down the dock. Press enter to start app. If tab is pressed instead of enter, Desktop icons should be selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1855711/+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 1855647] Re: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc?
If a DVD is loaded, a disc with a DVD tag is displayed on the dock. Why not display a disc with a ISO tag if an ISO is loaded.? -- 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/1855647 Title: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc? Status in glib2.0 package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Dock 3) When an ISO image is loaded, a disc with ISO tag would be displayed on the dock. 4) A disc drive was displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1855647/+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 1856014] Re: Extension enable/disable slider switch missing
Reported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856014 Title: Extension enable/disable slider switch missing Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If I remember correctly, there was a slider switch in the top right corner of the extension settings window. 4) Extensions are not appearing on the top bar. Extensions appeared before and now they do not appear. I tried removing and reinstalling the extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856014/+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 1856179] Re: WINE .desktop files are not grouped into a folder on the app screen.
Reported. -- 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/1856179 Title: WINE .desktop files are not grouped into a folder on the app screen. Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop app icons should be automatically grouped into a folder on the app screen. I am not able to manually group them. I can group other app icons. 4) WINE. desktop apps were NOT grouped into a folder on the app screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856179/+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 1854379] Re: Snap packages sources are not stated on listings
Fixed upstream in https://gitlab.gnome.org/GNOME/gnome- software/merge_requests/384 ** Changed in: gnome-software (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1854379 Title: Snap packages sources are not stated on listings Status in gnome-software package in Ubuntu: Fix Committed Bug description: As shown in the attaching (flathub_source_good.png), flathub packages shown in listings with the: 'source: dl.flathub.org' shown directily without having to click into the application package. This is not the case for Snap packages. You have to click into the listing to find out if it is a SNAP package or not. This is confusing these days as you can have the same package from multiple sources (ubuntu source, SNAP, flathub...) SNAP sources should be shown the same way. A user would want to know the source, especially if it is a SNAP/flatpak because they would associate it with more frequent updates and the other benefits of the packaging. Ideally you could also filter based on the source as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1854379/+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 1856196] Re: Lower the snapd recommends to a suggests
** Also affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: snapd-glib (Ubuntu Bionic) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Also affects: snapd-glib (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu Disco) Status: New => Fix Committed ** Changed in: snapd-glib (Ubuntu Disco) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Disco) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Xenial) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Xenial) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1856196 Title: Lower the snapd recommends to a suggests Status in snapd-glib package in Ubuntu: Fix Committed Status in snapd-glib source package in Xenial: Fix Committed Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Disco: Fix Committed Status in snapd-glib source package in Eoan: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Bug description: * Impact libsnapd-glib is a small library used to talk to snapd. It's currently used by gnome-software but has been added to pulseaudio in bug #1781428. It currently recommends snapd but the library works fine without it and there is no reason to pull snapd from library clients. * Test case $ sudo apt install libsnapd-glib1 -> snapd shouldn't be pulled in * Regression potential That's only a depends change, snapd isn't going to be pulled in when installing the library anymore but that's wanted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+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 1856196] Re: Lower the snapd recommends to a suggests
** Also affects: snapd-glib (Ubuntu Focal) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Also affects: snapd-glib (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: snapd-glib (Ubuntu Eoan) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu Eoan) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: snapd-glib (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1856196 Title: Lower the snapd recommends to a suggests Status in snapd-glib package in Ubuntu: Fix Committed Status in snapd-glib source package in Xenial: New Status in snapd-glib source package in Bionic: Fix Committed Status in snapd-glib source package in Eoan: Fix Committed Status in snapd-glib source package in Focal: Fix Committed Bug description: * Impact libsnapd-glib is a small library used to talk to snapd. It's currently used by gnome-software but has been added to pulseaudio in bug #1781428. It currently recommends snapd but the library works fine without it and there is no reason to pull snapd from library clients. * Test case $ sudo apt install libsnapd-glib1 -> snapd shouldn't be pulled in * Regression potential That's only a depends change, snapd isn't going to be pulled in when installing the library anymore but that's wanted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
I can't seem to reproduce the problem just yet (using 20.04 with Intel graphics). My first two ideas are: * Maybe this is related to Terminal's broken transparency (bug 561370) * Maybe it's Nvidia-specific. That log message "Not using GLX TFP" is from the mutter compositor code. It means the driver has decided to not use GLX_EXT_texture_from_pixmap which may or may not be related to this bug. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
Also forgot to mention that I expect this is probably related to fullscreen bypass. Does it only occur in Xorg sessions? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
Oh, you can't test Wayland easily when using the Nvidia driver. I recommend not so don't worry about that. ** Tags added: nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856179] Re: WINE .desktop files are not grouped into a folder on the app screen.
Can you please report this to the upstream developers? https://gitlab.gnome.org/GNOME/gnome-shell/issues ** Tags added: 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/1856179 Title: WINE .desktop files are not grouped into a folder on the app screen. Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop app icons should be automatically grouped into a folder on the app screen. I am not able to manually group them. I can group other app icons. 4) WINE. desktop apps were NOT grouped into a folder on the app screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856179/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
The upstream bug for X11 here is https://gitlab.gnome.org/GNOME/mutter/issues/919 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
mvo and others, please test the above fix on Ubuntu 20.04 if it is convenient. When and if confirmed to be working we will propose the same to 19.10. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1856196] Re: Lower the snapd recommends to a suggests
This needs to be SRUd back to older releases, right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1856196 Title: Lower the snapd recommends to a suggests Status in snapd-glib package in Ubuntu: New Bug description: * Impact libsnapd-glib is a small library used to talk to snapd. It's currently used by gnome-software but has been added to pulseaudio in bug #1781428. It currently recommends snapd but the library works fine without it and there is no reason to pull snapd from library clients. * Test case $ sudo apt install libsnapd-glib1 -> snapd shouldn't be pulled in * Regression potential That's only a depends change, snapd isn't going to be pulled in when installing the library anymore but that's wanted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This bug was fixed in the package pulseaudio - 1:13.0-1ubuntu5 --- pulseaudio (1:13.0-1ubuntu5) focal; urgency=medium * Add 0031-lp1847570-Revert-switch-on-connect-Do-not-ignore-HDMI-sinks.patch to revert to PulseAudio v12 behaviour and ignore monitors with HDMI ports. At least until a proper solution arrives in PulseAudio v14. (LP: #1847570) -- Daniel van Vugt Wed, 11 Dec 2019 16:34:39 +0800 ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
> For openvpn + systemd-resolve:
>
> With "up / down" openvpn config file commands you can wrap "systemd-
> resolve --set-dns=XXX" and update the given DNS servers.
There's a package for that: openvpn-systemd-resolved
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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
This bug was fixed in the package firefox - 71.0+build5-0ubuntu0.16.04.1
---
firefox (71.0+build5-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream stable release (71.0+build5)
* Update test expectation
- debian/tests/html5test
* Fix build failures on armhf and s390x with clang 8
- debian/patches/armhf-clang-no-integrated-as-for-neon.patch
- debian/patches/s390x-fix-hidden-symbol.patch
* Temporarily hardcode MOZ_BUILD_DATE to ensure the build ID is strictly less
than the one for the bionic build already in bionic-updates (LP: #1851936)
-- Olivier Tilloy Wed, 11 Dec 2019
21:51:56 +0100
** Changed in: firefox (Ubuntu)
Status: Fix Committed => Fix Released
--
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 Released
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 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
Whenever I have a fullscreen app focused on, and then hit the super key, I see this JS ERROR in the journalctl (see attachment). Note that if the app is not fullscreen, there is no flashing and no journalctl error log. ** Attachment added: "journalctl.out" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+attachment/5312068/+files/journalctl.out -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash Status in gnome-shell package in Ubuntu: New Bug description: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856251] [NEW] Going from apps overview screen to fullscreen'd app causes flash
Public bug reported: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. - Whenever I have a fullscreen app focused on, and then hit the super key, - I see this JS ERROR in the journalctl: - - Dec 12 16:15:14 bmo gnome-shell[3482]: JS ERROR: TypeError: this._workspacesViews[i] is undefined - _updateWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:774:13 - setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:764:9 - setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/viewSelector.js:293:9 - _updateWorkspacesGeometry@resource:///org/gnome/shell/ui/overviewControls.js:471:9 - vfunc_allocate@resource:///org/gnome/shell/ui/overviewControls.js:415:9 - _computeWindowCenter@resource:///org/gnome/shell/ui/workspace.js:309:19 - _init@resource:///org/gnome/shell/ui/workspace.js:160:9 - _addWindowClone@resource:///org/gnome/shell/ui/workspace.js:1845:21 - Workspace<@resource:///org/gnome/shell/ui/workspace.js:1166:17 - _updateWorkspaces@resource:///org/gnome/shell/ui/workspacesView.js:265:29 - WorkspacesView<@resource:///org/gnome/shell/ui/workspacesView.js:100:9 - _updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:678:24 - show@resource:///org/gnome/shell/ui/workspacesView.js:608:9 - show@resource:///org/gnome/shell/ui/viewSelector.js:268:9 - _animateVisible@resource:///org/gnome/shell/ui/overview.js:532:9 - show@resource:///org/gnome/shell/ui/overview.js:518:9 - toggle@resource:///org/gnome/shell/ui/overview.js:639:13 - _initializeUI/<@resource:///org/gnome/shell/ui/main.js:211:13 - Dec 12 16:15:14 bmo gnome-shell[3482]: NOTE: Not using GLX TFP! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) -- You received this bug notification
[Desktop-packages] [Bug 1855489] Re: Chromium auto-restart feature breaks many features
*** This bug is a duplicate of bug 1616650 *** https://bugs.launchpad.net/bugs/1616650 Okay, another updated happened today (version 79.0.3945.79) and I can confirm that it creates the issue where I lose the dot under the Gnome icon. So bug $1616650 definitely looks like the solution to this problem. Thank you. -- 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/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: Incomplete Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I insist that changing the Download folder had no effects. That's not the issue in this case. Also, I could download files and they would go in my ~/Downloads folder as expected. No problem on that one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855489/+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 1855894] Re: Ukrainian translation problem for "Unlock keyring" dialog
Thanks for reporting. I was unable to find the exact string since I don't speak the language, but I assume it would be one of these translations https://translations.launchpad.net/ubuntu/eoan/+source/seahorse/+pots/seahorse/uk/+translate?batch=10=all=unlock. ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1855894 Title: Ukrainian translation problem for "Unlock keyring" dialog Status in Ubuntu Translations: New Status in seahorse package in Ubuntu: New Bug description: It's the wrong character for "Unlock keyring" dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1855894/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
At the time I filed the bug, I did not notice an updated build in focal - it was still the same one as in eoan, but perhaps I was just not paying enough attention. I will try it out. That version is likely to be new enough to work, although I know there was an update to libusbmuxd with a version and soname bump in november (although the functional changes are already present in that git revision) and that would be worth having to avoid long term confusion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
I'll try out the focal builds when I get a chance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I think that the upstream bug https://gitlab.gnome.org/GNOME/mutter/issues/878 may not be the same issue. This bug has "X11" in the title, and so it really refers to behavior under X11. On Ubuntu 19.10, if I run an X11 session then copying/pasting fails very often, especially in LibreOffice. For this reason I switched to Wayland several weeks ago. Under Wayland, copying/pasting still fails occasionally, but far less often. I saw copy/paste failures dozens of times per day under X11, and now they happen maybe once or twice per day in Wayland (with intensive use of LibreOffice in both cases). In a comment in the mutter bug linked above, Carlos Garnacho wrote This is wayland specific. So it is unclear to me that the patches linked there (which are to both GTK and mutter) will fix the problem in X11. Has anyone tried to reproduce this copy/paste problem after applying these patches under X11? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Hey all, got it working on my Asus E200HA @ Xubuntu 19.10. As already mentioned, the installed kernel (currently 5.3.0-24) already brings the driver. What I had to do was uninstalling libasound2 (currently 1.1.9-1), as the sound card is not supported in this version. After uninstalling, I installed the latest alsa-lib [1] (1.2.1.2). Note, that the default installation of the alsa-lib takes place in "/usr/lib", but it should be placed in "/usr/lib/x86_64-linux-gnu/". This can be done by running "./configure --libdir=/usr/lib/x86_64-linux-gnu/". After installing it, I downloaded the latest alsa-ucm-config [2] (1.2.1.2). The content of the ucm2 folder must be stored in "/usr/share/alsa/ucm2/". After a reboot, the sound works :) So, installing the latest libasound2 (= alsa-lib) on the right place and placing the UCM files in the right directory did the trick for me. [1] https://github.com/alsa-project/alsa-lib [2] https://github.com/alsa-project/alsa-ucm-conf/ -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1852170] Re: [amdgpu] Severe screen corruption
*** This bug is a duplicate of bug 1848741 *** https://bugs.launchpad.net/bugs/1848741 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1852170 Title: [amdgpu] Severe screen corruption Status in xorg package in Ubuntu: Confirmed Bug description: Screen occasionally shows strange distortions and corruptions during almost any activity. Static or bars of colour appear in unusual places along the screen. Corruptions are often (though not always) removed in some sections of the screen by the appearance of other display elements (windows, tooltip, mouse-over, etc.) Description: Ubuntu 19.10 Release: 19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status 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.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 16:13:38 2019 DistUpgraded: 2019-11-07 18:03:17,611 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 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:506f] InstallationDate: Installed on 2018-09-07 (430 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KUCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro radeon.modeset=0 ivrs_ioapic[32]=00:14.0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-07 (4 days ago) dmi.bios.date: 07/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KUCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0UET47W(1.27):bd07/16/2018:svnLENOVO:pn20KUCTO1WW:pvrThinkPadE485:rvnLENOVO:rn20KUCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E485 dmi.product.name: 20KUCTO1WW dmi.product.sku: LENOVO_MT_20KU_BU_Think_FM_ThinkPad E485 dmi.product.version: ThinkPad E485 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 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 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/1852170/+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 1855172] Re: Synaptics s3203 touchpad on Dell Inspiron 15 5547 has no working after recent upgrade
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: xserver-xorg-input-synaptics (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1855172 Title: Synaptics s3203 touchpad on Dell Inspiron 15 5547 has no working after recent upgrade Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu 18.04 with the `apt upgrade` command, and the kernel upgrade to 4.15.0-72. After a reboot, the touchpad stopped working. And the external USB mouse kept working fine. Looking for this issue, I found these reports about similar problems (https://sangams.com.np/fix-ubuntu-18-4-touchpad-not-working-properly/ and https://askubuntu.com/questions/1041820/touchpad-not-working-on- ubuntu-18-04), and I checked the package `xserver-xorg-input- synaptics` wasn't installed. Then I tried to install with the command: `apt install xserver-xorg-input-synaptics`. I rebooted the computer, but the problem continues. After I ran a diagnostic test with BIOS from Dell Notebook, and on interacting with the diagnostic system, I was able to use the touchpad without problems. Then I suppose this problem is from SO kernel upgraded. = Follow some info's system: $uname -a Linux myinspiron155547 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ Dell WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855172/+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 1856145] Re: Display a message box if a user double clicks on an .exe or .msi file.
** Description changed: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 - 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed for Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" + 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed for Ubuntu. Some Windows software can function correctly on Ubuntu, if a compatibility layer called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856145 Title: Display a message box if a user double clicks on an .exe or .msi file. Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed for Ubuntu. Some Windows software can function correctly on Ubuntu, if a compatibility layer called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856145/+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 1856145] Re: Display a message box if a user double clicks on an .exe or .msi file.
** Description changed: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 - 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed to run on Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" + 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed for Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856145 Title: Display a message box if a user double clicks on an .exe or .msi file. Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed for Ubuntu. Some Windows software can function correctly on Ubuntu, if a compatibility layer called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856145/+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 1856214] [NEW] Selecting multiple documents only the first one goes to selected printer if not default printer
Public bug reported: Selecting multiple documents, then right click, select print, then, in printing dialog any printer not default. Only the first document will go to the selected printer, all others will go to the default printer. Found with: - Ubuntu 19.10, 20.04 - Windows 10 Thunderbird: - latest esr - nightly This seems to happen, because thunderbird creates one job for every document the user selected, but without keeping the selected printer. This bug may be a security problem, if the default printer is a fast one accessible by others, while the selected printer is not default, but located in a closed room for printing confidential documents. In this case the first printed document will go where it was intended, while the additionally selected documents will unintentionally go to the default printer open to the public. There are some solutions coming to mind: 1. Make all documents to print into one big document before sending them as a single job to the printer. 2. Keep the selected printer for all jobs – maybe even for jobs later on. 3. Ask which printer to use before every document the user asked to print. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.2.2+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191201113928 CurrentDesktop: XFCE Date: Thu Dec 12 18:08:57 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thunderbird (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 thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1856214 Title: Selecting multiple documents only the first one goes to selected printer if not default printer Status in thunderbird package in Ubuntu: New Bug description: Selecting multiple documents, then right click, select print, then, in printing dialog any printer not default. Only the first document will go to the selected printer, all others will go to the default printer. Found with: - Ubuntu 19.10, 20.04 - Windows 10 Thunderbird: - latest esr - nightly This seems to happen, because thunderbird creates one job for every document the user selected, but without keeping the selected printer. This bug may be a security problem, if the default printer is a fast one accessible by others, while the selected printer is not default, but located in a closed room for printing confidential documents. In this case the first printed document will go where it was intended, while the additionally selected documents will unintentionally go to the default printer open to the public. There are some solutions coming to mind: 1. Make all documents to print into one big document before sending them as a single job to the printer. 2. Keep the selected printer for all jobs – maybe even for jobs later on. 3. Ask which printer to use before every document the user asked to print. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.2.2+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191201113928 CurrentDesktop: XFCE Date: Thu Dec 12 18:08:57 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1856214/+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 1856145] Re: Display a message box if a user double clicks on an .exe or .msi file.
** Description changed: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 - 3) If a user clicks on an .exe or.msi file, display a "Windows software is not compatible with Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" + 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed to run on Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856145 Title: Display a message box if a user double clicks on an .exe or .msi file. Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If a user clicks on an .exe or.msi file, display a "Windows software is not designed to run on Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856145/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
This upstream bug looks like the same issue: https://gitlab.gnome.org/GNOME/mutter/issues/878 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 631035] Re: Adding cups networking printer which requires auth: "held for authentication"
And it is an issue with various print servers out there requiring user/password, because printing is prohibited until the user authenticates at the printer – mostly because it is thought as good practice not to have confidential print jobs laying around because these where never fetched by the user printing them …. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/631035 Title: Adding cups networking printer which requires auth: "held for authentication" Status in system-config-printer package in Ubuntu: Confirmed Bug description: I'm trying to use a cups network printer over ipp which requires authentication. I can easily add the printer (System Settings - Printer Configuration - New Printer) but as soon as I want to print something the print job get hold. The printer applet lists the job with "held for authentication". But no user/pass input form opening or available. Workaround: stop cups, edit printers.conf, hardcode user+pass in the printer-uri and start cups again... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/631035/+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 631035] Re: Adding cups networking printer which requires auth: "held for authentication"
It is still an issue with 19.10 and upcoming 20.04 .. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/631035 Title: Adding cups networking printer which requires auth: "held for authentication" Status in system-config-printer package in Ubuntu: Confirmed Bug description: I'm trying to use a cups network printer over ipp which requires authentication. I can easily add the printer (System Settings - Printer Configuration - New Printer) but as soon as I want to print something the print job get hold. The printer applet lists the job with "held for authentication". But no user/pass input form opening or available. Workaround: stop cups, edit printers.conf, hardcode user+pass in the printer-uri and start cups again... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/631035/+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 1850069] Re: No sound output on i386 starting with version 79
In my tests, I didn't have to enable any specific features, sound output worked out of the box with the stock packages, no configuration needed. -- 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/1850069 Title: No sound output on i386 starting with version 79 Status in chromium-browser package in Ubuntu: Fix Released Bug description: Steps to reproduce the problem: 1. Play sounds (video, audio, speech synthesis) 2. 3. What is the expected behavior? 1. Sound should be output to headphones or speakers What went wrong? 1. No sound is output to headphones or speakers DOMException: Could not start audio source Did this work before? Yes 79.0.3921.0 Does this work in other browsers? Yes Chrome version: 79.0.3941.4 Channel: n/a ALSA lib pcm_direct.c:1722:(snd1_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio) [32691:32691:1027/165318.863140:ERROR:alsa_util.cc(204)] PcmOpen: default,Invalid argument https://bugs.chromium.org/p/chromium/issues/detail?id=1018580 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 79.0.3941.4-0ubuntu0.18.04.1 [origin: LP-PPA-chromium-team-dev] ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CrashDB: ubuntu CurrentDesktop: XFCE DRM.card0-DP-1: 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///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg= modes: 1920x1080 Date: Sun Oct 27 17:45:32 2019 Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. Latitude E7440 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850069/+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 1850069] Re: No sound output on i386 starting with version 79
Note, see https://bugs.chromium.org/p/chromium/issues/detail?id=1032949#c7 > @guest271314: thanks for attempting to verify. The verification, however, requires --enable-features=AudioServiceSandbox; also the latest fix in #c5, which addresses only one of the issues uncovered recently, is not yet in canary. -- 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/1850069 Title: No sound output on i386 starting with version 79 Status in chromium-browser package in Ubuntu: Fix Released Bug description: Steps to reproduce the problem: 1. Play sounds (video, audio, speech synthesis) 2. 3. What is the expected behavior? 1. Sound should be output to headphones or speakers What went wrong? 1. No sound is output to headphones or speakers DOMException: Could not start audio source Did this work before? Yes 79.0.3921.0 Does this work in other browsers? Yes Chrome version: 79.0.3941.4 Channel: n/a ALSA lib pcm_direct.c:1722:(snd1_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio) [32691:32691:1027/165318.863140:ERROR:alsa_util.cc(204)] PcmOpen: default,Invalid argument https://bugs.chromium.org/p/chromium/issues/detail?id=1018580 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 79.0.3941.4-0ubuntu0.18.04.1 [origin: LP-PPA-chromium-team-dev] ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CrashDB: ubuntu CurrentDesktop: XFCE DRM.card0-DP-1: 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///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg= modes: 1920x1080 Date: Sun Oct 27 17:45:32 2019 Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. Latitude E7440 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850069/+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 1856014] Re: Extension enable/disable slider switch missing
That's probably also an upstream issue and to report to them... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856014 Title: Extension enable/disable slider switch missing Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If I remember correctly, there was a slider switch in the top right corner of the extension settings window. 4) Extensions are not appearing on the top bar. Extensions appeared before and now they do not appear. I tried removing and reinstalling the extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856014/+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 1856032] Re: DVD icon did not disappear from dash.
Confirmed from a 19.10 usb stick on a computer with a CD drive, 'gio mount -o' shows the mount are removed and nautilus correctly refresh, the launcher doesn't though ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed ** Tags added: lts-desktop-wishlist ** Tags removed: lts-desktop-wishlist ** Tags added: desktop-lts-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1856032 Title: DVD icon did not disappear from dash. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Dock 3) I placed a DVD in the optical drive. An optical disc with a DVD tag appeared on the dock. I pressed the button on the optical drive to open it. I removed the disc and pressed in the tray. The icon should have disappeared from the dock. 4) The icon did NOT disappear from the dock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1856032/+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 1855997] Re: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1855997 Title: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1 Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: - make sure Firefox is not running - export MOZ_ENABLE_WAYLAND=1 - firefox then in a new terminal - export MOZ_ENABLE_WAYLAND=1 - firefox www.google.com Expectation: - a new tab opens in the Firefox window, loading google Actual result: - firefox crashes This is a recent regression: it used to work fine in 70.0.1+build1-0ubuntu0.19.10.1, broke when I upgraded to 71.0+build5-0ubuntu0.19.10.1. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 71.0+build5-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 09:26:41 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:722 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-10-18 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/+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 1850069] Re: No sound output on i386 starting with version 79
The upstream bug was marked Fixed, and I verified that the i386 builds for 79.0.3945.79 (debs and snap) indeed work. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/1850069 Title: No sound output on i386 starting with version 79 Status in chromium-browser package in Ubuntu: Fix Released Bug description: Steps to reproduce the problem: 1. Play sounds (video, audio, speech synthesis) 2. 3. What is the expected behavior? 1. Sound should be output to headphones or speakers What went wrong? 1. No sound is output to headphones or speakers DOMException: Could not start audio source Did this work before? Yes 79.0.3921.0 Does this work in other browsers? Yes Chrome version: 79.0.3941.4 Channel: n/a ALSA lib pcm_direct.c:1722:(snd1_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio) [32691:32691:1027/165318.863140:ERROR:alsa_util.cc(204)] PcmOpen: default,Invalid argument https://bugs.chromium.org/p/chromium/issues/detail?id=1018580 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 79.0.3941.4-0ubuntu0.18.04.1 [origin: LP-PPA-chromium-team-dev] ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CrashDB: ubuntu CurrentDesktop: XFCE DRM.card0-DP-1: 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///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg= modes: 1920x1080 Date: Sun Oct 27 17:45:32 2019 Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. Latitude E7440 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850069/+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 1856204] [NEW] If a printer is set to "AuthInfoRequested negotiate" cups asks password for user negotiate
Public bug reported: If a printer is set to "AuthInfoRequested negotiate" cups will ask for password for user "negotiate" instead to exaust an error because "negotiate" isn't a keyword. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:45:11 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** 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/1856204 Title: If a printer is set to "AuthInfoRequested negotiate" cups asks password for user negotiate Status in cups package in Ubuntu: New Bug description: If a printer is set to "AuthInfoRequested negotiate" cups will ask for password for user "negotiate" instead to exaust an error because "negotiate" isn't a keyword. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:45:11 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None
[Desktop-packages] [Bug 1856201] [NEW] AuthInfoRequired set for one Printer will set it for all printers
Public bug reported: If at least one printer is set to "AuthInfoRequested negotiate" this will be taken for all printers, even if these have set "AuthInfoRequested none". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:39:56 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** 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/1856201 Title: AuthInfoRequired set for one Printer will set it for all printers Status in cups package in Ubuntu: New Bug description: If at least one printer is set to "AuthInfoRequested negotiate" this will be taken for all printers, even if these have set "AuthInfoRequested none". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:39:56 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
So for the hp-spectre-x360-convertible-15 laptop, probably the internal mic doesn't connect to the codec, it connects to the PCH directly. So setting 0x12/0x13 to internal mic doesn't work at all. Please install this testing kernel, then boot with this kernel and upload the dmesg, Let us see if the dmic connects to the PCH or not. thx. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
@Gord > There are no circumstances where it makes sense to have libsnapd-glib1 as a > dependency of > pulseaudio. Really it that it does, it"s a shared library and those are not optional under linux, you can have a read about ELF e.g here if you are intested https://lwn.net/Articles/631631/ Libraries are small and don't create real overhead, you probably have binaries pulling other libs you don't want. GTK for example does pull in libwayland and it's not optional either -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Bug #1856196 is now used to SRU the snapd-glib Recommends->Suggests change, closing the pulseaudio side since the update got reverted for now and the actual bug is not there ** No longer affects: snapd-glib (Ubuntu) -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
If you want to speak to the snapd guys and ask them to make libsnapd- glib1 a dependency of snapd, by all means do so. There are no circumstances where it makes sense to have libsnapd-glib1 as a dependency of pulseaudio. Pulseaudio and Snap are two seperate entities, and only those with snapd installed actually need snapd library support. I don't want it. I don't need it, and I certainly don't want the dependencies it drags in. And I don't want to have to make admin changes to accomodate the whims and fanciful notions of others. And that, I think, is all I wish to say on the matter. -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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
Note, there is a spread test in snapd that checks for if the mediation patches are dropped (or added). While it is fine for https://launchpad.net/bugs/1856054 to be fast tracked, this pulseaudio bug should not be marked as Fix Released before the end of year break unless you coordinate with the snapd team first so as to avoid the spread test failing when no one is around to fix it. Specifically, snapd needs: https://github.com/snapcore/snapd/pull/7885 https://github.com/snapcore/snapd/pull/7886 To be clear, the snapd deb doesn't need to be involved in any of this; it is just coordinating with upstream so the upstream CI doesn't break over the holidays. -- 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
[Desktop-packages] [Bug 1856196] [NEW] Lower the snapd recommends to a suggests
Public bug reported: * Impact libsnapd-glib is a small library used to talk to snapd. It's currently used by gnome-software but has been added to pulseaudio in bug #1781428. It currently recommends snapd but the library works fine without it and there is no reason to pull snapd from library clients. * Test case $ sudo apt install libsnapd-glib1 -> snapd shouldn't be pulled in * Regression potential That's only a depends change, snapd isn't going to be pulled in when installing the library anymore but that's wanted ** Affects: snapd-glib (Ubuntu) Importance: High Assignee: Robert Ancell (robert-ancell) Status: New ** Changed in: snapd-glib (Ubuntu) Importance: Undecided => High ** Changed in: snapd-glib (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1856196 Title: Lower the snapd recommends to a suggests Status in snapd-glib package in Ubuntu: New Bug description: * Impact libsnapd-glib is a small library used to talk to snapd. It's currently used by gnome-software but has been added to pulseaudio in bug #1781428. It currently recommends snapd but the library works fine without it and there is no reason to pull snapd from library clients. * Test case $ sudo apt install libsnapd-glib1 -> snapd shouldn't be pulled in * Regression potential That's only a depends change, snapd isn't going to be pulled in when installing the library anymore but that's wanted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+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
** Changed in: pulseaudio (Ubuntu Xenial) Status: Fix Released => Fix Committed ** Changed in: pulseaudio (Ubuntu Bionic) Status: Fix Released => Fix Committed -- 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 PlugSlot Notes audio-playback
[Desktop-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
The loop isn't within cups, but within js running within the browser. Noting this I tried to switch to an other browser to get rid of this loop. But without success: any of the tested ones leads to this loop: - Firefox (stable, esr, nightly) - Chrome (stable, beta, unstable, waterfall) - Chromium (stable, waterfall) - Vivaldi (stable, snapshot) - Opera (stable, beta, snapshot) - otter-browser - lynx -> pages unusable -- did not test further. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: Incomplete Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID
[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support
This update has been pulled from -updates by Sebastien as it was causing pulling in snapd via a recommends chain on systems that do not want to have snapd installed. A fix is in the works from what I know. Marking it as verification-failed so that it doesn't get re-released by accident. ** Tags removed: verification-done verification-done-bionic verification-done-xenial ** Tags added: verification-failed verification-failed-bionic verification-failed-xenial -- 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 Released Status in pulseaudio source package in Bionic: Fix Released 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
[Desktop-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Did you use the web interface of CUPS? Does the same problem occur when using the "lpadmin" command in a terminal? Does it also occur when using the printer part of the GNOME Control Center or system-config-printer? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: Incomplete Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize:
[Desktop-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
** Also affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-bb-incoming rls-xx-incoming ** Tags removed: rls-xx-incoming ** Tags added: rls-x-incoming -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Status in snapd-glib package in Ubuntu: New Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Same for any page with any printer. CUPS seems to run an endless loop exausting it has done ok. But nothing done at all. Just looping. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: New Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd']
[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
We first need to assert if it's working in the current version, then it would be nice to backport support to Bionic but that might be non trivial since it involves a soname change/transition -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1854363] Re: [upstream] Typo in thunderbird code prevents central configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1854363 Title: [upstream] Typo in thunderbird code prevents central configuration Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Confirmed Bug description: The latest thunderbird (1:68.2.1+build1-0ubuntu0.18.04.1) introduces a typo that destroys our autoconfiguration. Error messages: Netscape.cfg/AutoConfig failed. Please contact your system administrator. Error: getLDAPAttibutes failed: ReferenceError: processLDAPValues is not defined Netscape.cfg/AutoConfig failed. Please contact your system administrator. Error: authconfig.js failed failed: TypeError: userInfo.mail is undefined Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1592922 I have downgraded thunderbird and confirmed that this happen when upgrading to 1:68.2.1+build1 My system: Description:Ubuntu 18.04.3 LTS Release:18.04 apt policy thunderbird thunderbird: Installed: 1:52.7.0+build1-0ubuntu1 Candidate: 1:68.2.1+build1-0ubuntu0.18.04.1 Version table: 1:68.2.1+build1-0ubuntu0.18.04.1 500 500 http://ubuntu.uib.no/archive bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 1:52.7.0+build1-0ubuntu1 500 500 http://ubuntu.uib.no/archive bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1854363/+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 1856005] Re: Set "Documents" folder as default when saving a file.
*** This bug is a duplicate of bug 194904 *** https://bugs.launchpad.net/bugs/194904 Maybe there should be options in preferences: *Documents folder(default) *Last used folder *Custom folder -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1856005 Title: Set "Documents" folder as default when saving a file. Status in gedit: Unknown Status in gedit package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 3.34.0-1 3) I opened Gedit, typed some stuff and then clicked the save button. Gedit should save documents to the documents folder by default. 4) Gedit defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1856005/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Thank you for your bug report. Could you try on the current Ubuntu serie (focal), it should work there? https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/1.2.1~git20190929.60823f9-1 ** Changed in: libimobiledevice (Ubuntu) Importance: Undecided => High ** Changed in: libplist (Ubuntu) Importance: Undecided => High ** Changed in: libusbmuxd (Ubuntu) Importance: Undecided => High ** Changed in: usbmuxd (Ubuntu) Importance: Undecided => High ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04
>From https://lwn.net/Articles/714710/ "The TIMER_STATS feature, which made some timer statistics available in /proc/timer_stats, has been removed. It was seen as a security problem, since it could leak process information across namespaces; the tracing subsystem should be used to get this information instead." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1753263 Title: GNOME Power Statistics shows nothing on Ubuntu 18.04 Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: GNOME Power Statistics shows nothing on Ubuntu 18.04, just the "cannot enable timerstats" error. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Same problem here, the microphone shows as (unplugged) in the PulseAudio Volume Control. Ubuntu 18.04.3 LTS. ❯ uname -a Linux luisz-G3-3590 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ❯ arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3254 Analog [ALC3254 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 2: ALC3254 Alt Analog [ALC3254 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ** Attachment added: "unplugged built-in microphone" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5311999/+files/pulseunplugged.png -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Same for adding a new printer. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: New Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep:
[Desktop-packages] [Bug 1856189] [NEW] Trying to delete a printer will fill up the filesystem with logmessages
Public bug reported: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor:
[Desktop-packages] [Bug 1856014] Re: Extension enable/disable slider switch missing
** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856014 Title: Extension enable/disable slider switch missing Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If I remember correctly, there was a slider switch in the top right corner of the extension settings window. 4) Extensions are not appearing on the top bar. Extensions appeared before and now they do not appear. I tried removing and reinstalling the extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856014/+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 194904] Re: Text editor default save directory should be ~/Documents
** Summary changed: - Text editor default save directory + Text editor default save directory should be ~/Documents ** Bug watch added: gitlab.gnome.org/GNOME/gedit/issues #36 https://gitlab.gnome.org/GNOME/gedit/issues/36 ** Changed in: gedit Importance: Low => Unknown ** Changed in: gedit Status: Won't Fix => Unknown ** Changed in: gedit Remote watch: GNOME Bug Tracker #504067 => gitlab.gnome.org/GNOME/gedit/issues #36 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/194904 Title: Text editor default save directory should be ~/Documents Status in gedit: Unknown Status in gedit package in Ubuntu: Triaged Bug description: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" $ dpkg -l *gedit* | grep ii ii gedit 2.21.1-0ubuntu3 official text editor of the GNOME desktop environment ii gedit-common 2.21.1-0ubuntu3 official text editor of the GNOME desktop environment The default directory to save files in the text editor (gedit) is in the users home directory. i.e. /home/bob/ I propose to change it, to the "Documents" subdirectory which already exist. So it gets saved to /home/bob/Documents/ Else, why do we have "Pictures", "Videos", "Music" and "Documents" directory in our home directory, if they are not for use? To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/194904/+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 1856005] Re: Set "Documents" folder as default when saving a file.
*** This bug is a duplicate of bug 194904 *** https://bugs.launchpad.net/bugs/194904 ** Changed in: gedit (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gedit (Ubuntu) Status: New => Triaged ** This bug has been marked a duplicate of bug 194904 Text editor default save directory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1856005 Title: Set "Documents" folder as default when saving a file. Status in gedit: Unknown Status in gedit package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 3.34.0-1 3) I opened Gedit, typed some stuff and then clicked the save button. Gedit should save documents to the documents folder by default. 4) Gedit defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1856005/+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 1856187] [NEW] Cups wont print to smb-shared printer requiring user authentication via kerberos
Public bug reported: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not true: the printer requires authentication. Maybe a bug. This print server requires any user to be authenticated and have a kerberos ticket. This is true. The user has a kerberos ticket and this user is allowed to print. The users kerberos ticket cache is available in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it into account. May be a bug too. Changing "AuthInfoRequired" from "none" to "username,password" allows cups to print. But this has to be done editing /etc/cups/printers.conf. The web printer configuration just does not allow to set anything else than "none". This is a bug. Documentation misses what "AuthInfoRequired" has to be set for if kerberos authentication will be used. This is a bug too! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 13:54:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** 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/1856187 Title: Cups wont print to smb-shared printer requiring user authentication via kerberos Status in cups package in Ubuntu: New Bug description: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not
[Desktop-packages] [Bug 1789656] Re: Complete system freeze happening sporadically when running chromium
This is the journal just before freeze. It does not seem to be referred to Chrome ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+attachment/5311974/+files/journal.txt -- 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/1789656 Title: Complete system freeze happening sporadically when running chromium Status in chromium-browser package in Ubuntu: New Bug description: This context is in syslog before complete system freeze, repeated a few times (attached file). Aug 29 15:43:41 chromium-browser.desktop[5003]: [5003:5017:0829/154341.786374:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service It happens sporadic but only after the start of chromium-browser loading about 20 tabs and moving from one to another. Complete system freeze, no console, no REISUB works. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 68.0.3440.106-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DVI-I-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLUoHABUUAQOANR54Cu6Ro1RMmSYPUFS/74BxT4EAgUCBgJUAlQ+zAAEBAjqAGHE4LUBYLEUAEyshAAAeAjqA0HI4LUAQLEWAEyshAAAe/QAYSxpRFwAKICAgICAg/ABTTUZYMjQ5MEhECiAgAYoCAxzxS5MEBRQDEhAfICEiIwkHB2cDDAAQALgtAR2A0HIcFiAQLCWAEyshAACeAR2AGHEcFiBYLCUAEyshAACeAR0AclHQHiBuKFUAEyshAAAejArQkCBAMSAMQFUAEyshAAAejArQiiDgLRAQPpYAEyshAAAezg== modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Wed Aug 29 16:01:30 2018 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2012-02-05 (2397 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120204) Load-Avg-1min: 2.18 Load-Processes-Running-Percent: 0.1% MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-08-14 (15 days ago) dmi.bios.date: 07/30/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QLD PRO 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.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2017-01-25T17:18:56.251795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+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 1856179] [NEW] WINE .desktop files are not grouped into a folder on the app screen.
Public bug reported: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop app icons should be automatically grouped into a folder on the app screen. I am not able to manually group them. I can group other app icons. 4) WINE. desktop apps were NOT grouped into a folder on the app screen. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 - Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 - Version table: - *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 - 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 3.34.1-1ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages + Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 + Version table: + *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 + 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.34.1-1ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop apps should be grouped into a folder on the app screen. 4) WINE. desktop apps were NOT grouped into a folder on the app screen. ** Description changed: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop apps should be grouped into a folder on the app screen. - 4) WINE. desktop apps were NOT grouped into a folder on the app screen. + 4) WINE .desktop apps were NOT grouped into a folder on the app screen. ** Description changed: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages - 3) WINE .desktop apps should be grouped into a folder on the app screen. - 4) WINE .desktop apps were NOT grouped into a folder on the app screen. + 3) WINE .desktop app icons should be automatically grouped into a folder on the app screen. I am not able to manually group them. I can group other app icons. + 4) WINE. desktop apps were NOT grouped into a folder on the app screen. -- 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/1856179 Title: WINE .desktop files are not grouped into a folder on the app screen. Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 3) WINE .desktop app icons should be automatically grouped into a folder on the app screen. I am not able to manually group them. I can group other app icons. 4) WINE. desktop apps were NOT grouped into a folder on the app screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856179/+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 1856145] Re: Display a message box if a user double clicks on an .exe or .msi file.
software-center was superseded by gnome-software some time ago ** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856145 Title: Display a message box if a user double clicks on an .exe or .msi file. Status in gnome-software package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If a user clicks on an .exe or.msi file, display a "Windows software is not compatible with Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1856145/+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 1854665] Re: If a user adds a "Select Custom Icon" to a usb drive, display the custom icon on the dash instead of the default gray usb icon.
The correct icon is displayed in /media/htpc ** Attachment added: "drive.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1854665/+attachment/5311967/+files/drive.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1854665 Title: If a user adds a "Select Custom Icon" to a usb drive, display the custom icon on the dash instead of the default gray usb icon. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 19.10 1. I connected a USB external HDD to my computer. A gray USB icon appeared on the dash. I started the Files app and then right clicked on the name of my USB external HDD and then clicked properties. I then clicked the "Select Custom Icon" and selected an icon. The selected custom icon appears on the drive properties screen. 2. The dash should display the selected custom icon for my USB external HDD instead of the default gray USB icon. 3. The dash still shows the default gray USB icon for my external USB HDD. The selected custom icon did not appear on the dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1854665/+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 1856145] [NEW] Display a message box if a user double clicks on an .exe or .msi file.
You have been subscribed to a public bug: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If a user clicks on an .exe or.msi file, display a "Windows software is not compatible with Ubuntu. Some Windows software can function correctly on Ubuntu, if a program called WINE is installed. Would you like to download and install WINE?" 4) Double clicking on an .exe file started Archive manager. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- Display a message box if a user double clicks on an .exe or .msi file. https://bugs.launchpad.net/bugs/1856145 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856166] Re: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers
** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1856166 Title: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers Status in nvidia-graphics-drivers-430 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: Triaged Bug description: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1856166/+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 1854472] Re: ubuntu-drivers-common fails when no PATH environment variable is passed
This my verification for eoan. This is the old package and the failure: :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.7.6 Candidate: 1:0.7.6 Version table: *** 1:0.7.6 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status :~$ PATH="" /usr/bin/ubuntu-drivers devices ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 38, in detect universal_newlines=True) File "/usr/lib/python3.7/subprocess.py", line 800, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.7/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay': 'aplay' Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 268, in sys.exit(command(args)) File "/usr/bin/ubuntu-drivers", line 85, in command_devices sys_path=sys_path, freeonly=args.free_only) File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 543, in system_device_drivers if not _is_manual_install(apt_cache[pkg]): File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 226, in _is_manual_install stderr=subprocess.PIPE) File "/usr/lib/python3.7/subprocess.py", line 800, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.7/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'modinfo': 'modinfo' And this is what happens after installing the package in eoan-proposed: :~$ PATH="" /usr/bin/ubuntu-drivers devices == /sys/devices/pci:00/:00:1c.0/:02:00.0 == modalias : pci:v8086d24FDsv8086sd0010bc02sc80i00 vendor : Intel Corporation model: Wireless 8265 / 8275 (Dual Band Wireless-AC 8265) driver : backport-iwlwifi-dkms - distro free :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.7.6.0.1 Candidate: 1:0.7.6.0.1 Version table: *** 1:0.7.6.0.1 400 400 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.7.6 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1854472 Title: ubuntu-drivers-common fails when no PATH environment variable is passed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Eoan: Fix Committed Bug description: SRU Request: [Impact] * ubuntu-drivers-common fails when no PATH environment variable is passed: https://errors.ubuntu.com/problem/52d04f39f8cbdb77d65ec57f19a5801284c1e2b0 * While the reasons why the PATH variable is empty are unknown, the ubuntu-drivers tools should be more robust and not fail, and we can expect a minimal PATH (such as /sbin:/usr/sbin:/bin:/usr/bin) to be available on the system. [Test Case] * Install ubuntu-drivers-common from the -proposed repository. * Call the ubuntu drivers tool passing the "devices" parameter: ubuntu-drivers devices * Call the ubuntu drivers tool passing the "devices" parameter and an empty PATH variable: PATH="" /usr/bin/ubuntu-drivers devices * Neither case should fail any more. [Regression Potential] * Low. Nothing really changes in the functioning if the PATH variable is not empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1854472/+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 1854472] Re: ubuntu-drivers-common fails when no PATH environment variable is passed
I can confirm that the problem is solved in bionic: :~$ PATH="" /usr/bin/ubuntu-drivers devices :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.5.2.5 Candidate: 1:0.5.2.5 Version table: *** 1:0.5.2.5 400 400 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.5.2.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:0.5.2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** 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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1854472 Title: ubuntu-drivers-common fails when no PATH environment variable is passed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Eoan: Fix Committed Bug description: SRU Request: [Impact] * ubuntu-drivers-common fails when no PATH environment variable is passed: https://errors.ubuntu.com/problem/52d04f39f8cbdb77d65ec57f19a5801284c1e2b0 * While the reasons why the PATH variable is empty are unknown, the ubuntu-drivers tools should be more robust and not fail, and we can expect a minimal PATH (such as /sbin:/usr/sbin:/bin:/usr/bin) to be available on the system. [Test Case] * Install ubuntu-drivers-common from the -proposed repository. * Call the ubuntu drivers tool passing the "devices" parameter: ubuntu-drivers devices * Call the ubuntu drivers tool passing the "devices" parameter and an empty PATH variable: PATH="" /usr/bin/ubuntu-drivers devices * Neither case should fail any more. [Regression Potential] * Low. Nothing really changes in the functioning if the PATH variable is not empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1854472/+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 1855736] Re: Duplicity fails to start
I had done, but just to be sure I purged it again, autoremove the un- needed items (python fasteners etc), reinstalled, rebooted, and get the same error on "duplicity --version" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+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 1855709] Re: [nvidia] Activities search menu won't show any icon
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1855709 Title: [nvidia] Activities search menu won't show any icon Status in gnome-shell package in Ubuntu: Invalid Bug description: since I upgraded from ubuntu 19.04 to ubuntu 19.10, the search function will not show any software, file, etc. icon anymore. If I write in the search box the exact name of the software, say for example "writer", and I hit the enter key the program will start fine. So, the search itself is working, I just do not see any icon. If I use Super + A, I can see all the icons there, but if I start typing something in the search box, icons disappear. All my Gnome Shell extensions work fine and don't show any sign of incompatibility or error: Text translator, Drop down terminal, Dynamic panel transparency, Gsconnect, Impatience, and Openweather. I have already trued to reinstall gnome-session with no result. I am running gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 in ubuntu 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-06-13 (545 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: eoan third-party-packages Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-24 (46 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855709/+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 1856160] Re: Bar between bread crumbs and search icon.
** Attachment added: "screenshot.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1856160/+attachment/5311949/+files/screenshot.png ** Description changed: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 - 3) No bar between bread crumbs and search icon. If I remember correctly. + 3) There should be no bar between bread crumbs and the search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' - b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' - b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' + b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANG=en_US.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- 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/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) There should be no bar between bread crumbs and the search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1856166] [NEW] NVS 5200M not supported by 435, but is recommended by ubuntu-drivers
Public bug reported: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1856166 Title: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers Status in nvidia-graphics-drivers-430 package in Ubuntu: New Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1856166/+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 1855709] Re: [nvidia] Activities search menu won't show any icon
Finally! The issue was definitely in the graphic driver. I purged the nvidia-440 (which, by the way, was the suggested open source driver) and the issue was gone using the standard Nouveau driver. I reinstalled the nvidia driver from terminal, and the funny thing is I wrote nvidia- driver-435* but it installed nvidia-driver-440. The important thing is that now the issue is gone and here is the output (or part of it) of journalctl -b0: rlb@rlb-GA-970A-D3:~$ journalctl -b0 -- Logs begin at Wed 2018-06-13 11:35:32 CEST, end at Thu 2019-12-12 10:42:44 CE dic 12 10:38:27 rlb-GA-970A-D3 kernel: Linux version 5.3.0-24-generic (buildd@lg dic 12 10:38:27 rlb-GA-970A-D3 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5. dic 12 10:38:27 rlb-GA-970A-D3 kernel: KERNEL supported cpus: dic 12 10:38:27 rlb-GA-970A-D3 kernel: Intel GenuineIntel dic 12 10:38:27 rlb-GA-970A-D3 kernel: AMD AuthenticAMD dic 12 10:38:27 rlb-GA-970A-D3 kernel: Hygon HygonGenuine dic 12 10:38:27 rlb-GA-970A-D3 kernel: Centaur CentaurHauls dic 12 10:38:27 rlb-GA-970A-D3 kernel: zhaoxin Shanghai dic 12 10:38:27 rlb-GA-970A-D3 kernel: random: get_random_u32 called from bsp_in dic 12 10:38:27 rlb-GA-970A-D3 kernel: x86/fpu: Supporting XSAVE feature 0x001: dic 12 10:38:27 rlb-GA-970A-D3 kernel: x86/fpu: Supporting XSAVE feature 0x002: dic 12 10:38:27 rlb-GA-970A-D3 kernel: x86/fpu: Supporting XSAVE feature 0x004: dic 12 10:38:27 rlb-GA-970A-D3 kernel: x86/fpu: xstate_offset[2]: 576, xstate_s dic 12 10:38:27 rlb-GA-970A-D3 kernel: x86/fpu: Enabled xstate features 0x7, con dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-provided physical RAM map: dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0x-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0x0009f800-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0x000f-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0x0010-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0xcfda-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0xcfdd1000-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0xcfe0-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0xe000-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0xfec0-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: BIOS-e820: [mem 0x0001-0x dic 12 10:38:27 rlb-GA-970A-D3 kernel: NX (Execute Disable) protection: active dic 12 10:38:27 rlb-GA-970A-D3 kernel: SMBIOS 2.4 present. dic 12 10:38:27 rlb-GA-970A-D3 kernel: DMI: Gigabyte Technology Co., Ltd. GA-970 dic 12 10:38:27 rlb-GA-970A-D3 kernel: tsc: Fast TSC calibration using PIT dic 12 10:38:27 rlb-GA-970A-D3 kernel: tsc: Detected 3624.099 MHz processor dic 12 10:38:27 rlb-GA-970A-D3 kernel: e820: update [mem 0x-0x0fff] dic 12 10:38:27 rlb-GA-970A-D3 kernel: e820: remove [mem 0x000a-0x000f] dic 12 10:38:27 rlb-GA-970A-D3 kernel: AGP: No AGP bridge found dic 12 10:38:27 rlb-GA-970A-D3 kernel: last_pfn = 0x22f000 max_arch_pfn = 0x4000 dic 12 10:38:27 rlb-GA-970A-D3 kernel: MTRR default type: uncachable dic 12 10:38:27 rlb-GA-970A-D3 kernel: MTRR fixed ranges enabled: dic 12 10:38:27 rlb-GA-970A-D3 kernel: 0-9 write-back dic 12 10:38:27 rlb-GA-970A-D3 kernel: A-B uncachable dic 12 10:38:27 rlb-GA-970A-D3 kernel: C-C7FFF write-protect dic 12 10:38:27 rlb-GA-970A-D3 kernel: C8000-F uncachable dic 12 10:38:27 rlb-GA-970A-D3 kernel: MTRR variable ranges enabled: dic 12 10:38:27 rlb-GA-970A-D3 kernel: 0 base mask 8000 w dic 12 10:38:27 rlb-GA-970A-D3 kernel: 1 base 8000 mask C000 w dic 12 10:38:27 rlb-GA-970A-D3 kernel: 2 base C000 mask F000 w dic 12 10:38:27 rlb-GA-970A-D3 kernel: 3 base CFE0 mask FFE0 u dic 12 10:38:27 rlb-GA-970A-D3 kernel: 4 disabled dic 12 10:38:27 rlb-GA-970A-D3 kernel: 5 disabled dic 12 10:38:27 rlb-GA-970A-D3 kernel: 6 disabled dic 12 10:38:27 rlb-GA-970A-D3 kernel: 7 disabled dic 12 10:38:27 rlb-GA-970A-D3 kernel: TOM2: 00022f00 aka 8944M dic 12 10:38:27 rlb-GA-970A-D3 kernel: x86/PAT: Configuration [0-7]: WB WC UC- dic 12 10:38:27 rlb-GA-970A-D3 kernel: total RAM covered: 3326M dic 12 10:38:27 rlb-GA-970A-D3 kernel: Found optimal setting for mtrr clean up dic 12 10:38:27 rlb-GA-970A-D3 kernel: gran_size: 64K chunk_size: 4M dic 12 10:38:27 rlb-GA-970A-D3 kernel: e820: update [mem 0xcfe0-0x] dic 12 10:38:27 rlb-GA-970A-D3 kernel: last_pfn = 0xcfda0 max_arch_pfn = 0x4 dic 12 10:38:27 rlb-GA-970A-D3 kernel: found SMP MP-table at [mem 0x000f4c60-0x0 dic 12 10:38:27 rlb-GA-970A-D3 kernel: check: Scanning 1 areas for low memory co dic 12 10:38:27 rlb-GA-970A-D3 kernel: Using GB pages for direct mapping dic 12 10:38:27 rlb-GA-970A-D3 kernel: BRK [0x79c01000, 0x79c01fff] PGTABLE dic 12 10:38:27
[Desktop-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
If you are worried about what the Pulse Audio change is actually doing, here's a description: 1. there is a new "snap-policy" PA module that is loaded by default. 2. when a client attempts to use the microphone and has a "snap.*" AppArmor label, it contacts snapd to check whether that app has permission to record audio (as opposed to simply playing sounds). 3. if the client is not a snap application or it is a snap application with record access, then PA will create record stream. So there should be no problem with removing snapd again. In fact the policy module should effectively be inert if no snaps are ever run, not even trying to talk to snapd. The "Recommends: snapd" is definitely too strong for the way Pulse Audio is using libsnapd-glib. Once snapd-glib's dependency is relaxed, we should be able to push this update again. -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856160] Re: Bar between bread crumbs and search icon.
Thank you for your bug report. Why do you think there should be a bar there? It seems like an upstream design decision...? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Opinion -- 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/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) No bar between bread crumbs and search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
The Xenial/Bionic SRUs have been removed until the Recommends on snapd gets lowered to a Suggest -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856160] [NEW] Bar between bread crumbs and search icon.
Public bug reported: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) No bar between bread crumbs and search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) No bar between bread crumbs and search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
AFAICT the addition of snapd as an indirect recommends was an unintended consequence of the update, so I'm tagging this regression-update. ** Tags added: regression-update -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Note also that it's only a recommends, so while the problem is being worked on you can install the SRU using --no-install-recommends as a workaround (or remove snapd again after update) -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1
@Gord, is your issue with libsnapd-glib or with the fact that the lib recommends snapd and that recommends are pulled in by default? The library as Daniel pointed out shouldn't be an issue, it's small and not doing anything if the service is not there. ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - pulseaudio now depends on libsnapd-glib1 + pulseaudio now depends on libsnapd-glib1 which recommends snapd -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted
The most annoying part about this bug is that it leaves the user guessing what's going on. I did not know if it is an issue with local or remote system. Speculating that deleting excluded folders might be triggering the issue etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1600299 Title: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup package in Mandriva: New Bug description: I've got my system set up with off-site backup over sftp. This works fine but the problem is that while deja-dup is gathering files and calculating the backup delta the connection to the server times out. This means that it's not available when deja-dup actually tries to push files to the server and results in this error message: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted (16) By sitting in the file manager and jumping between folders the connection can be kept alive but that's rather annoying and requires my presence. Would really like to see deja-dup actually trying to set up the connection again instead. Using: Manjaro 16.06.1 deja-dup 34.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1600299/+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 1856005] Re: Set "Documents" folder as default when saving a file.
Setting a personal preference was requested a long time ago but never implemented - https://gitlab.gnome.org/GNOME/gedit/issues/36 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/issues #36 https://gitlab.gnome.org/GNOME/gedit/issues/36 ** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/issues/36 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1856005 Title: Set "Documents" folder as default when saving a file. Status in gedit: Unknown Status in gedit package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.34.0-1 3) I opened Gedit, typed some stuff and then clicked the save button. Gedit should save documents to the documents folder by default. 4) Gedit defaults to the Home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1856005/+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
