[Touch-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
>From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached?field.comment=From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+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 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
>From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached?field.comment=From syslog: "Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this name or index. Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize daemon due to errors while executing startup commands. Source of commands: /home/jarnos/.config/pulse//default.pa Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Failed with result 'exit-code'. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Failed to start Sound Service. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Reached target Main User Target. Jul 25 00:07:01 jarnos-OptiPlex-9010 systemd[1569]: Startup finished in 220ms. Jul 25 00:07:02 jarnos-OptiPlex-9010 systemd[1569]: pulseaudio.service: Scheduled restart job, restart counter is at 1." default.pa attached ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513624/+files/default.pa -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+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 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Description changed: - First pulseaudio fails for some reason. + First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the + volume control in Xfce panel shows mute after I start session, but I can + not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- 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/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+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 1937988] Re: The image is distrorted while use iGPU rendering and output via AMD GPU
the fix commit not upstream to mesa yet, after it lands to upstream, we can backport the commit in to Ubuntu and start SRU process. I tried backport the commit to Focal's mesa, it works. -- 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/1937988 Title: The image is distrorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+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 1937988] [NEW] The image is distrorted while use iGPU rendering and output via AMD GPU
Public bug reported: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 ** Affects: oem-priority Importance: Critical Assignee: Shengyao Xue (xueshengyao) Status: In Progress ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1904984 originate-from-1917700 originate-from-1931050 somerville sutton ** Tags added: oem-priority originate-from-1931050 sutton ** Tags added: originate-from-1917700 ** Tags added: originate-from-1904984 somerville ** Changed in: oem-priority Assignee: (unassigned) => Shengyao Xue (xueshengyao) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => 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/1937988 Title: The image is distrorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+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 1934995] Re: Broken on ppc64el (toolchain bug?)
Indeed the open(2) manpage is misleading in that regard. The actual definition in fcntl.h is like this: extern int open (const char *__file, int __oflag, ...) __nonnull ((1)); (with a few variants, but they all use varargs). So I did the same in umockdev for full header compatibility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) Status in umockdev package in Ubuntu: New Bug description: umockdev appears to be broken on ppc64el in impish. Running it on one of Mir's umockdev-using tests results in: (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/ MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/ LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin *** stack smashing detected ***: terminated umockdev-run: unable to propagate signal 6 to child 15833: No such process (You can also see this in the Mir 2.4.1-0ubuntu1 build log: https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish- ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz ) Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute results in those tests passing. Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild environment results in packages that do *not* pass those tests, suggesting a toolchain change might be responsible. Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and vala 0.48.12-1 in Impish and none of these appear to work. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: umockdev 0.16.1-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 16:04:15 2021 InstallationDate: Installed on 2021-06-26 (11 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: umockdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1934995] Re: Broken on ppc64el (toolchain bug?)
So I don't have the faintest idea what caused this to start failing but the issue here is in mir: int (*real_open)(char const *path, int flags, mode_t mode); *(void **)(_open) = dlsym(RTLD_NEXT, "open"); return (*real_open)(path, flags, mode); The declaration for real_open here does not match that used by the open() function call in umockdev, which uses va_args. This means that the stack frame gcc creates for mir's wrapper does not have space for a parameter save area which the code gcc generates for umockdev assumes it has, and so the stack gets stomped on. So if the prototype in mir is fixed here (also the one for open64) I bet things will start working again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) Status in umockdev package in Ubuntu: New Bug description: umockdev appears to be broken on ppc64el in impish. Running it on one of Mir's umockdev-using tests results in: (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/ MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/ LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin *** stack smashing detected ***: terminated umockdev-run: unable to propagate signal 6 to child 15833: No such process (You can also see this in the Mir 2.4.1-0ubuntu1 build log: https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish- ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz ) Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute results in those tests passing. Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild environment results in packages that do *not* pass those tests, suggesting a toolchain change might be responsible. Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and vala 0.48.12-1 in Impish and none of these appear to work. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: umockdev 0.16.1-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 16:04:15 2021 InstallationDate: Installed on 2021-06-26 (11 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: umockdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot
[Expired for procps (Ubuntu) because there has been no activity for 60 days.] ** Changed in: procps (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1929011 Title: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot Status in procps package in Ubuntu: Expired Bug description: Left-Alt is always operational & Right-Alt is not at any time & not specific to this report's subject category. True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso. It is natural to use Right-Alt due to a closer distance to the SysRq key. This might help explain why some say REISUB does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 00:27:12 2021 InstallationDate: Installed on 2020-07-14 (309 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1929011/+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 1937893] Re: Touchscreen Misbehaving After Upgrading to Ubuntu 21.04
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Touchscreen Misbehaving After Upgrading to Ubuntu 21.04 + [HP Pavilion x360 Convertible] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937893 Title: [HP Pavilion x360 Convertible] Touchscreen Misbehaving After Upgrading to Ubuntu 21.04 Status in linux package in Ubuntu: New Bug description: I just upgraded from Ubuntu 20.10 to 21.04. After the upgrade, the touchscreen of my laptop has started registering random touch events when no touch input is actually being given by the user. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 12:54:15 2021 DistUpgraded: 2021-07-07 09:51:26,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81a9] InstallationDate: Installed on 2020-10-10 (286 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=58c17d38-5a4a-455c-a288-fffc3bd115a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-07-07 (17 days ago) dmi.bios.date: 06/25/2018 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.53 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.53 dmi.modalias: dmi:bvnInsyde:bvrF.35:bd06/25/2018:br15.35:efr57.53:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.53:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion x360 Convertible dmi.product.sku: Z4Q51PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937893/+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 1937932] Re: Blank Screen and Unable to get into windows while opening laptop lid after Sleep.
Thanks for the bug report. Please try logging into 'Ubuntu on Xorg' as well as 'Ubuntu' and tell us if both have the same problem. Also, next time the problem occurs please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937932 Title: Blank Screen and Unable to get into windows while opening laptop lid after Sleep. Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: While opening laptop display lid open ubuntu failed to open and stuck on blank screen with error. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Jul 25 15:02:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937932/+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 1937953] Re: systemd forcibly disables use of dummy/bond interfaces
A workaround is to create an empty file /etc/modprobe.d/systemd.conf but this is too imprecise. The files that systemd uses should ideally be named specifically for their purpose so that they can be overridden without affecting any future changes in systemd, e.g. /etc/modprobe.d/systemd-dummy.conf and /etc/modprobe.d/systemd- bonding.conf -- 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/1937953 Title: systemd forcibly disables use of dummy/bond interfaces Status in systemd package in Ubuntu: New Bug description: /etc/modprobe.d/local-dummy.conf contains: options dummy numdummies=10 /etc/modules-load.d/local-dummy.conf contains: dummy /lib/modprobe.d/systemd.conf contains: options bonding max_bonds=0 options dummy numdummies=0 On boot, the "dummy" module is loaded with the options "numdummies=10 numdummies=0" because configuration in /lib/modprobe.d/ overrides configuration in /etc/modprobe.d/. This makes it impossible to automatically load the dummy module with 10 interfaces and then use them in /etc/network/interfaces.d/ because the configuration file provided with systemd overrides my module configuration by setting the number of interfaces back to 0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.50 Uname: Linux 5.4.132+ x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 19:18:14 2021 InstallationDate: Installed on 2014-05-10 (2633 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.132+ root=UUID=3d2fba1f-59b9-424f-a0df-2e7f1e2d8637 ro rootflags=subvol=@ sysrq_always_enabled panic=600 reboot=p sd_mod.stop_before_reboot=0 page_owner=on page_poison=1 debug_objects=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-11-24 (973 days ago) dmi.bios.date: 11/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.20 dmi.board.name: Z170 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd11/22/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.systemd.journald.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2018-11-24T15:04:07.599704 mtime.conffile..etc.systemd.logind.conf: 2015-07-04T15:46:37.746749 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937953/+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 1937953] [NEW] systemd forcibly disables use of dummy/bond interfaces
Public bug reported: /etc/modprobe.d/local-dummy.conf contains: options dummy numdummies=10 /etc/modules-load.d/local-dummy.conf contains: dummy /lib/modprobe.d/systemd.conf contains: options bonding max_bonds=0 options dummy numdummies=0 On boot, the "dummy" module is loaded with the options "numdummies=10 numdummies=0" because configuration in /lib/modprobe.d/ overrides configuration in /etc/modprobe.d/. This makes it impossible to automatically load the dummy module with 10 interfaces and then use them in /etc/network/interfaces.d/ because the configuration file provided with systemd overrides my module configuration by setting the number of interfaces back to 0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.50 Uname: Linux 5.4.132+ x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 19:18:14 2021 InstallationDate: Installed on 2014-05-10 (2633 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.132+ root=UUID=3d2fba1f-59b9-424f-a0df-2e7f1e2d8637 ro rootflags=subvol=@ sysrq_always_enabled panic=600 reboot=p sd_mod.stop_before_reboot=0 page_owner=on page_poison=1 debug_objects=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-11-24 (973 days ago) dmi.bios.date: 11/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.20 dmi.board.name: Z170 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd11/22/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.systemd.journald.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2018-11-24T15:04:07.599704 mtime.conffile..etc.systemd.logind.conf: 2015-07-04T15:46:37.746749 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1937953 Title: systemd forcibly disables use of dummy/bond interfaces Status in systemd package in Ubuntu: New Bug description: /etc/modprobe.d/local-dummy.conf contains: options dummy numdummies=10 /etc/modules-load.d/local-dummy.conf contains: dummy /lib/modprobe.d/systemd.conf contains: options bonding max_bonds=0 options dummy numdummies=0 On boot, the "dummy" module is loaded with the options "numdummies=10 numdummies=0" because configuration in /lib/modprobe.d/ overrides configuration in /etc/modprobe.d/. This makes it impossible to automatically load the dummy module with 10 interfaces and then use them in /etc/network/interfaces.d/ because the configuration file provided with systemd overrides my module configuration by setting the number of interfaces back to 0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.50 Uname: Linux 5.4.132+ x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 19:18:14 2021 InstallationDate: Installed on 2014-05-10 (2633 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.132+ root=UUID=3d2fba1f-59b9-424f-a0df-2e7f1e2d8637 ro rootflags=subvol=@ sysrq_always_enabled panic=600 reboot=p sd_mod.stop_before_reboot=0 page_owner=on page_poison=1 debug_objects=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-11-24 (973 days ago) dmi.bios.date: 11/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.20 dmi.board.name: Z170 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd11/22/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M.
[Touch-packages] [Bug 1937085] Re: 21.04 - Xerox printer is properly configured and install at OS but not at re-add??
** No longer affects: ubuntu-mate ** Changed in: cups (Ubuntu) Status: New => Invalid -- 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/1937085 Title: 21.04 - Xerox printer is properly configured and install at OS but not at re-add?? Status in cups package in Ubuntu: Invalid Bug description: This is kind of a follow-up to: https://bugs.launchpad.net/ubuntu- mate/+bug/1937083 and I am not sure if it needs to be opened or not hence I am opening it as a different bug. I am using a Xerox Versalink C405 printer; I have totally reinstalled UM 21.04-latest as fresh OS; My Xerox Versalink C405 printer has been working fine from LAN and from windoze machines; I have had a "hardware problem" w/ my Xerox printer in Linux and since that problem it stopped working; My solution was to readd the printer (See the bug I opened previously); The bug/problem: I am unable to reinstall Xerox Versalink C405 when adding manually. Why on Earth was the default OS able to install it w/ 0 user interaction but when I need to reinstall it manually from inside the OS it is unable to find it's driver? So what I did was: browse for a driver and look @ /opt/XeroxOffice/prtsys/ppd/XROFFSTD.ppd and have pointed to it = Xerox printer is now installed. But it says "Xerox-CommonXCPT". When I try to print, it doesn't do anything. Here is what /var/log/cups/ entries say about this: ╰─➤ cat page_log C405 dd 988 [21/Jul/2021:09:06:01 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - _xeroxofficetq1_ lp 989 [21/Jul/2021:09:06:01 -0400] total 0 - localhost PrtDrv-m6AN7m - - Xerox-CommonXCPT dd 990 [21/Jul/2021:09:23:34 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - ╭─dd@T-2033.t /var/log/cups ╰─➤ cat error_log E [21/Jul/2021:00:00:02 -0400] Unknown directive BrowseOrder on line 24 of /etc/cups/cupsd.conf. E [21/Jul/2021:00:00:02 -0400] Unknown directive BrowseAllow on line 25 of /etc/cups/cupsd.conf. E [21/Jul/2021:00:00:02 -0400] Unknown browse protocol "CUPS" ignored. E [21/Jul/2021:00:00:02 -0400] Unknown directive BrowseAddress on line 27 of /etc/cups/cupsd.conf. W [21/Jul/2021:00:00:02 -0400] No limit for Validate-Job defined in policy default and no suitable template found. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-Jobs defined in policy default - using Pause-Printer's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-My-Jobs defined in policy default - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Close-Job defined in policy default - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No JobPrivateAccess defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No JobPrivateValues defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateAccess defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateValues defined in policy default - using defaults. W [21/Jul/2021:00:00:02 -0400] No limit for Validate-Job defined in policy authenticated - using Print-Job's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-Jobs defined in policy authenticated - using Pause-Printer's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Cancel-My-Jobs defined in policy authenticated - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No limit for Close-Job defined in policy authenticated - using Send-Document's policy. W [21/Jul/2021:00:00:02 -0400] No JobPrivateAccess defined in policy authenticated - using defaults. W [21/Jul/2021:00:00:02 -0400] No JobPrivateValues defined in policy authenticated - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateAccess defined in policy authenticated - using defaults. W [21/Jul/2021:00:00:02 -0400] No SubscriptionPrivateValues defined in policy authenticated - using defaults. E [21/Jul/2021:00:00:02 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [21/Jul/2021:09:08:07 -0400] [CGI] ippfind (PID 4108744) stopped with status 1! E [21/Jul/2021:09:14:39 -0400] [CGI] ippfind (PID 4109374) stopped with status 1! E [21/Jul/2021:09:14:39 -0400] [cups-deviced] PID 4109371 (driverless) stopped with status 1! E [21/Jul/2021:09:19:09 -0400] [CGI] ippfind (PID 4109554) stopped with status 1! As a reminder, the official driver is located @ https://www.support.xerox.com/en-us/product/versalink-c405/downloads My next step will be: 1. purge installed printer; 2. rm -rf /opt/Xerox* 3. Redownload the driver @ support.xerox.com + reinstall + retest; 4. Update you with the result Thanks <3 To manage notifications about this bug go to:
[Touch-packages] [Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting
This is my contents of /etc/systemd/timesyncd.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See timesyncd.conf(5) for details. [Time] NTP=ntp.se se.pool.ntp.org FallbackNTP=ntp.ubuntu.com #RootDistanceMaxSec=5 #PollIntervalMinSec=32 #PollIntervalMaxSec=2048 And this is the outputs of some timedatectl status commands: raek@mizar:~$ timedatectl status Local time: Sun 2021-07-25 20:13:01 CEST Universal time: Sun 2021-07-25 18:13:01 UTC RTC time: Sun 2021-07-25 18:13:01 Time zone: Europe/Stockholm (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no raek@mizar:~$ timedatectl timesync-status Server: 2a01:3f7::1 (ntp.se) Poll interval: 34min 8s (min: 32s; max 34min 8s) Leap: normal Version: 4 Stratum: 1 Reference: PPS Precision: 1us (-25) Root distance: 30us (max: 5s) Offset: -104us Delay: 11.063ms Jitter: 5.968ms Packet count: 147 Frequency: +4.989ppm -- 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/1937238 Title: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: New Bug description: [impact] systemd-time-wait-sync service never completes when systemd-timesyncd package is not installed [test case] remove the systemd-timesyncd package and enable the systemd-time-wait- sync service, and reboot. Check status of the service to see it's stuck in 'activating' state, e.g.: ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago [regression potential] TBD [scope] this is needed in f and later the systemd-timesyncd package was split out from the main systemd package starting in focal, so this problem exists in f and later the service doesn't exist in b, so this is not needed there [original description] When I start my server running Ubuntu 20.04 the systemd-time-wait- sync.service is stuck in "activating" state. I noticed this because none of the systemd timer units triggered, because all the timers depend on systemd-time-wait-sync.service. Running "systemctl restart systemd-time-wait-sync.service" manually works around the problem. Some logs and command outputs: raek@mizar:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service systemd-time-wait-sync.service loaded activating start start Wait Until Kernel Time Synchronized raek@mizar:~$ systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago Docs: man:systemd-time-wait-sync.service(8) Main PID: 514 (systemd-time-wa) Tasks: 1 (limit: 9415) Memory: 972.0K CGroup: /system.slice/systemd-time-wait-sync.service └─514 /lib/systemd/systemd-time-wait-sync Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC Warning: journal has been rotated since unit was started, output may be incomplete. raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service -- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 CEST. -- Jul
[Touch-packages] [Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting
Hmm. The systemd-timesyncd package is installed and systemd- timesyncd.service is enabled. raek@mizar:~/code/raek-totp-token/firmware$ apt-cache policy systemd-timesyncd systemd-timesyncd: Installed: 245.4-4ubuntu3.11 Candidate: 245.4-4ubuntu3.11 Version table: *** 245.4-4ubuntu3.11 500 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages raek@mizar:~/code/raek-totp-token/firmware$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-07-22 11:06:53 CEST; 3 days ago Docs: man:systemd-timesyncd.service(8) Main PID: 792 (systemd-timesyn) Status: "Initial synchronization to time server [2a01:3f7::1]:123 (ntp.se)." Tasks: 2 (limit: 9415) Memory: 3.2M CGroup: /system.slice/systemd-timesyncd.service └─792 /lib/systemd/systemd-timesyncd Jul 22 11:06:53 mizar systemd[1]: Starting Network Time Synchronization... Jul 22 11:06:53 mizar systemd[1]: Started Network Time Synchronization. Jul 22 11:06:59 mizar systemd-timesyncd[792]: Network configuration changed, trying to establish connection. Jul 22 11:07:01 mizar systemd-timesyncd[792]: Network configuration changed, trying to establish connection. Jul 22 11:07:02 mizar systemd-timesyncd[792]: Network configuration changed, trying to establish connection. Jul 22 11:07:02 mizar systemd-timesyncd[792]: Network configuration changed, trying to establish connection. Jul 22 11:07:04 mizar systemd-timesyncd[792]: Network configuration changed, trying to establish connection. Jul 22 11:07:04 mizar systemd-timesyncd[792]: Initial synchronization to time server [2a01:3f7::1]:123 (ntp.se). I have done some NTP-related configuration (added an NTP server more close by(. I'll try to find all deviations from the default I have made and come back. -- 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/1937238 Title: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: New Bug description: [impact] systemd-time-wait-sync service never completes when systemd-timesyncd package is not installed [test case] remove the systemd-timesyncd package and enable the systemd-time-wait- sync service, and reboot. Check status of the service to see it's stuck in 'activating' state, e.g.: ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago [regression potential] TBD [scope] this is needed in f and later the systemd-timesyncd package was split out from the main systemd package starting in focal, so this problem exists in f and later the service doesn't exist in b, so this is not needed there [original description] When I start my server running Ubuntu 20.04 the systemd-time-wait- sync.service is stuck in "activating" state. I noticed this because none of the systemd timer units triggered, because all the timers depend on systemd-time-wait-sync.service. Running "systemctl restart systemd-time-wait-sync.service" manually works around the problem. Some logs and command outputs: raek@mizar:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service systemd-time-wait-sync.service loaded activating start start Wait Until Kernel Time Synchronized raek@mizar:~$ systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago Docs: man:systemd-time-wait-sync.service(8) Main PID: 514 (systemd-time-wa) Tasks: 1 (limit: 9415) Memory: 972.0K CGroup: /system.slice/systemd-time-wait-sync.service └─514
[Touch-packages] [Bug 1937951] [NEW] modules for non-existent hardware are loaded for unknown reason (Ubunntu 20.04, kernel 5.4.0-80-generic)
Public bug reported: My laptop is Asus X302LA. I removed its HDD and plugged it externally via USB-SATA convertor. To restore the system's bootability, I had to switch from MODULES=dep to MODULES=most in /etc/initramfs-tools/initramfs.conf and regenerate initramfs images by command update-initramfs -u -k all After a successful boot I checked lsmod output and was surprised by a number of loaded modules for seemingly absent hardware. Like, inv_mpu6050 and ak8975. Do I have a way to check this hardware is actually present and is reporting any meaningful data ? If no, do Ubuntu maintainers of linux kernel and initramfs tools have a way to avoid loading these modules when their hardware is absent ? ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1937951 Title: modules for non-existent hardware are loaded for unknown reason (Ubunntu 20.04, kernel 5.4.0-80-generic) Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: My laptop is Asus X302LA. I removed its HDD and plugged it externally via USB-SATA convertor. To restore the system's bootability, I had to switch from MODULES=dep to MODULES=most in /etc/initramfs-tools/initramfs.conf and regenerate initramfs images by command update-initramfs -u -k all After a successful boot I checked lsmod output and was surprised by a number of loaded modules for seemingly absent hardware. Like, inv_mpu6050 and ak8975. Do I have a way to check this hardware is actually present and is reporting any meaningful data ? If no, do Ubuntu maintainers of linux kernel and initramfs tools have a way to avoid loading these modules when their hardware is absent ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937951/+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 1937945] [NEW] old gpg keyserver no longer works
Public bug reported:
This is with lxc 1:4.0.6-0ubuntu1~20.04.1 on Ubuntu 20.04 LTS.
All lxc-create commands that need to download GPG keys fail with
something similar to:
$ lxc-create -n foobar -t download -- -d ubuntu -r focal -a amd64
The cached copy has expired, re-downloading...
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver
lxc-create: foobar: lxccontainer.c: create_run_template: 1616 Failed to create
container from template
It turns out that the GPG keyserver used (pool.sks-keyservers.net) no
longer produces the expected responses. Upstream lxc has a ticket for
this:
https://github.com/lxc/lxc/issues/3894 ('lxc-create fails because
"ERROR: Unable to fetch GPG key from keyserver')
and it was fixed by changing:
DOWNLOAD_KEYSERVER="hkp://pool.sks-keyservers.net"
to:
DOWNLOAD_KEYSERVER="hkp://keyserver.ubuntu.com"
in this commit:
https://github.com/lxc/lxc/commit/f2a5d95d00a55bed27ef9920d67617cc75fecad8
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1937945
Title:
old gpg keyserver no longer works
Status in lxc package in Ubuntu:
New
Bug description:
This is with lxc 1:4.0.6-0ubuntu1~20.04.1 on Ubuntu 20.04 LTS.
All lxc-create commands that need to download GPG keys fail with
something similar to:
$ lxc-create -n foobar -t download -- -d ubuntu -r focal -a amd64
The cached copy has expired, re-downloading...
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver
lxc-create: foobar: lxccontainer.c: create_run_template: 1616 Failed to
create container from template
It turns out that the GPG keyserver used (pool.sks-keyservers.net) no
longer produces the expected responses. Upstream lxc has a ticket for
this:
https://github.com/lxc/lxc/issues/3894 ('lxc-create fails because
"ERROR: Unable to fetch GPG key from keyserver')
and it was fixed by changing:
DOWNLOAD_KEYSERVER="hkp://pool.sks-keyservers.net"
to:
DOWNLOAD_KEYSERVER="hkp://keyserver.ubuntu.com"
in this commit:
https://github.com/lxc/lxc/commit/f2a5d95d00a55bed27ef9920d67617cc75fecad8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1937945/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Could you attach output of "linux-purge --info"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools package in Ubuntu: Confirmed Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k That may be worse way, as then initrd.img file is missing for longer period of time and system integrity may suffer in case of e.g. power cut. Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Did you run "sudo linux-purge --keep=1"? (or replace "1" by "0" to purge even more) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools package in Ubuntu: Confirmed Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k That may be worse way, as then initrd.img file is missing for longer period of time and system integrity may suffer in case of e.g. power cut. Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+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 964705] Re: System policy prevents modification of network settings for all users
Still happening in Ubuntu 20.04 focal , We need to find some workaround for this , any other mobile or desktop OS can do this ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/964705 Title: System policy prevents modification of network settings for all users Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: Fix Released Status in network-manager package in openSUSE: Fix Released Bug description: This seems like a regression? The screen shot is at http://thesii.org/Screenshot.jpg The nearest link I can find is from the forum area at http://ubuntuforums.org/showthread.php?p=1146 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 19:36:45 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/964705/+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 1937932] [NEW] Blank Screen and Unable to get into windows while opening laptop lid after Sleep.
Public bug reported: While opening laptop display lid open ubuntu failed to open and stuck on blank screen with error. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Jul 25 15:02:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937932 Title: Blank Screen and Unable to get into windows while opening laptop lid after Sleep. Status in xorg package in Ubuntu: New Bug description: While opening laptop display lid open ubuntu failed to open and stuck on blank screen with error. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Jul 25 15:02:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05
[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot
This bug still exist since i was a kid. now in 2021 its still exist in Ubuntu 20.04 (LTS) . Will reupdate the status 10 years from now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot Status in ufw: Invalid Status in ufw package in Ubuntu: Invalid Status in ufw source package in Xenial: Invalid Status in ufw source package in Bionic: Invalid Status in ufw source package in Cosmic: Invalid Status in ufw source package in Disco: Invalid Bug description: Whenever I boot into 17.10 ufw is always inactive, even though /etc/ufw/ufw.conf has this: # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:56:40 2017 InstallationDate: Installed on 2015-04-01 (936 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+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 1937927] [NEW] Realtek 8821C PCIe Wifi driver problem, wifi speed very slow on connecting to 2.4ghz network.
Public bug reported: I am using the Realtek 8821C PCIE Wifi driver that is provided in the Additional drivers app of Ubuntu. When I connect to a 2.4 ghz network, the internet speed is very slow, it rarely goes above 4mbps. But the driver works fine when connected to a 5ghz network, easily reaching speeds of over 80mbps. I don't think it is a problem of my wifi router because in Windows OS running on the same laptop, I mostly get speeds of around 40mbps when connected to the 2.4 ghz network. 1. What is the full computer model number? Ans: HP Laptop 15s-eq0500AU. 2. If you update your BIOS to the newest version following the guide here, does this change anything? Ans: No. 3. Regarding your wireless Access Point (WAP): 3c. What wireless connection type are you using (802.11ac, 802.11n 150/300, 802.11g, etc.)? Ans: 802.11n 3d. If you switch to a different wireless type (802.11g or 802.11n if you are using 802.11g) does this change anything? Ans: Yes, in the 5ghz 802.11ac type, the speed is very normally very good. 3f. In order to understand the wireless environment your WAP is working in, please provide the output of the following terminal command: sudo iw dev wlan0 scan | grep -i "ds parameter set" Ans: [sudo] password for soumadeepsarkar1: command failed: No such device (-19) Output of sudo iw dev wlo1 scan | grep -i "ds parameter set" DS Parameter set: channel 11 DS Parameter set: channel 149 DS Parameter set: channel 149 DS Parameter set: channel 11 DS Parameter set: channel 2 DS Parameter set: channel 6 DS Parameter set: channel 10 DS Parameter set: channel 1 DS Parameter set: channel 7 DS Parameter set: channel 13 DS Parameter set: channel 1 DS Parameter set: channel 1 DS Parameter set: channel 4 DS Parameter set: channel 3 DS Parameter set: channel 10 3g. What encryption type are you using (ex. WEP, WPA2-PSK, etc.)? Ans: WPA2-PSK 3o. What frequency are you using (2.4GHz, 5GHz, etc.)? Ans: 2.4 GHz 3p. If you change frequency does it change anything? Ans: Yes, speed is good in 5ghz 4. Does another wireless device tested with the WAP have the same problem as the hardware you initially reported with? Ans: No. 5. What is the distance of the wireless device from the WAP? Ans: 6 metre 6. What is the number and type of obstructions between your device and the WAP? Ans: 2 6a. If you bring the device close to the WAP and eliminate obstructions, does this change anything? Ans: No 7. Does the issue occur with different WAPs? Ans: Yes 8. Is it a regression (i.e. did the problem happen in a prior Ubuntu release)? If so, what release specifically did it last work with? If you do not know, could you please test for this in the earliest release of Ubuntu that is supported as per Ubuntu Releases? Ans: I don't know if it is a regression and I cannot test for this in another release of Ubuntu. 9. Does this problem occur in the newest mainline kernel following https://wiki.ubuntu.com/Kernel/MainlineBuilds? Please mention what specific version of the mainline kernel you tested with in your report. Ans: Kernel version: 5.11.0-25-generic ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumadeepsarkar1 1797 F pulseaudio /dev/snd/controlC0: soumadeepsarkar1 1797 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 10:11:55 2021 InstallationDate: Installed on 2021-07-02 (23 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15s-eq0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2d1ce438-fd55-446d-8d61-e2d579055204 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-07-02 (22 days ago) dmi.bios.date: 05/13/2021 dmi.bios.release: 15.42 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.41 dmi.modalias: dmi:bvnAMI:bvrF.42:bd05/13/2021:br15.42:efr99.41:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 440L6PA#ACJ
