[Touch-packages] [Bug 1714813] Re: No headphone sound.
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1714813 Title: No headphone sound. Status in pulseaudio package in Ubuntu: Expired Bug description: Reproduces on: Ubuntu Mate: 16.04.3, 17.04, 17.10 Kubuntu: 17.04, 17.10 Ubuntu Budgie: 17.10 Probably not DE related since it is happening in KDE, Mate, and Budgie. Here's the output of `aplay -l` and `lspci`, let me know what other details I can provide: $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2) 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01) 04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1714813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756198] Re: Intermittent HDMI sound, working with some videos/audios, failing with others
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1756198 Title: Intermittent HDMI sound, working with some videos/audios, failing with others Status in pulseaudio package in Ubuntu: Expired Bug description: I'm using Lubuntu 17.10 on an ACER REVO RL80 connected to my TV through HDMI. The sound output is configured via sound settings (pavucontrol) to HDMI ouput. The sound is OK with some apps, and KO with some others. For example in VLC, it works usually fine. But on chromium/youtube, the sound is HS. Actually, i think it's not really a per app problem, but it might depend more on the type of audio being played. I thought the audio was working fine on firefox youtube at first, but once I ran into a specific video with the audio HS (and I checked this video had sound). When the audio is HS on a video play, if I start a video that usually doesn't have the problem, this video has the audio HS too. And reversely, if the audio is OK on a video, and if I start a video that usually have the problem, this time the video has its audio OK. Knowing this, I made a small sript to "fix" the audio of a video witht he problem. I pause the video with the audio problem, I start a sound hat usually doesn't have the problem, and I change the audio output back and forth to HDMI output again. It usually fixes audio, and I jsute need to resume the video with the problem BEFORE the good audio is over, and it's OK. This is my script mpv /path/to/whitenoise_48k.wav & pacmd set-card-profile 0 output:analog-stereo pacmd set-card-profile 0 output:hdmi-stereo And it's interesting to note that the same sound in 44k doesn't work (whitenoise_44k.wav). Weird stuff... These are the outputs of some commands, can make more if you want. aplay --list-devices List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC662 rev3 Digital [ALC662 rev3 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 lspci -v 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) Subsystem: Acer Incorporated [ALI] 7 Series/C216 Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at f7e3 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel pacmd list-cards 1 card(s) available. index: 0 name: driver: owner module: 22 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7e3 irq 30" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1e20" device.product.name = "7 Series/C216 Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 60, available: no) output:analog-stereo: Analog Stereo Output (priority 6000, available: no) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: no) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560, available: unknown) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460, available: unknown) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1b.0.hdmi-stereo/#5: Built-in Audio Digital Stereo (HDMI)
[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic
I can still reproduce this bug with the Ubuntu cosmic 20181014 iso on VirtualBox (my host is also running cosmic and I use the distro-packaged VirtualBox). The workaround mentioned in the bug description works well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1796822 Title: Desktop live cd boots corrupted screen in Virtualbox on Bionic Status in initramfs-tools package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in initramfs-tools source package in Cosmic: Fix Released Status in xorg-server source package in Cosmic: Confirmed Bug description: On a Bionic host running the standard archive version of Virtualbox and the daily ISO of Cosmic, the live session starts with a corrupted graphical display, as can be seen here: https://imgur.com/a/rkTId4S (also attached) Switching VTs to 2 and back to 1 clears the display and things work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797735] [NEW] Use Ubuntu-specific Google API keys
Public bug reported: Test Case = In the "Welcome to Ubuntu" wizard in Ubuntu 18.10, on the Online Accounts Screen, click Google. The dialog currently reads "Sign in to continue to GNOME" After authenticating, it says "GNOME wants to access your Google account" (Because it's a web page, Google can change the exact wording at any time.) Suggestion == Canonical should consider using its own Google API keys. I suggest using different keys at least for each LTS release. Benefits These API keys have usage limits. Ubuntu is a substantial part of GNOME's usage and it makes sense to spread out the load more. Occasionally, there is a need to replace keys. If Canonical already has a system for these keys, it might be able to replace these keys faster. An example of when it was needed was with Evolution 3.20 which had a bug (sort of a DDoS) that led to Google throttling all users of that API key. Other Info == Both GOA and EDS have Google keys and Canonical should probably use separate keys for each. (Users of the Evolution app can choose to use GNOME Online Accounts or authenticate directly in Evolution without using GOA.) ** Affects: evolution-data-server (Ubuntu) Importance: Low Status: New ** Affects: gnome-online-accounts (Ubuntu) Importance: Low Status: New ** Tags: cosmic ** Also affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Description changed: Test Case = In the "Welcome to Ubuntu" wizard in Ubuntu 18.10, on the Online Accounts Screen, click Google. The dialog currently reads "Sign in to continue to GNOME" + After authenticating, it says "GNOME wants to access your Google account" (Because it's a web page, Google can change the exact wording at any time.) Suggestion == Canonical should consider using its own Google API keys. I suggest using different keys at least for each LTS release. Benefits These API keys have usage limits. Ubuntu is a substantial part of GNOME's usage and it makes sense to spread out the load more. Occasionally, there is a need to replace keys. If Canonical already has a system for these keys, it might be able to replace these keys faster. An example of when it was needed was with Evolution 3.20 which had a bug (sort of a DDoS) that led to Google throttling all users of that API key. Other Info == Both GOA and EDS have Google keys and Canonical should probably use separate keys for each. (Users of the Evolution app can choose to use GNOME Online Accounts or authenticate directly in Evolution without using GOA.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1797735 Title: Use Ubuntu-specific Google API keys Status in evolution-data-server package in Ubuntu: New Status in gnome-online-accounts package in Ubuntu: New Bug description: Test Case = In the "Welcome to Ubuntu" wizard in Ubuntu 18.10, on the Online Accounts Screen, click Google. The dialog currently reads "Sign in to continue to GNOME" After authenticating, it says "GNOME wants to access your Google account" (Because it's a web page, Google can change the exact wording at any time.) Suggestion == Canonical should consider using its own Google API keys. I suggest using different keys at least for each LTS release. Benefits These API keys have usage limits. Ubuntu is a substantial part of GNOME's usage and it makes sense to spread out the load more. Occasionally, there is a need to replace keys. If Canonical already has a system for these keys, it might be able to replace these keys faster. An example of when it was needed was with Evolution 3.20 which had a bug (sort of a DDoS) that led to Google throttling all users of that API key. Other Info == Both GOA and EDS have Google keys and Canonical should probably use separate keys for each. (Users of the Evolution app can choose to use GNOME Online Accounts or authenticate directly in Evolution without using GOA.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1797735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1796822 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1796822 Title: Desktop live cd boots corrupted screen in Virtualbox on Bionic Status in initramfs-tools package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in initramfs-tools source package in Cosmic: Fix Released Status in xorg-server source package in Cosmic: Confirmed Bug description: On a Bionic host running the standard archive version of Virtualbox and the daily ISO of Cosmic, the live session starts with a corrupted graphical display, as can be seen here: https://imgur.com/a/rkTId4S (also attached) Switching VTs to 2 and back to 1 clears the display and things work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200766/+files/lp1794629-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200768/+files/lp1794629-artful.debdiff ** Patch removed: "bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200217/+files/bionic-upstream-delay-bailout-for-invalid-authenticating-user.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200767/+files/lp1794629-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
All debdiffs tested in the wild (except artful). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
** Patch added: "lp1794629-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5200765/+files/lp1794629-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 848164] Re: Auto connect to 3G network only works after manually enabling mobile broadband after modem inserted/bootup/resume
Issue still here in 14.04 in network-manager 0.9.8.8-0ubuntu7.3. 3g stick doesn't auto reconnect after hibernation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/848164 Title: Auto connect to 3G network only works after manually enabling mobile broadband after modem inserted/bootup/resume Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager package in Debian: Fix Released Bug description: NetworkManager does not connect to my 3G provider at login, even though it is configured for automatic connection. What I expect: - When selecting the option "connect automatically" in the network-setting for a mobile connection, it should connect automatically, like it has until Ubuntu 11.04. What happens: - When I plug in the modem (USB; e.g. "UMTS-Stick"), it appears as available connection, but does not connect; ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Mon Sep 12 20:32:01 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 10.0.0.1 dev wlan0 proto static 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.6 169.254.0.0/16 dev wlan0 scope link metric 1000 Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, no user) LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to oneiric on 2011-09-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/848164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797727] Re: ncurses in cosmic breaks many Mono apps
** Package changed: ncurses (Ubuntu) => mono (Ubuntu) ** Bug watch added: github.com/mono/mono/issues #6752 https://github.com/mono/mono/issues/6752 ** Also affects: mono via https://github.com/mono/mono/issues/6752 Importance: Unknown Status: Unknown ** Description changed: Impact -- Many mono apps don't run in cosmic when run from a terminal. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. Test Case - Install the updated ncurses packages. You may need to log out and log back in (or reboot). Install pdfmod. - From gnome-terminal, run + From gnome-terminal, run $ pdfmod The app should start. Regression Potential --- - This change was applied in Debian in 6.1+20180714-1 in July. - https://salsa.debian.org/debian/ncurses/commit/3f3e26996d Other Info -- I noticed this while working on pdfmod for LP: #1771025 . The only app listed there that runs before this fix in cosmic is bareftp. - - For more details about the bug, see the Debian bug and the Debian commit - message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1797727 Title: ncurses in cosmic breaks many Mono apps Status in mono: Unknown Status in mono package in Ubuntu: Triaged Bug description: Impact -- Many mono apps don't run in cosmic when run from a terminal. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. Test Case - Install the updated ncurses packages. You may need to log out and log back in (or reboot). Install pdfmod. From gnome-terminal, run $ pdfmod The app should start. Regression Potential --- Other Info -- I noticed this while working on pdfmod for LP: #1771025 . The only app listed there that runs before this fix in cosmic is bareftp. To manage notifications about this bug go to: https://bugs.launchpad.net/mono/+bug/1797727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797727] Re: ncurses in cosmic breaks many Mono apps
** Description changed: Impact -- - Many mono apps don't run in cosmic. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. + Many mono apps don't run in cosmic when run from a terminal. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. Test Case - Install the updated ncurses packages. You may need to log out and log back in (or reboot). Install pdfmod. - Run pdfmod. + From gnome-terminal, run + $ pdfmod The app should start. Regression Potential --- This change was applied in Debian in 6.1+20180714-1 in July. https://salsa.debian.org/debian/ncurses/commit/3f3e26996d Other Info -- I noticed this while working on pdfmod for LP: #1771025 . The only app listed there that runs before this fix in cosmic is bareftp. For more details about the bug, see the Debian bug and the Debian commit message. ** Changed in: ncurses (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1797727 Title: ncurses in cosmic breaks many Mono apps Status in ncurses package in Ubuntu: Triaged Bug description: Impact -- Many mono apps don't run in cosmic when run from a terminal. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. Test Case - Install the updated ncurses packages. You may need to log out and log back in (or reboot). Install pdfmod. From gnome-terminal, run $ pdfmod The app should start. Regression Potential --- This change was applied in Debian in 6.1+20180714-1 in July. https://salsa.debian.org/debian/ncurses/commit/3f3e26996d Other Info -- I noticed this while working on pdfmod for LP: #1771025 . The only app listed there that runs before this fix in cosmic is bareftp. For more details about the bug, see the Debian bug and the Debian commit message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1797727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797727] [NEW] ncurses in cosmic breaks many Mono apps
Public bug reported: Impact -- Many mono apps don't run in cosmic when run from a terminal. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. Test Case - Install the updated ncurses packages. You may need to log out and log back in (or reboot). Install pdfmod. >From gnome-terminal, run $ pdfmod The app should start. Regression Potential --- This change was applied in Debian in 6.1+20180714-1 in July. https://salsa.debian.org/debian/ncurses/commit/3f3e26996d Other Info -- I noticed this while working on pdfmod for LP: #1771025 . The only app listed there that runs before this fix in cosmic is bareftp. For more details about the bug, see the Debian bug and the Debian commit message. ** Affects: ncurses (Ubuntu) Importance: High Assignee: Jeremy Bicha (jbicha) Status: Triaged ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1797727 Title: ncurses in cosmic breaks many Mono apps Status in ncurses package in Ubuntu: Triaged Bug description: Impact -- Many mono apps don't run in cosmic when run from a terminal. Although mono apps aren't as popular or as well-maintained as they used to be, this is still bad. Test Case - Install the updated ncurses packages. You may need to log out and log back in (or reboot). Install pdfmod. From gnome-terminal, run $ pdfmod The app should start. Regression Potential --- This change was applied in Debian in 6.1+20180714-1 in July. https://salsa.debian.org/debian/ncurses/commit/3f3e26996d Other Info -- I noticed this while working on pdfmod for LP: #1771025 . The only app listed there that runs before this fix in cosmic is bareftp. For more details about the bug, see the Debian bug and the Debian commit message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1797727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797717] [NEW] fstrim -av tries to trim read only mounted ntfs-3g and fails
Public bug reported: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails Status in util-linux package in Ubuntu: New Bug description: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797715] [NEW] Libvirt kvm windows guest has no network after upgrade to 18.10
Public bug reported: Today I upgraded to 18.10 beta and now my windows guest doesn't have network. The network is configured to NAT. The network card is of course shown in the guest, but it doesn't get an IP via dhcp. Even configuring a static IP doesn't help - the same network IP of the host is not reachable from the guest. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => libvirt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797715 Title: Libvirt kvm windows guest has no network after upgrade to 18.10 Status in libvirt package in Ubuntu: New Bug description: Today I upgraded to 18.10 beta and now my windows guest doesn't have network. The network is configured to NAT. The network card is of course shown in the guest, but it doesn't get an IP via dhcp. Even configuring a static IP doesn't help - the same network IP of the host is not reachable from the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1797715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797714] [NEW] No sound after upgrade to Kubuntu 18.10 beta
Public bug reported: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: New Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771036] Re: Please remove libgnome-keyring from Ubuntu
** No longer affects: mail-notification (Ubuntu) ** No longer affects: mate-power-manager (Ubuntu) ** Description changed: libgnome-keyring has been removed from Debian Testing and will not be included in the Debian 10 "Buster" release. We should do the same. Users who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few years. This bug depends on the libgnome removal LP: #1771031 - ukui-power-manager is a blocker LP: #1767165 - - mate-power-manager was fixed in Debian so presumably can be done in - 18.10 too. + ukui-power-manager is a blocker LP: #1767165 (but mate-power-manager was + done) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771036 Title: Please remove libgnome-keyring from Ubuntu Status in libgnome-keyring package in Ubuntu: New Status in moonshot-ui package in Ubuntu: New Status in mysql-workbench package in Ubuntu: New Bug description: libgnome-keyring has been removed from Debian Testing and will not be included in the Debian 10 "Buster" release. We should do the same. Users who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few years. This bug depends on the libgnome removal LP: #1771031 ukui-power-manager is a blocker LP: #1767165 (but mate-power-manager was done) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnome-keyring/+bug/1771036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554471] Re: Mouse not working
Gosh, this is an old post. Thanks for the link. Sadly I no longer have the Cougar mouse so can't test the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1554471 Title: Mouse not working Status in xorg package in Ubuntu: Triaged Bug description: I have a Cougar 450M gaming mouse. I am dual booting between Windows 10 and Xubuntu. The mouse works perfectly in Windows but fails dismally in any flavour of Ubuntu (tried Ubuntu, Lubuntu and Xubuntu) including during the OS installation phase. On very rare occasion it will work when I boot into Ubuntu, but 9 out of 10 times the only functions available are the mouse buttons and scroll wheel. There is also a DPI adjustment button on the 450M which cycles through the various available settings and changes colour based on the current DPI setting. I have noted that if you press the button once, the button changes colour as expected, but if you continue to press the button, nothing happens. It seems to freeze on that setting. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 8 10:52:02 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2730] InstallationDate: Installed on 2016-03-03 (4 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Mar 8 10:48:41 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797695] Re: packagekitd crashed with SIGABRT in std::terminate()
*** This bug is a duplicate of bug 1796315 *** https://bugs.launchpad.net/bugs/1796315 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1796315, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1797695/+attachment/5200625/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1797695/+attachment/5200627/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1797695/+attachment/5200630/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1797695/+attachment/5200631/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1797695/+attachment/5200632/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1797695/+attachment/5200633/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1797695/+attachment/5200634/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1796315 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1797695 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: New Bug description: packagekit ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu6 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Sat Oct 13 17:08:08 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-10-13 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1797695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791983] Re: kill -TERM exitcode regression 16.04
No update on this bug within a month. Ubuntu 16.04 LTS will be kept broken? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1791983 Title: kill -TERM exitcode regression 16.04 Status in procps package in Ubuntu: New Bug description: I had a regression error in one of my testsuites. https://github.com/gdraheim/docker-systemctl-replacement/issues/43 After investigating I did find that the command "kill -TERM" behaves different in Ubuntu 16.04 in comparison to all other Ubuntu versions and in comparison to all other tested Linux distributions (opensuse,centos). > "kill -TERM" does report an exitcode=0 (OK) where it should say failed. Note that the testsuite of coreutils does define a behaviour of not-ok at http://git.savannah.gnu.org/cgit/coreutils.git/tree/tests/misc/kill.sh There you can see # params required returns_ 1 env kill || fail=1 returns_ 1 env kill -TERM || fail=1 However this is the result tested with the available docker images == kill ubuntu:14.04 => 1 ubuntu:16.04 => 1 ubuntu:18.04 => 1 ubuntu:18.10 => 1 == kill -TERM ubuntu:14.04 => 1 ubuntu:16.04 => 0 ubuntu:18.04 => 1 ubuntu:18.10 => 1 I am attaching the testscript that shows the results above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1791983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797678] Re: Printing stops with Status as "Idle - Filter failed"
Solution found in Ask Ubuntu site at: https://askubuntu.com/questions/1081885/printer-stopped-working-after-upgrade-16-04-to-18-04 Solution is: sudo rmdir /usr/share/ghostscript/9.25/iccprofiles sudo apt-get install --reinstall libgs9-common -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1797678 Title: Printing stops with Status as "Idle - Filter failed" Status in cups package in Ubuntu: New Bug description: This happened after an upgrade from Xenial to Bionic on this Barebones PC. Interestingly after an upgrade from Xenial to Bionic on a Laptop this problem did not occur. It also occurred with a clean install on another Barebones PC, but was fixed by installing package hplip. I've tried installing hplip on this PC but to no effect. PS I don't know if the problem is with CUPS or hplip or another package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 13 09:10:56 2018 InstallationDate: Installed on 2018-02-09 (245 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Deskjet_2540_series_527711_: ipp://HPD0BF9C527711.local:631/ipp/print device for HP-Deskjet-2540-series: dnssd://Deskjet%202540%20series%20%5B527711%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9c527711 device for Samsung-SCX-472x: socket://192.168.101.20:9100 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_2540_series_527711_.ppd', '/etc/cups/ppd/Samsung-SCX-472x.ppd', '/etc/cups/ppd/HP-Deskjet-2540-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_2540_series_527711_.ppd: Permission denied grep: /etc/cups/ppd/Samsung-SCX-472x.ppd: Permission denied grep: /etc/cups/ppd/HP-Deskjet-2540-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=f83725aa-582a-4c36-9ad8-738122da2e0c ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-07 (5 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797678/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361610] Re: libPCRE3 8.31 regex matching is not working
** Tags added: upgrade-software-version
** Changed in: poco (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1361610
Title:
libPCRE3 8.31 regex matching is not working
Status in pcre3 package in Ubuntu:
Invalid
Status in poco package in Ubuntu:
Fix Released
Bug description:
It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
handle regex matching alright. This also affects the libPocoFoundation
RegularExpression classes.
I attached a proof-of-concept which tests a good and bad heystack
string to a regex pattern with Poco, Boost and PCRE. I tested it on
two different machines with the following output:
Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013
i686 i686 i686 GNU/Linux
Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? no --> NOT CORRECT
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes --> NOT CORRECT
Ubuntu 12.04.3 LTS 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes --> OK
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.12 2011-01-15
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no --> OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I see the messages (starting with "Could not find key with description") on a fresh install of Linux Mint 19 Cinnamon. Second line of kern.log says: "Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797678] Re: Printing stops with Status as "Idle - Filter failed"
I forgot to say that the printer is a networked Samsung SCX-4729FD. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1797678 Title: Printing stops with Status as "Idle - Filter failed" Status in cups package in Ubuntu: New Bug description: This happened after an upgrade from Xenial to Bionic on this Barebones PC. Interestingly after an upgrade from Xenial to Bionic on a Laptop this problem did not occur. It also occurred with a clean install on another Barebones PC, but was fixed by installing package hplip. I've tried installing hplip on this PC but to no effect. PS I don't know if the problem is with CUPS or hplip or another package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 13 09:10:56 2018 InstallationDate: Installed on 2018-02-09 (245 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Deskjet_2540_series_527711_: ipp://HPD0BF9C527711.local:631/ipp/print device for HP-Deskjet-2540-series: dnssd://Deskjet%202540%20series%20%5B527711%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9c527711 device for Samsung-SCX-472x: socket://192.168.101.20:9100 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_2540_series_527711_.ppd', '/etc/cups/ppd/Samsung-SCX-472x.ppd', '/etc/cups/ppd/HP-Deskjet-2540-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_2540_series_527711_.ppd: Permission denied grep: /etc/cups/ppd/Samsung-SCX-472x.ppd: Permission denied grep: /etc/cups/ppd/HP-Deskjet-2540-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=f83725aa-582a-4c36-9ad8-738122da2e0c ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-07 (5 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797678/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797678] [NEW] Printing stops with Status as "Idle - Filter failed"
Public bug reported: This happened after an upgrade from Xenial to Bionic on this Barebones PC. Interestingly after an upgrade from Xenial to Bionic on a Laptop this problem did not occur. It also occurred with a clean install on another Barebones PC, but was fixed by installing package hplip. I've tried installing hplip on this PC but to no effect. PS I don't know if the problem is with CUPS or hplip or another package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 13 09:10:56 2018 InstallationDate: Installed on 2018-02-09 (245 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Deskjet_2540_series_527711_: ipp://HPD0BF9C527711.local:631/ipp/print device for HP-Deskjet-2540-series: dnssd://Deskjet%202540%20series%20%5B527711%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9c527711 device for Samsung-SCX-472x: socket://192.168.101.20:9100 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_2540_series_527711_.ppd', '/etc/cups/ppd/Samsung-SCX-472x.ppd', '/etc/cups/ppd/HP-Deskjet-2540-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_2540_series_527711_.ppd: Permission denied grep: /etc/cups/ppd/Samsung-SCX-472x.ppd: Permission denied grep: /etc/cups/ppd/HP-Deskjet-2540-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=f83725aa-582a-4c36-9ad8-738122da2e0c ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-07 (5 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1797678 Title: Printing stops with Status as "Idle - Filter failed" Status in cups package in Ubuntu: New Bug description: This happened after an upgrade from Xenial to Bionic on this Barebones PC. Interestingly after an upgrade from Xenial to Bionic on a Laptop this problem did not occur. It also occurred with a clean install on another Barebones PC, but was fixed by installing package hplip. I've tried installing hplip on this PC but to no effect. PS I don't know if the problem is with CUPS or hplip or another package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 13 09:10:56 2018 InstallationDate: Installed on 2018-02-09 (245 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Deskjet_2540_series_527711_: ipp://HPD0BF9C527711.local:631/ipp/print device for HP-Deskjet-2540-series: dnssd://Deskjet%202540%20series%20%5B527711%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9c527711 device for Samsung-SCX-472x: socket://192.168.101.20:9100 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_2540_series_527711_.ppd', '/etc/cups/ppd/Samsung-SCX-472x.ppd', '/etc/cups/ppd/HP-Deskjet-2540-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_2540_series_527711_.ppd: Permission denied grep: /etc/cups/ppd/Samsung-SCX-472x.ppd: Permission denied grep: /etc/cups/ppd/HP-Deskjet-2540-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=f83725aa-582a-4c36-9ad8-738122da2e0c ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-07 (5 days ago) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797678/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
One AskUbuntu user got error a about sandboxing and _apt user (see https://askubuntu.com/q/1082648/66509 ): "Download is performed unsandboxed as root as file '/home/jim/Downloads/rainlendar2-lite_2.14.2.b157-1_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)" see full output below: jim@jim-Z1-7623:~/Downloads$ sudo apt-get install ./rainlendar2-lite_2.14.2.b157-1_amd64.deb [sudo] password for jim: Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'rainlendar2-lite' instead of './rainlendar2-lite_2.14.2.b157-1_amd64.deb' The following NEW packages will be installed: rainlendar2-lite 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 0 B/17.9 MB of archives. After this operation, 20.5 MB of additional disk space will be used. Get:1 /home/jim/Downloads/rainlendar2-lite_2.14.2.b157-1_amd64.deb rainlendar2-lite amd64 2.14.2.b157-1 [17.9 MB] Selecting previously unselected package rainlendar2-lite. (Reading database ... 180109 files and directories currently installed.) Preparing to unpack .../rainlendar2-lite_2.14.2.b157-1_amd64.deb ... Unpacking rainlendar2-lite (2.14.2.b157-1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ... Setting up rainlendar2-lite (2.14.2.b157-1) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ... N: Download is performed unsandboxed as root as file '/home/jim/Downloads/rainlendar2-lite_2.14.2.b157-1_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
