[Touch-packages] [Bug 1900253] Re: No Sound on ASUS ZenBook UX463FL_Q427FL
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1900253 Title: No Sound on ASUS ZenBook UX463FL_Q427FL Status in alsa-driver package in Ubuntu: Expired Bug description: This seems related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 : - same soundcard (Realtek ALC294). - Ubuntu 20.04 (kernel - 5.4.0-51-generic #56-Ubuntu SMP) - Internal speakers work - Jack (heaphones, external speakers) do not (cracking sound apparently correlated with laptop activity) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1900253/+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 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all
Sorry, forgot to add aslainfo. ** Attachment added: "alsainfo.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+attachment/5444389/+files/alsainfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903896 Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound was working just fine. I didn't work with my laptop for about half an hour and I didn't change anything that I can think of. But suddenly, there were no sounds anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 21:20:12 2020 InstallationDate: Installed on 2020-10-14 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP410UF.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP410UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook Flip 14 TP410UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+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 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all
Exactly the same problem. Since update yesterday. Asus Vivobook Flip 14 TP420IA. Realtek ALC256. Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-33-generic OS Type: 64-bit Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15,1 GiB of RAM Graphics Processor: AMD RENOIR ** Attachment added: "apt_history.log" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+attachment/5444388/+files/apt_history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903896 Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound was working just fine. I didn't work with my laptop for about half an hour and I didn't change anything that I can think of. But suddenly, there were no sounds anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 21:20:12 2020 InstallationDate: Installed on 2020-10-14 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP410UF.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP410UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook Flip 14 TP410UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+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 1903896] Re: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903896 Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound was working just fine. I didn't work with my laptop for about half an hour and I didn't change anything that I can think of. But suddenly, there were no sounds anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 21:20:12 2020 InstallationDate: Installed on 2020-10-14 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP410UF.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP410UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook Flip 14 TP410UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+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 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
May I know when will it be in proposed? should I invite someone to review? thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1908473] [NEW] rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak
Public bug reported:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks file
descriptors due to a bug where it does not correctly close sockets, and
instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually close
all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets will
be in FIN-WAIT-2.
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and depends
on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a configuration file to enable imrelp.
The changes to rsyslog implement a testcase which exercises the
problematic code to ensure things are working as expected, and should
run during autopkgtest time.
[Other]
Upstream bug list:
https://github.com/rsyslog/rsyslog/issues/4350
https://github.com/rsyslog/rsyslog/issues/4005
https://github.com/rsyslog/librelp/issues/188
The following commits fix the problem:
rsyslogd
commit baee0bd5420649329793746f0daf87c4f59fe6a6
Author: Andre lorbach
Date: Thu Apr 9 13:00:35 2020 +0200
Subject: testbench: Add test for imrelp to check broken session handling.
Link:
https://github.com/rsyslog/rsyslog/commit/baee0bd5420649329793746f0daf87c4f59fe6a6
librelp
===
commit 7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
Author: Andre lorbach
Date: Mon May 11 14:59:55 2020 +0200
Subject: fix memory leak on session break.
Link:
https://github.com/rsyslog/librelp/commit/7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
commit 4a6ad8637c244fd3a1caeb9a93950826f58e956a
Author: Andre lorbach
Date: Wed Apr 8 15:55:32 2020 +0200
Subject: replsess: fix double free of sendbuf in some cases.
Link:
https://github.com/rsyslog/librelp/commit/4a6ad8637c244fd3a1caeb9a93950826f58e956a
** Affects: librelp (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: rsyslog (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: librelp (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: rsyslog (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: librelp (Ubuntu Groovy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: rsyslog (Ubuntu Groovy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: librelp (Ubuntu Hirsute)
Importance: Medium
Assignee:
[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie
This bug was fixed in the package binutils - 2.35.50.20201210-0ubuntu2 --- binutils (2.35.50.20201210-0ubuntu2) hirsute; urgency=medium * Revert linker options parsing patch. LP: #1907789. -- Matthias Klose Fri, 11 Dec 2020 11:29:47 +0100 ** Changed in: binutils (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Oops. It appears this was fixed in gdm3 in 2017. If you have any more problems then please open new bugs. ** Tags added: a2dp ** No longer affects: gdm3 (Ubuntu Zesty) ** No longer affects: pulseaudio (Ubuntu Zesty) ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #323 https://gitlab.gnome.org/GNOME/gdm/-/issues/323 ** Changed in: gdm Importance: Medium => Unknown ** Changed in: gdm Status: Expired => Unknown ** Changed in: gdm Remote watch: GNOME Bug Tracker #784856 => gitlab.gnome.org/GNOME/gdm/-/issues #323 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/340 ** Changed in: pulseaudio Importance: Medium => Unknown ** Changed in: pulseaudio Remote watch: freedesktop.org Bugzilla #57167 => gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340 ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** No longer affects: bluez (Ubuntu Xenial) ** No longer affects: gdm3 (Ubuntu Xenial) ** No longer affects: pulseaudio (Ubuntu Xenial) ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** No longer affects: bluez (Ubuntu) ** No longer affects: pulseaudio (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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Unknown Status in PulseAudio: Unknown Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+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 1772941] Re: isc-dhcp-server does not listen network interfaces
I think i have the same issue. Ubuntu 18.04.5 i386 with two NIC and configured in order to listen and serve lease on a specific NIC. After the boot procedure, the service fail. If i make a restart without changing anything it's work. ** Attachment added: "status-restart.txt" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1772941/+attachment/5444319/+files/status-restart.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1772941 Title: isc-dhcp-server does not listen network interfaces Status in isc-dhcp package in Ubuntu: Confirmed Bug description: System: Ubuntu 16.04.4 LTS x64 XFCE desktop Version of package: isc-dhcp-server Uname: 4.4.0-127-generic Result spected: service isc-dhcp-server status returning that service is active, running and OK. Network interfaces: 2, enp0s3 (static, main), en0s8 not configured yet. Current result: service isc-dhcp-server status returns an error message, which says that there is no network interface listening. In /etc/default/isc-dhcp-server I have configured this line: INTERFACES="enp0s3" but still giving the same error. Links to an ask ubuntu question:https://askubuntu.com/questions/536531/dhcp-server-wont-start-gives-not-configured-to-listen-on-any-interfaces-eve To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1772941/+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 1908438] [NEW] When specifying wrong syntax in sudoers.d include files sudo throws a segmentation fault
Public bug reported: I made a mistake and used a relative rather than absolute path to the application: The following file placed in the /etc/sudoers.d causes a segmentation fault in when and sudo command is run. /etc/sudoers.d/reset_database #Allows reset_database to be called as user jacobus jacobus ALL=NOPASSWD: systemctl stop freeradius jacobus ALL=NOPASSWD: systemctl start freeradius jacobus ALL=NOPASSWD: systemctl restart postgresql ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: sudo 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 22:19:05 2020 InstallationDate: Installed on 2019-06-04 (561 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: sudo UpgradeStatus: Upgraded to groovy on 2020-10-25 (52 days ago) VisudoCheck: Error: command ['pkexec', '/usr/sbin/visudo', '-c'] failed with exit code 1: /etc/sudoers.d/reset_database: bad permissions, should be mode 0440 /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK /etc/sudoers.d/cephadm: parsed OK /etc/sudoers.d/openfortigui: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1908438 Title: When specifying wrong syntax in sudoers.d include files sudo throws a segmentation fault Status in sudo package in Ubuntu: New Bug description: I made a mistake and used a relative rather than absolute path to the application: The following file placed in the /etc/sudoers.d causes a segmentation fault in when and sudo command is run. /etc/sudoers.d/reset_database #Allows reset_database to be called as user jacobus jacobus ALL=NOPASSWD: systemctl stop freeradius jacobus ALL=NOPASSWD: systemctl start freeradius jacobus ALL=NOPASSWD: systemctl restart postgresql ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: sudo 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 22:19:05 2020 InstallationDate: Installed on 2019-06-04 (561 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: sudo UpgradeStatus: Upgraded to groovy on 2020-10-25 (52 days ago) VisudoCheck: Error: command ['pkexec', '/usr/sbin/visudo', '-c'] failed with exit code 1: /etc/sudoers.d/reset_database: bad permissions, should be mode 0440 /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK /etc/sudoers.d/cephadm: parsed OK /etc/sudoers.d/openfortigui: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1908438/+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 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression
The proposed solution fixes the bug I filed when joining against older Windows Active Directory servers. (https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673) i.e. The domain join works without the --use-ldaps. We do not currently have the correct certificate set up to use --use- ldaps, so I am not currently able exercise that test case. (Thank you to the Ubuntu team for the rapid response.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in adcli source package in Bionic: Fix Committed Status in cyrus-sasl2 source package in Bionic: Fix Committed Bug description: [Impact] A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a regression for some users when attempting to join a Active Directory realm. adcli introduced a default behaviour change, moving from GSS- API to GSS-SPNEGO as the default channel encryption algorithm. adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi- mit, a part of cyrus-sasl2. The implementation seems to have some compatibility issues with particular configurations of Active Directory on recent Windows Server systems. Particularly, adcli sends a ldap query to the domain controller, which responds with a tcp ack, but never returns a ldap response. The connection just hangs at this point and no more traffic is sent. You can see it on the packet trace below: https://paste.ubuntu.com/p/WRnnRMGBPm/ On Focal, where the implementation of GSS-SPNEGO is working, we see a full exchange, and adcli works as expected: https://paste.ubuntu.com/p/8668pJrr2m/ The fix is to not assume use of confidentiality and integrity modes, and instead use the flags negotiated by GSS-API during the initial handshake, as required by Microsoft's implementation. [Testcase] You will need to set up a Windows Server 2019 system, install and configure Active Directory and enable LDAP extensions and configure LDAPS and import the AD SSL certificate to the Ubuntu client. Create some users in Active Directory. On the Ubuntu client, set up /etc/hosts with the hostname of the Windows Server machine, if your system isn't configured for AD DNS. From there, install adcli 0.8.2-1 from -release. $ sudo apt install adcli Set up a packet trace with tcpdump: $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)' Next, join the AD realm using the normal GSS-API: # adcli join --verbose -U Administrator --domain WIN- SB6JAS7PH22.testing.local --domain-controller WIN- SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL You will be prompted for Administrator's passowrd. The output should look like the below: https://paste.ubuntu.com/p/NWHGQn746D/ Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the regression. Repeat the above steps. Now you should see the connection hang. https://paste.ubuntu.com/p/WRnnRMGBPm/ Finally, install the fixed cyrus-sasl2 package from -proposed https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test $ sudo apt-get update $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db libsasl2-modules-gssapi-mit Repeat the steps. GSS-SPNEGO should be working as intended, and you should get output like below: https://paste.ubuntu.com/p/W5cJNGvCsx/ [Where problems could occur] Since we are changing the implementation of GSS-SPNEGO, and cyrus- sasl2 is the library which provides it, we can potentially break any package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO. $ apt rdepends libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-mit Reverse Depends: |Suggests: ldap-utils Depends: adcli Conflicts: libsasl2-modules-gssapi-heimdal |Suggests: libsasl2-modules Conflicts: libsasl2-modules-gssapi-heimdal |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules |Suggests: ldap-utils |Depends: msktutil Conflicts: libsasl2-modules-gssapi-heimdal |Depends: libapache2-mod-webauthldap Depends: freeipa-server Depends: freeipa-client Depends: adcli Depends: 389-ds-base |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules While this SRU makes cyrus-sasl2 work with Microsoft implementations of GSS-SPNEGO, which will be the more common usecase, it may change the behaviour when connecting to a MIT krb5 server with the GSS- SPNEGO protocol, as krb5 assumes use of confidentiality and integrity modes. This shouldn't be a problem as the krb5 implementation signals its intentions by setting the correct flags
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
You'll be able to install the driver after having rebooted and upgraded the distribution. You don't have to (and can't atm) do it _during_ install. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture:
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Hello, I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 bluetooth speaker. I had in logs : `src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:DF:15:7F:ED:AA: Protocol not available` I found a workaround here https://askubuntu.com/questions/1172000/a2dp-sink-profile-connect-failed ``` $ pactl load-module module-bluetooth-policy $ pactl load-module module-bluetooth-discover ``` I did not understand why these commands were mandatory as I already have them in `/etc/pulse/default.pa` Then I checked my `~/.config/pulse/default.pa` and found this : ``` #!/usr/bin/pulseaudio -nF # # Work around for PA not allowing access to A2DP profiles in the user session # because GDM already has it open. # LP: #1703415 # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif ``` So here, we are : today, with - Ubuntu 20.10 - Pulseaudio 1:13.99.2-1ubuntu2.1 - BlueZ 5.55-0ubuntu1.1 => I do not reproduce the original bug. => Moreover, the now unnecessary workaround in `~/.config/pulse/default.pa` is preventing normal use for bluetooth devices. **Workaround for the workaround** : comment the lines in `~/.config/pulse/default.pa` ``` #!/usr/bin/pulseaudio -nF # # Work around for PA not allowing access to A2DP profiles in the user session # because GDM already has it open. # LP: #1703415 # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware #.ifexists module-bluetooth-policy.so # unload-module module-bluetooth-policy #.endif # #.ifexists module-bluetooth-discover.so # unload-module module-bluetooth-discover #.endif ``` -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Expired Status in PulseAudio: Unknown Status in gdm3 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 source package in Xenial: Triaged Status in pulseaudio source package in Xenial: Triaged Status in gdm3 source package in Zesty: Triaged Status in pulseaudio source package in Zesty: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+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 1888726] Re: systemd-udevd regression: some renamed network interfaces stuck in "pending" state
** Merge proposal linked: https://code.launchpad.net/~oddbloke/curtin/+git/curtin/+merge/395436 -- 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/1888726 Title: systemd-udevd regression: some renamed network interfaces stuck in "pending" state Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Invalid Bug description: Summary: In Ubuntu Server 20.04 LTS and newer, using netplan.io and systemd- networkd, in certain network configurations, renamed network interfaces get stuck in "pending" state and are not configured properly. On boot, system is stuck on "Wait for Network to be Configured" for 2 minutes. How to reproduce: 1. Configure a machine (for example, a virtual machine) with two Ethernet network cards. Make note of MAC addresses of these network cards. 2. Set up netplan with a single configuration file, contents are in the attached "00-static.yaml" file. Replace the MAC addresses to match your setup. IP address configuration is omitted and is not necessary to reproduce the bug. 3. Reboot the system. Expected outcome: 1. System boots in a reasonable time 2. First network interface (wan) is brought up, is not renamed, and is marked as configured by networkd 3. Second network interface (lan) is brought up, renamed, configured for MTU=9000, and is marked as configured by networkd 4. VLAN interface (vlan20) is brought up, renamed, configured for MTU=9000, and is marked as configured by networkd Actual outcome: 1. System boot is delayed by 2 minutes 2. First network interface (wan) is configured as expected 3. Second network interface (lan) is configured as expected 4. VLAN interface (vlan20) seems to be configured as expected, but is stuck in "pending" state according to networkctl list Test environment: Hardware: Virtual machine with the following configuration * 4 amd64 CPU cores (also tested with a single core) * 1 GB RAM * 8 GB disk * 2 network cards (vmxnet3 in VMware, virtio in Parallels) Working as expected: * [1] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 0.99-0ubuntu3~19.10.2, systemd+udev 242-7ubuntu3.11 Broken: * [2] Ubuntu Server 19.10, kernel 5.3.0-62, netplan.io 0.99-0ubuntu3~19.10.2, systemd 242-7ubuntu3.11, udev 245.4-4ubuntu3.1 * [3] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev 245.4-4ubuntu3.1 * [4] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git e9769453 * [5] Ubuntu Server 20.04 LTS, kernel 5.4.0-42, netplan.io 0.99-0ubuntu3~20.04.2, systemd+udev vanilla upstream git v242 * [6] Ubuntu Server 20.10 daily-live, kernel 5.4.0-26, netplan.io 0.99-0ubuntu5, systemd+udev 245.6-3ubuntu3 [2] As noted above, issue was reproduced in 19.10 by upgrading ONLY udev and libudev1 to ones shipped in focal-updates. [4] It was also reproduced in vanilla upstream systemd, git master commit e9769453. Just installed on top of existing systemd using "sudo ninja -C build install". [5] Interestingly enough, issue also seems to exist in vanilla v242. Either that, or the installation didn't replace the packaged systemd properly. This may hint at some distribution-specific patch that got removed before 20.04. This issue was reproduced in VMware ESXi 6.7U3, VMware Fusion 11.5.5 and Parallels Desktop 15.1.4. This leads me to believe that network card drivers or virtualisation engines do not play part in the issue. Extra observations: To make the example configuration (00-static.yaml) not get stuck in "pending" state, any one of the following options helps: * Remove "set-name" parameter for "lan" interface * Remove "mtu" parameter for "lan" interface * Remove "wan" interface entirely I got some data/logs for each of these scenarios for eoan [1] and focal [3], as well as the original broken config, and put them together in the attached "parallels.tar.gz". Note about Apport: Attached apport report was generated for test environment [2] above. Attachments: * 00-static.yaml: minimalistic broken netplan configuration example * parallels.tar.gz: various logs for eoan [1] and focal [3], as described in "Extra observations" above ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules Date: Thu Jul 23 18:54:58 2020 InstallationDate: Installed on 2020-07-22 (1 days ago) InstallationMedia: Ubuntu-Server
[Touch-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
alsa-lib 1.2.2-2.1ubuntu2.3 is now in the focal queue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1908023] Re: Installing libgbm1 will make other packages removed
** No longer affects: hwe-next ** No longer affects: mesa (Ubuntu) ** Summary changed: - Installing libgbm1 will make other packages removed + installation stopped by an exception from mark_install() in Cache class of python3-apt ** Description changed: - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 20.04/20.04.1 + Exception in the installation - 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - libgbm1/20.0.4-2ubuntu1 libgbm1/20.0.8-0ubuntu1~20.04.1 + Aug 12 19:26:59 ubuntu /plugininstall.py: Exception during installation: + Aug 12 19:26:59 ubuntu /plugininstall.py: Traceback (most recent call last): + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 235, in run + Aug 12 19:26:59 ubuntu /plugininstall.py: self.install_extras() + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1212, in install_extras + Aug 12 19:26:59 ubuntu /plugininstall.py: self.do_install(filtered_extra_packages) + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 941, in do_install + Aug 12 19:26:59 ubuntu /plugininstall.py: mark_install(cache, pkg) + Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 553, in mark_install + Aug 12 19:26:59 ubuntu /plugininstall.py: raise InstallStepError( + Aug 12 19:26:59 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Unable to install 'libgbm1' due to conflicts. - 3) What you expected to happen - Not so many packages will be removed when executing `apt-get --yes install libgbm1`. + This happen in oem project because we have lots pkg to upgrade during + installation because the design of factory process need it. - 4) What happened instead - Executing `apt-get --yes install libgbm1` will make many other packages to be removed. + As package list have certain dependency, and the the order that we get + the pkg from the python set object is not good for underlying apt + engine, then exception will raise. ** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908023 Title: installation stopped by an exception from mark_install() in Cache class of python3-apt Status in OEM Priority Project: In Progress Bug description: Exception in the installation Aug 12 19:26:59 ubuntu /plugininstall.py: Exception during installation: Aug 12 19:26:59 ubuntu /plugininstall.py: Traceback (most recent call last): Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 235, in run Aug 12 19:26:59 ubuntu /plugininstall.py: self.install_extras() Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1212, in install_extras Aug 12 19:26:59 ubuntu /plugininstall.py: self.do_install(filtered_extra_packages) Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 941, in do_install Aug 12 19:26:59 ubuntu /plugininstall.py: mark_install(cache, pkg) Aug 12 19:26:59 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 553, in mark_install Aug 12 19:26:59 ubuntu /plugininstall.py: raise InstallStepError( Aug 12 19:26:59 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Unable to install 'libgbm1' due to conflicts. This happen in oem project because we have lots pkg to upgrade during installation because the design of factory process need it. As package list have certain dependency, and the the order that we get the pkg from the python set object is not good for underlying apt engine, then exception will raise. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908023/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Your comment is not helpful. Not checking the box would not install nVidia drivers and your suggestion is not a valid workaround. ** Changed in: apt (Ubuntu Focal) Importance: Medium => High ** Changed in: apt (Ubuntu Focal) Milestone: None => ubuntu-20.04.2 -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
The first chance to fix it was in August, the next chance to fix it is in February. There's really no urgency here. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
There is an easy workaround, too: just don't check the box to install third party drivers. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Bionic) Status: New => Confirmed -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: apt (Ubuntu Groovy) Status: Fix Released => Triaged ** Changed in: apt (Ubuntu Focal) Status: Fix Released => Triaged ** Changed in: apt (Ubuntu Bionic) Status: Fix Released => Confirmed ** Changed in: apt (Ubuntu Bionic) Status: Confirmed => New -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname:
[Touch-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers
So, from #21 I'm on 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
So 9 months almost after reporting this bug it is still happening on install. I expected better from Ubuntu that this, makes your entire 20.04 OS not worth even downloading if for this long you let a MAJOR flaw like this continue. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64
[Touch-packages] [Bug 1908334] Re: Printer managed wrongly in Settings -> Printers
Cups shows only one of them (attachment3) ** Attachment added: "Screenshot from 2020-12-16 13-31-45.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444207/+files/Screenshot%20from%202020-12-16%2013-31-45.png -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Re: Printer managed wrongly in Settings -> Printers
(attachment2) ** Attachment added: "Screenshot from 2020-12-16 13-29-53.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444205/+files/Screenshot%20from%202020-12-16%2013-29-53.png -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Re: Printer managed wrongly in Settings -> Printers
I switched to the latest kernel now. After removing all printers, the one described in paragraph one of #1 keeps getting re-detected. (attachment 1) Applications show two of them, where the first is "gathering information" and cannot print. (attachment2 in the following post) ** Attachment added: "Screenshot from 2020-12-16 13-28-53.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444204/+files/Screenshot%20from%202020-12-16%2013-28-53.png -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908051] Re: error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Steps to reproduce:
1. download and extract
https://launchpad.net/ubuntu/+archive/primary/+files/libunity_7.1.4+19.04.20190319.orig.tar.gz
2. get and apply patch
https://launchpadlibrarian.net/443817430/0001-Fix-FTB-with-recent-vala-requiring-non-public-abstra.patch
3. run NOCONFIGURE=1 ./autogen.sh
4. run ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--disable-static
5. run make
Expected output:
libunity is compiled successfully
Actual output:
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert from
`void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string,
GLib.Variant)'
..
..
unity-sound-menu-mpris.vala:408.5-408.56: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnablePlayerSpecificItems (ObjectPath
object_path, string desktop_id) throws IOError;
Compilation failed: 1 error(s), 22 warning(s)
make[2]: *** [Makefile:1391: libunity_la_vala.stamp] Error 1
Other information
Arch Linux 64bit, current
vala 0.50.2-1
gobject-introspection 1.66.1-3
gnome-common 3.18.0-4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1908051
Title:
error: Argument 7: Cannot convert from `void
Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Status in libunity package in Ubuntu:
Incomplete
Bug description:
make returns:
unity-protocol.vapi:242.4-242.43: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint
view_type) throws GLib.IOError;
unity-launcher.vala:61.5-61.42: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public HashTable query ()
^^
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert
from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string,
GLib.Variant)'
DBusSignalFlags.NONE, this.owner_changed);
^^
unity-scope-channel.vala:269.9-269.52: warning: Access to possible `null'.
Perform a check or use an unsafe cast.
(transfer_model as DiffModel).commit_changes ();
unity-synchronizer.vala:93.5-93.18: warning: `GLib.HashTable.add' has been
deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:434.7-434.28: warning:
`GLib.HashTable.add' has been deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:606.7-606.72: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByField).map_subscope_categories
(scope_id, proxy.categories_model);
^^
unity-aggregator-scope-private.vala:1308.7-1308.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
scope_id);
unity-aggregator-scope-private.vala:1352.7-1352.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
master_scope_id);
unity-scope-loader.vala:41.49-41.69: warning: `GLib.ModuleFlags.BIND_LAZY'
has been deprecated since vala-0.46. Use LAZY
unity-sound-menu-mpris.vala:475.5-475.27: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void raise() throws IOError{
^^^
unity-sound-menu-mpris.vala:580.5-580.32: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void play_pause() throws IOError
unity-sound-menu-mpris.vala:585.5-585.26: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void next() throws IOError
^^
unity-sound-menu-mpris.vala:590.5-590.30: warning: DBus methods are
recommended to throw at least `GLib.Error' or
[Touch-packages] [Bug 1908334] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444193/+files/ProcModules.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444194/+files/UdevDb.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444195/+files/acpidump.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444192/+files/ProcInterrupts.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444190/+files/ProcCpuinfoMinimal.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444189/+files/ProcCpuinfo.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444191/+files/ProcEnviron.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] PrintingPackages.txt
apport information ** Attachment added: "PrintingPackages.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444188/+files/PrintingPackages.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444187/+files/Lsusb-v.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444186/+files/Lsusb-t.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444185/+files/Lsusb.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444184/+files/Lspci-vt.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444183/+files/Lspci.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444181/+files/KernLog.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444182/+files/Locale.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444180/+files/Dependencies.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Re: Printer managed wrongly in Settings -> Printers
apport information ** Tags added: apport-collected focal ** Description changed: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-11-16 (395 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ + MachineType: HP OMEN by HP Laptop 17-cb0xxx + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-control-center + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 + Tags: focal + Uname: Linux 5.4.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/05/2019 + dmi.bios.vendor: AMI + dmi.bios.version: F.16 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 8603 + dmi.board.vendor: HP + dmi.board.version: 45.38 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP OMEN + dmi.product.name: OMEN by HP Laptop 17-cb0xxx + dmi.product.sku: 7NG00EA#BED + dmi.sys.vendor: HP ** Attachment added: "CupsErrorLog.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444178/+files/CupsErrorLog.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually
[Touch-packages] [Bug 1908334] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1908334/+attachment/5444179/+files/CurrentDmesg.txt -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Re: Printer managed wrongly in Settings -> Printers
(add missing screenshot) Now I don't think this CUPS-BRF-Printer is related as it is shown even if my printer is turned off. ** Package changed: ubuntu => cups (Ubuntu) ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-12-16 12-11-41.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908334/+attachment/5444176/+files/Screenshot%20from%202020-12-16%2012-11-41.png -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] [NEW] Printer managed wrongly in Settings -> Printers
You have been subscribed to a public bug: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment printer -- Printer managed wrongly in Settings -> Printers https://bugs.launchpad.net/bugs/1908334 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- 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 1889166] Re: mir: build failure on s390x
In src/miral/CMakeLists.txt Change: set_source_files_properties(xcursor.c PROPERTIES COMPILE_DEFINITIONS _GNU_SOURCE) to set_source_files_properties(xcursor.c PROPERTIES COMPILE_DEFINITIONS _GNU_SOURCE COMPILE_FLAGS "-Wno-error=stringop-truncation" ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: apt (Ubuntu Focal) Status: Triaged => Fix Released ** Changed in: apt (Ubuntu Groovy) Status: Triaged => Fix Released ** Changed in: apt (Ubuntu Bionic) Status: Confirmed => Fix Released -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules:
[Touch-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
@seb128 Hello, I reupload the debdiff for focal based on the latest alsa-lib version. Please help to upload to queue. version is 1.2.2-2.1ubuntu2.3.debdiff. Thanks, ** Patch added: "alsa-lib_1.2.2-2.1ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1899857/+attachment/5444146/+files/alsa-lib_1.2.2-2.1ubuntu2.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2
** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1908259 Title: TEST-36-NUMAPOLICY fails with qemu 5.2 Status in systemd: Unknown Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Bug description: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) E: QEMU failed with exit code 1 Isolated this to a test without systemd: $ apt install linux-image-generic qemu-system-x86 $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' Upgrading to 5.2 makes this: $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) The numa spec is indeed a bit short -numa node,nodeid=0 If I change this to -numa node,mem=512M,nodeid=0 It would work, but that kind of specification is forbidden >=5.1 Parameter -numa node,mem is not supported by this machine type Use -numa node,memdev instead You'd need also something like -M pc-i440fx-5.0 which isn't anything the test wants to set in stone I guess. Instead using memdev works: -object memory-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0 This works fine and is in qemu since quite some time. Properly documented since 2.12 but actually available since 2.1 (2014) The argument for this test is in test/TEST-36-NUMAPOLICY/test.sh QEMU_OPTIONS="-numa node,nodeid=0" Fixing that to a new form should help. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1908259/+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 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions
** Changed in: auto-package-testing Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored by curl in Bionic and earlier versions Status in Auto Package Testing: Fix Released Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: alvaro (alvariturituro) => (unassigned) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => alvaro (alvariturituro) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020
