[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Bugs is not linked to Pulseaudio, it happens to me with Pipewire too (I had the bug with PA, and still here with PW...) -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in PipeWire: New Status in PulseAudio: New Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1764965/+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 2062126] [NEW] Booting with laptop lid closed and external monitors on X11 causes the computer to sleep prior to login
Public bug reported: When powering on a laptop with the lid closed, connected to a dock which is connected to external monitors, if gdm3 is going to run on X11, the computer is suspended prior to the login screen being displayed. Tapping a key on the keyboard wakes the computer out of suspend and immediately shows the login screen on the external monitors as expected. The computer does not suspend prior to login if gdm3 is going to run on Wayland. I'm encountering this issue with Ubuntu 24.04 beta, and believe it may be related to the following systemd issue: https://github.com/systemd/systemd/issues/16045 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2062126 Title: Booting with laptop lid closed and external monitors on X11 causes the computer to sleep prior to login Status in systemd package in Ubuntu: New Bug description: When powering on a laptop with the lid closed, connected to a dock which is connected to external monitors, if gdm3 is going to run on X11, the computer is suspended prior to the login screen being displayed. Tapping a key on the keyboard wakes the computer out of suspend and immediately shows the login screen on the external monitors as expected. The computer does not suspend prior to login if gdm3 is going to run on Wayland. I'm encountering this issue with Ubuntu 24.04 beta, and believe it may be related to the following systemd issue: https://github.com/systemd/systemd/issues/16045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062126/+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 1407940] Re: whoopsie-preferences does nothing
I have the same problem in Ubuntu MATE 22.04.3: $ sudo whoopsie-preferences Acquired the name: com.ubuntu.WhoopsiePreferences And it just hangs, no window comes up. I used to have trouble starting applications as root under X.Org, so I tried the old incantation too: pkexec env DISPLAY=:0 XAUTHORITY=/home/rdiez/.Xauthority whoopsie- preferences But the result is the same. There is no user-interface element in Ubuntu MATE to open the Whoopsie configuration tool, so manually typing some command would be the only way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1407940 Title: whoopsie-preferences does nothing Status in apport package in Ubuntu: Expired Bug description: Invoking `sudo whoopsie-preferences` does nothing but print an unhelpful error message to console. There should be a feedback of any king regardless of what the error is. The output is ** (process:13772): WARNING **: Could not get metrics: Key file does not have key 'report_metrics' initctl: Job failed to start Could not process configuration: Key file does not have key 'report_metrics' Could not process configuration: (null) Acquired the name: com.ubuntu.WhoopsiePreferences ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu8 Uname: Linux 3.17.7-031707-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 6 12:38:59 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-03 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apport SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1407940/+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 2031252] Re: Playing video with audio freezes
Same issue here. Gary's workaround works for me as well (Thank you!). Dell XPS 13 running Ubuntu 23.10, but it already happened before. -- 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/2031252 Title: Playing video with audio freezes Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm not sure when this started, but any video I play with audio is not working properly - it severely lags and/or freezes. This happens in Youtube on both Chrome and Firefox, and in the regular GNOME media player. Audio by itself works fine, and video with audio muted works fine. I tried restarting and downgrading the kernel, to no avail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ari2679 F pipewire ari2700 F wireplumber /dev/snd/seq:ari2679 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 13 17:22:56 2023 InstallationDate: Installed on 2022-06-07 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago) dmi.bios.date: 06/12/2023 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET85W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031252/+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 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
On 18.04, I noticed this warning started occurring after i ran a GTK application - gtimelog - with sudo. Now this warning is printed every time i run the application without sudo. Warning disappears when running as sudo. Seems like some permissions problem. Don't know how to fix it. Moral of the story : Don't run gui applications with sudo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 2022836] [NEW] package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de er
Public bug reported: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 3 13:13:18 2023 ErrorMessage: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2022836 Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 Status in tzdata package in Ubuntu: New Bug description: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 3 13:13:18 2023 ErrorMessage: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2022836/+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 2022835] [NEW] package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [01/Jun/2023:00:00:26 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:09:56 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:13:20 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Date: Sat Jun 3 13:13:20 2023 ErrorMessage: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for HP_Color_LaserJet_E55040_5A6F72: implicitclass://HP_Color_LaserJet_E55040_5A6F72/ device for HP_LaserJet_P4014_319155: implicitclass://HP_LaserJet_P4014_319155/ device for HP_LaserJet_P4014_319155@NPI319155.local: implicitclass://HP_LaserJet_P4014_319155%40NPI319155.local/ device for L5190: dnssd://EPSON%20L5190%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-e0bb9e531389 MachineType: Dell Inc. Latitude 5430 Papersize: letter PpdFiles: HP_Color_LaserJet_E55040_5A6F72: HP Color LaserJet E55040, driverless, cups-filters 1.28.15 L5190: EPSON L5190 Series, driverless, cups-filters 1.28.15 HP_LaserJet_P4014_319155@NPI319155.local: HP LaserJet P4014, driverless, cups-filters 1.28.15 HP_LaserJet_P4014_319155: HP LaserJet P4014, driverless, cups-filters 1.28.15 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=2efb7e3e-d9e5-4dda-a70f-e5c6425f913c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=2efb7e3e-d9e5-4dda-a70f-e5c6425f913c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: cups Title: package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2022 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 03G0RF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd06/20/2022:br1.4:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn03G0RF:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2022835 Title: package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 Status in cups package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [01/Jun/2023:00:00:26 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:09:56 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:13:20 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Date: Sat Jun 3 13:13:20 2023 ErrorMessage: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for HP_Color_LaserJet_E55040_5A6F72: implicitclass://HP_Color_LaserJet_E55040_5A6F72/ device for HP_LaserJet_P4014_319155: implicitclass://HP_LaserJ
[Touch-packages] [Bug 2016021] Re: icu FTBFS on lunar
OK makes sense. Tests that are 'skipped' as above are listed at the end of the test run (with the bug url) and can be optionally enabled. (BTW ICU 73 is in RC and releases soon.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/2016021 Title: icu FTBFS on lunar Status in icu package in Ubuntu: Confirmed Bug description: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+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 2016021] Re: icu FTBFS on lunar
What ICU is this? I can't tell which version from here. Your analysis
sounds reasonable, may have to ignore the tests (there's a logKnownIssue
mechanism) - put the following before the failing test case:
if (logKnownIssue("https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021";,
"tzdata issue")) {
return;
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/2016021
Title:
icu FTBFS on lunar
Status in icu package in Ubuntu:
Confirmed
Bug description:
During the last test rebuild, it was noticed that icu failed to build
from source, with the following failures in the test suite:
-
| *** FAILING TEST SUMMARY FOR: intltest
TestAliasedNames
TestCanonicalID
TimeZoneTest
format
| *** END FAILING TEST SUMMARY FOR: intltest
The issue is related to the recent tzdata updates: not only the usual
batch of changes made to reflect the current state of the world, but
also changes made to have a better data set for pre-1970 dates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+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 2011309] Re: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for
** Changed in: pulseaudio (Ubuntu) Status: Opinion => Invalid -- 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/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: Invalid Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011309/+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 2011309] Re: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for
Current the machine in use is a mini-pc. Per other purchasers of the mini-pc on Amazon, the sound chips on this pc are not compatible with Ubuntu jammy-jellyfish and thus this writer should NOT have upgraded the pc to jammy-jellyfish which did not immediately but eventually appeared to kill sound on the pc. I have since USB ported Focal-Fossa back on this machine and the sound works fine and I set the pc to NEVER upgrade Ubuntu to Jammy. So there is no current reason to continue this bug, unless someone is aware of how Jammy would become compatible. I will leave it to the community to decide to close this bug. But I do not intend to pursue it since the mini-pc is a useful tool as it is and works quite fine with what it has got. It only costs $129 so it is not worth the sweat. -- 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/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: Opinion Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011309/+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 2011309] Re: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for
** Changed in: pulseaudio (Ubuntu) Status: New => Opinion -- 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/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: Opinion Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011309/+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 2011309] [NEW] [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also fo
Public bug reported: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: New Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.produc
Re: [Touch-packages] [Bug 2009224] Bug is not a security issue
This bug may NOT BE A SECURITY ISSUE, but without access to audio I cannot do 90% of the work I do in Ubuntu. I suggest that you acknowledge the problem and fix it. For the meantime I will be using Windows 10. G Bug description: I didn't have sound after an update to Ubuntu (and a reboot the next day). Pulseaudio does not recognize my soundcard. Since all my work involves audio, I have switched to Windows 10 (I have a dual boot computer). LSPCI finds my sound card but alsa and pacmd don't. Until this is fixed, I am no longer using UBuntu but am switching to Windows 10. Let me know when this issue is resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: george 4472 F pipewire-media- /dev/snd/pcmC1D0c: george 4473 F...m pulseaudio /dev/snd/seq:george 4471 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 13:14:07 2023 InstallationDate: Installed on 2021-07-19 (592 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago) dmi.bios.date: 03/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A3 dmi.board.name: H11H4-AD2 dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: SoniaHC dmi.product.sku: dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009224/+subscriptions On 3/3/23 2:09 PM, Paulo Flabiano Smorigo wrote: > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > -- 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/2009224 Title: pulseaudio does not recognize PCI SoundBlaster card Status in alsa-driver package in Ubuntu: New Bug description: I didn't have sound after an update to Ubuntu (and a reboot the next day). Pulseaudio does not recognize my soundcard. Since all my work involves audio, I have switched to Windows 10 (I have a dual boot computer). LSPCI finds my sound card but alsa and pacmd don't. Until this is fixed, I am no longer using UBuntu but am switching to Windows 10. Let me know when this issue is resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: george 4472 F pipewire-media- /dev/snd/pcmC1D0c: george 4473 F...m pulseaudio /dev/snd/seq:george 4471 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 13:14:07 2023 InstallationDate: Installed on 2021-07-19 (592 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago) dmi.bios.date: 03/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A3 dmi.board.name: H11H4-AD2 dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer
[Touch-packages] [Bug 2009224] [NEW] pulseaudio does not recognize PCI SoundBlaster card
Public bug reported: I didn't have sound after an update to Ubuntu (and a reboot the next day). Pulseaudio does not recognize my soundcard. Since all my work involves audio, I have switched to Windows 10 (I have a dual boot computer). LSPCI finds my sound card but alsa and pacmd don't. Until this is fixed, I am no longer using UBuntu but am switching to Windows 10. Let me know when this issue is resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: george 4472 F pipewire-media- /dev/snd/pcmC1D0c: george 4473 F...m pulseaudio /dev/snd/seq:george 4471 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 13:14:07 2023 InstallationDate: Installed on 2021-07-19 (592 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago) dmi.bios.date: 03/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A3 dmi.board.name: H11H4-AD2 dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: SoniaHC dmi.product.sku: dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2009224 Title: pulseaudio does not recognize PCI SoundBlaster card Status in alsa-driver package in Ubuntu: New Bug description: I didn't have sound after an update to Ubuntu (and a reboot the next day). Pulseaudio does not recognize my soundcard. Since all my work involves audio, I have switched to Windows 10 (I have a dual boot computer). LSPCI finds my sound card but alsa and pacmd don't. Until this is fixed, I am no longer using UBuntu but am switching to Windows 10. Let me know when this issue is resolved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: george 4472 F pipewire-media- /dev/snd/pcmC1D0c: george 4473 F...m pulseaudio /dev/snd/seq:george 4471 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 13:14:07 2023 InstallationDate: Installed on 2021-07-19 (592 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-08-14 (201 days ago) dmi.bios.date: 03/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A3 dmi.board.name: H11H4-AD2 dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A3:bd03/18/2016:br5.11:svnAcer:pnSoniaHC:pvr:rvnAcer:rnH11H4-AD2:rvrV1.1:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: SoniaHC dmi.product.sku: dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009224/+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 1990659] [NEW] Systemd component broken following update
Public bug reported: Following update to the latest package today (245.4-4ubuntu3.18) on focal, systemd-resolved and systemd-timesyncd (at least) can't start Ubuntu 20.04 x86_64 kernel 5.4.0-122-generic logs: Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution... Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated too quickly. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Following update to the latest package today (245.4-4ubuntu3.18) on focal, systemd-resolved and systemd-timesyncd can't start Ubuntu 20.04 x86_64 kernel 5.4.0-122-generic logs: Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution... Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution. - Sep 23 10:48:53 curie systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. + Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated too quickly. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution. ** Description changed: Following update to the latest package today (245.4-4ubuntu3.18) on - focal, systemd-resolved and systemd-timesyncd can't start + focal, systemd-resolved and systemd-timesyncd (at least) can't start Ubuntu 20.04 x86_64 kernel 5.4.0-122-generic logs: Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution... Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Sep 23 10:48:53 systemd[1]: Stopped Network Name Resolution. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Start request repeated too quickly. Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Sep 23 10:48:53 systemd[1]: Failed to start Network Name Resolution. -- 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/1990659 Title: Systemd component broken following update Status in systemd package in Ubuntu: New Bug description: Following update to the latest package today (245.4-4ubuntu3.18) on focal, systemd-resolved and systemd-timesyncd (at least) can't start Ubuntu 20.04 x86_64 kernel 5.4.0-122-generic logs: Sep 23 10:48:53 systemd[1]: Starting Network Name Resolution... Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument Sep 23 10:48:53 systemd[1672342]: systemd-resolved.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-resolved: Invalid argument Sep 23 10:48:53 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NA
[Touch-packages] [Bug 1974427] [NEW] window redraw wrong size when plug in hdmi
Public bug reported: If I have a window open on the primary display (laptop) and plug in an HDMI monitor (secondary) the window (primary) redraws without accounting for the top status bar. In other words, the window status bar is COVERING UP the top of the application window (no min, max close). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 20 06:40:06 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:38ef] InstallationDate: Installed on 2022-05-14 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81D2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=ff8cc35c-2ad1-4b44-b02e-649148be44fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvr7VCN24WW:bd06/15/2018:br1.24:efr1.24:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:skuLENOVO_MT_81D2_BU_idea_FM_ideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/1974427 Title: window redraw wrong size when plug in hdmi Status in xorg package in Ubuntu: New Bug description: If I have a window open on the primary display (laptop) and plug in an HDMI monitor (secondary) the window (primary) redraws without accounting for the top status bar. In other words, the window status bar is COVERING UP the top of the application window (no min, max close). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 20 06:40:06 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:38ef] InstallationDate: Installed on 2022-05-14 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81D2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=ff8cc35c-2ad1-4b44-b02e-649148be44fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Upgra
[Touch-packages] [Bug 1969959] Re: Weird colors after startup (Ubuntu 22.04)
Same here, trying the first stable live release of 22.04. I get a weirdly saturated green-lime combo. Picture attached. VGA: Intel HD Graphics 530 Monitor: HP LE2201w ** Attachment added: "Picture of screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+attachment/5582878/+files/20220423_194416.jpg -- 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/1969959 Title: Weird colors after startup (Ubuntu 22.04) Status in xorg package in Ubuntu: Confirmed Bug description: I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+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 1718434] Re: Crash while playing video
You may close this bug as I upgraded the OS to Ubuntu 20 -- 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/1718434 Title: Crash while playing video Status in xorg package in Ubuntu: Invalid Bug description: Crash while playing video ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.69 Wed Aug 16 19:34:54 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 20 19:29:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1094] Subsystem: Acer Incorporated [ALI] Device [1025:1094] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a030 Quanta Computer, Inc. Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575G:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-575G dmi.product.version: V1.25 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83+git1708241830.f19dbb~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.3~git1708280730.242212~gd~x version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Sep 20 19:18:12 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718434/+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 1718434] Re: Crash while playing video
This issue not found in Ubuntu 20 -- 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/1718434 Title: Crash while playing video Status in xorg package in Ubuntu: Invalid Bug description: Crash while playing video ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.69 Wed Aug 16 19:34:54 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 20 19:29:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1094] Subsystem: Acer Incorporated [ALI] Device [1025:1094] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a030 Quanta Computer, Inc. Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.25:bd03/03/2017:svnAcer:pnAspireE5-575G:pvrV1.25:rvnAcer:rnIronman_SK:rvrV1.25:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-575G dmi.product.version: V1.25 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83+git1708241830.f19dbb~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.3~git1708280730.242212~gd~x version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Sep 20 19:18:12 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718434/+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 1956957] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
I see these in my package files, maybe I should delete a couple lines ? linux-generic-hwe-20.04 install linux-headers-5.11.0-27-generic install linux-headers-5.11.0-43-generic install linux-headers-5.4.0-88 install linux-headers-5.4.0-88-generic install linux-headers-5.4.0-89 install linux-headers-5.4.0-89-generic install linux-headers-5.4.0-91 install linux-headers-5.4.0-91-generic install linux-headers-generic install linux-headers-generic-hwe-20.04 install linux-hwe-5.11-headers-5.11.0-27install linux-hwe-5.11-headers-5.11.0-43install linux-image-5.11.0-27-generic install linux-image-5.11.0-43-generic install linux-image-5.4.0-88-genericinstall linux-image-5.4.0-89-genericinstall linux-image-5.4.0-91-genericinstall linux-image-generic install linux-image-generic-hwe-20.04 install linux-libc-dev:amd64install linux-modules-5.11.0-27-generic install linux-modules-5.11.0-43-generic install linux-modules-5.4.0-88-generic install linux-modules-5.4.0-89-generic install linux-modules-5.4.0-91-generic install linux-modules-extra-5.11.0-27-generic install linux-modules-extra-5.11.0-43-generic install linux-modules-extra-5.4.0-88-genericinstall linux-modules-extra-5.4.0-89-genericinstall linux-modules-extra-5.4.0-91-genericinstall -- 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/1956957 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: 3 weeks after installing 20.04.3 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 10 13:03:11 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-22 (19 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 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/1956957/+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 1956957] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Hello, Thank you for your answer. Here is the output : jr@jrUbuntu:~$ ls -l /boot total 339272 -rw-r--r-- 1 root root254083 déc. 14 11:29 config-5.11.0-44-generic -rw-r--r-- 1 root root254083 janv. 7 00:13 config-5.11.0-46-generic -rw-r--r-- 1 root root237940 janv. 6 22:56 config-5.4.0-94-generic drwx-- 3 root root 4096 janv. 1 1970 efi drwxr-xr-x 4 root root 4096 janv. 12 08:25 grub lrwxrwxrwx 1 root root27 janv. 12 08:24 initrd.img -> initrd.img-5.4.0-94-generic -rw-r--r-- 1 root root 102091693 janv. 10 13:07 initrd.img-5.11.0-44-generic -rw-r--r-- 1 root root 102091767 janv. 14 09:38 initrd.img-5.11.0-46-generic -rw-r--r-- 1 root root 88223747 janv. 12 08:25 initrd.img-5.4.0-94-generic lrwxrwxrwx 1 root root28 janv. 12 08:24 initrd.img.old -> initrd.img-5.11.0-46-generic drwx-- 2 root root 16384 déc. 22 11:00 lost+found -rw-r--r-- 1 root root182704 août 18 2020 memtest86+.bin -rw-r--r-- 1 root root184380 août 18 2020 memtest86+.elf -rw-r--r-- 1 root root184884 août 18 2020 memtest86+_multiboot.bin -rw--- 1 root root 5864386 déc. 14 11:29 System.map-5.11.0-44-generic -rw--- 1 root root 5864386 janv. 7 00:13 System.map-5.11.0-46-generic -rw--- 1 root root 4756293 janv. 6 22:56 System.map-5.4.0-94-generic lrwxrwxrwx 1 root root24 janv. 12 08:24 vmlinuz -> vmlinuz-5.4.0-94-generic -rw--- 1 root root 11746656 déc. 14 16:23 vmlinuz-5.11.0-44-generic -rw--- 1 root root 11746784 janv. 7 00:27 vmlinuz-5.11.0-46-generic -rw--- 1 root root 13656320 janv. 7 00:07 vmlinuz-5.4.0-94-generic lrwxrwxrwx 1 root root25 janv. 12 08:24 vmlinuz.old -> vmlinuz-5.11.0-46-generic jr@jrUbuntu:~$ There were more files and I ran sudo apt-get autoremove --purge Then apt-mark showmanual | grep -E "linux-.*[0-9]" | grep -v "hwe" | xargs -r sudo apt-mark auto And again sudo apt autoremove --purge -y Seems to have deleted a couple files. Well I installed it in the common way I'd say : USB drive, erase all disk and install encrypted version with LUKS. I connected to a wifi network during the installation. Then I ran the following commands to reinstall the packages I had on my previous computer (attached file) : sudo apt-get update sudo apt-get install dselect sudo dselect update sudo dpkg --set-selections < liste-des-paquets sudo apt-get -u dselect-upgrade (I've been doing this a couple times from previous systems, starting in 20.04, now I'm in 20.04.3). Do you see what happened ? Thanks ** Attachment added: "liste-des-paquets_jrUbuntu_2022-01-08-12-49" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956957/+attachment/5554394/+files/liste-des-paquets_jrUbuntu_2022-01-08-12-49 -- 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/1956957 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: 3 weeks after installing 20.04.3 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 10 13:03:11 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-22 (19 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 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/1956957/+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 1957055] [NEW] Xorg freeze
Public bug reported: tried with nvidia 390 driver also ,but no improvement ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 14:22:12 2022 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (156 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (141 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1957055 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: tried with nvidia 390 driver also ,but no improvement ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 14:22:12 2022 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (156 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (141 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.ver
[Touch-packages] [Bug 1956957] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: 3 weeks after installing 20.04.3 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 10 13:03:11 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-22 (19 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1956957 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: 3 weeks after installing 20.04.3 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 10 13:03:11 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-22 (19 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 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/1956957/+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 1955297] [NEW] Xorg freeze
Public bug reported: Mouse freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 18 15:24:35 2021 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (132 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (117 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1955297 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Mouse freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 18 15:24:35 2021 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (132 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (117 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell
[Touch-packages] [Bug 1953719] [NEW] logrotate.service fails because it starts before winbind.service
Public bug reported: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1953719 Title: logrotate.service fails because it starts before winbind.service Status in logrotate package in Ubuntu: New Bug description: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1953719/+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 1694989] Re: apt-mark overwrites existing held package info
This is very annoying, I agree that either, apt-mark should not accept 'uninstalled' packages or we should avoid losing packages marked as 'hold' Steps to reproduce (assuming none of these two packages are available) Trying to mark as hold two uninstalled packages... and notice that the second we add the second one we lost the status for the first one.. > apt update > apt-mark hold p0f p0f set on hold. > apt-mark showhold p0f > grep -c p0f /var/lib/dpkg/status 1 > apt-mark hold dovecot-core dovecot-core set on hold. > apt-mark showhold dovecot-core > grep -c p0f /var/lib/dpkg/status 0 -- 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/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Triaged Status in apt package in Debian: New Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+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 1948346] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has m
Easy to fix: sudo apt purge libnih1:i386 libnih-dbus1:i386 && sudo apt upgrade -y -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1948346] [NEW] package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has
Public bug reported: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1505584] Re: [Realtek ALC887-VD] Playback only through 2 channels by default
I have a worse bug : after setting alsamixer to 6ch and restarting pulseaudio, I have no rear sound and no dialog in 5.1 application (I select a 5.1 profile in pulseaudio + the sound section in Ubuntu setting pannel is unable to test the speakers (they remain silent while the system sound can actually be played in other manner). This occurs at least in Ubuntu 20.04 and 21.04 -- 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/1505584 Title: [Realtek ALC887-VD] Playback only through 2 channels by default Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu does not detect my 5.1 surround sound[0] by default. In order to get it detected, I have to do the following: 1) Open alsamixer 2) Change the "Channel Mode" setting from "2ch" to "6ch" (there is also a "4ch" setting) 3) `pulseaudio -k` I have to do this on every boot, as the "6ch" setting is not remembered. [0] My soundcard and sound system are 5.1, but I actually only have front left, center, right and the subwoofer. This shouldn't affect how Ubuntu acts at all (because it can't know what speakers I have plugged in to my subwoofer), but will mean that I can't report on whether or not rear channels are working as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel24007 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 13 10:23:16 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-30 (439 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] Playback problem UpgradeStatus: Upgraded to vivid on 2015-08-24 (49 days ago) dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31 (G3) (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd01/18/2012:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7788 dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-08-05T11:15:16.899686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1505584/+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 1940774] [NEW] xorg
Public bug reported: xorg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 21:14:51 2021 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (14 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2021-08-22 (0 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1940774 Title: xorg Status in xorg package in Ubuntu: New Bug description: xorg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 21:14:51 2021 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (14 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2021-08-22 (0 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20
[Touch-packages] [Bug 1938959] [NEW] package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Aug 4 19:47:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgTerminalLog: [1mdpkg:[0m error processing package mesa-va-drivers:amd64 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal [1mdpkg:[0m too many errors, stopping ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal ExtraDebuggingInterest: Yes, including running git bisection searches InstallationDate: Installed on 2020-04-01 (490 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 045e:0752 Microsoft Corp. Wired Keyboard 400 Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=d7a0cf22-bba9-4c79-89f5-0d805b99da00 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mesa Title: package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1208 dmi.board.asset.tag: Default string dmi.board.name: B250 MINING EXPERT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1208:bd09/24/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB250MININGEXPERT:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ubuntu -- 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/1938959 Title: package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in mesa package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Aug 4 19:47:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgTerminalLog: [1mdpkg:[0m error processing package mesa-va-drivers:amd64 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal [1mdpkg:[0m too many errors, stopping ErrorMessage: package is in a very bad inconsistent state; you shou
[Touch-packages] [Bug 1933530] Re: Translation error with accentuation
** Description changed: An alert is issued when the snap is called ```sh # LANG=pt_BR snap refresh 2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's "" is lowercase: "o directório de destino" Todos os snaps atualizados. ```sh In en_US works as expected ```sh # LANG=en_US snap refresh All snaps up to date. ``` - - Affected file - /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo + Patch Attached + Change line 4581 of data/pt/LC_MESSAGES/snappy.po + ``` + -msgstr "o directório de destino" + +msgstr "O directório de destino" + ``` Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175 ** Patch added: "snappy.patch" https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+attachment/5506768/+files/snappy.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1933530 Title: Translation error with accentuation Status in language-pack-pt-base package in Ubuntu: New Bug description: An alert is issued when the snap is called ```sh # LANG=pt_BR snap refresh 2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's "" is lowercase: "o directório de destino" Todos os snaps atualizados. ```sh In en_US works as expected ```sh # LANG=en_US snap refresh All snaps up to date. ``` Patch Attached Change line 4581 of data/pt/LC_MESSAGES/snappy.po ``` -msgstr "o directório de destino" +msgstr "O directório de destino" ``` Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+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 1933530] [NEW] Translation error with accentuation
Public bug reported: An alert is issued when the snap is called ```sh # LANG=pt_BR snap refresh 2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's "" is lowercase: "o directório de destino" Todos os snaps atualizados. ```sh In en_US works as expected ```sh # LANG=en_US snap refresh All snaps up to date. ``` Patch Attached Change line 4581 of data/pt/LC_MESSAGES/snappy.po ``` -msgstr "o directório de destino" +msgstr "O directório de destino" ``` Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175 ** Affects: language-pack-pt-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1933530 Title: Translation error with accentuation Status in language-pack-pt-base package in Ubuntu: New Bug description: An alert is issued when the snap is called ```sh # LANG=pt_BR snap refresh 2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's "" is lowercase: "o directório de destino" Todos os snaps atualizados. ```sh In en_US works as expected ```sh # LANG=en_US snap refresh All snaps up to date. ``` Patch Attached Change line 4581 of data/pt/LC_MESSAGES/snappy.po ``` -msgstr "o directório de destino" +msgstr "O directório de destino" ``` Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+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
Re: [Touch-packages] [Bug 1928346] Re: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Hi Alex! Please refer to the below Image! [image: Screenshot from 2021-05-14 19-21-46.png] Regards, *Rajthilak R* / +91 91593 82738 - M.Sc., Information Technology Anna University, Chennai. India. On Fri, May 14, 2021 at 6:00 AM Alex Murray <1928...@bugs.launchpad.net> wrote: > Thanks for reporting this issue - can you please try running the > following in a terminal and see if this resolves the problem: > > sudo apt-get install -f --reinstall libseccomp2 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1928346 > > Title: > package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: > package is in a very bad inconsistent state; you should reinstall it > before attempting configuration > > Status in libseccomp package in Ubuntu: > New > > Bug description: > Broken in mid of upgrade from 20.10 to 21.04 > > ProblemType: Package > DistroRelease: Ubuntu 21.04 > Package: libseccomp2:amd64 2.5.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu50.6 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Thu May 13 19:56:07 2021 > ErrorMessage: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > InstallationDate: Installed on 2018-12-12 (883 days ago) > InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 > (20180731) > Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, > 3.8.6-0ubuntu1 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.20.9ubuntu1 >apt 2.1.10ubuntu0.3 > SourcePackage: libseccomp > Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to > install/upgrade: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1928346/+subscriptions > ** Attachment added: "Screenshot from 2021-05-14 19-21-46.png" https://bugs.launchpad.net/bugs/1928346/+attachment/5497529/+files/Screenshot%20from%202021-05-14%2019-21-46.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1928346 Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libseccomp package in Ubuntu: New Bug description: Broken in mid of upgrade from 20.10 to 21.04 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libseccomp2:amd64 2.5.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 13 19:56:07 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-12-12 (883 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: libseccomp Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1928346/+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 1928346] [NEW] package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: Broken in mid of upgrade from 20.10 to 21.04 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libseccomp2:amd64 2.5.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 13 19:56:07 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-12-12 (883 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: libseccomp Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1928346 Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libseccomp package in Ubuntu: New Bug description: Broken in mid of upgrade from 20.10 to 21.04 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libseccomp2:amd64 2.5.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 13 19:56:07 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-12-12 (883 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: libseccomp Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1928346/+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 1910840] [NEW] Xorg freeze
Public bug reported: After login the screen freezes with mouse pointer duplicating. No operations can be performed .Need to do hard reboot.This started happening after upgrade(5.0.58) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:46:45 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-58-generic, x86_64: installed nvidia, 390.138, 5.4.0-59-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2020-11-02 (68 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e6874eb1-356d-41dd-b4e2-a1f27d050215 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1910840 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: After login the screen freezes with mouse pointer duplicating. No operations can be performed .Need to do hard reboot.This started happening after upgrade(5.0.58) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:46:45 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-58-generic, x86_64: installed nvidia, 390.138, 5.4.0-59-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2020-11-02 (68 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e6874eb1-356d-41dd-b4e2-a1f27d050215 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (p
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
I updated my Xubuntu system 2 days ago but only rebooted last night, and now my system won't boot. So I tried to reinstall, had it download updates during installation, and the installer crashed and sent me here. was installing Xubuntu 20.04.1 LTS from USB on: 2013 Alienware Aurora some i7 (ivy or sandy bridge) GTX 660ti -- 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 with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: Confirmed Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: 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 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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 1886697] [NEW] Xorg crash
Public bug reported: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know how to search the syslog, but I expect to find something funky around something like "GUI going to sleep". The reason I think it is a true "crash" is, despite being away from my the PC for 1 hr, the job directory is empty. This makes me think the computer processes were halted during the events that lead to the GUI death. I have played with my GPU settings. As per this NVIDIA thread https://forums.developer.nvidia.com/t/random-xid-61-and-xorg-lock- up/79731/252, I have set my minumum clock speed to 1050mHz. This had been successful up until this point at preventing a different issue not related to this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 13:26:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:13a2] InstallationDate: Installed on 2020-05-26 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5a52a344-c840-428b-89b5-b3c2e86fbc43 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal 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/1886697 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know how
[Touch-packages] [Bug 1885013] [NEW] package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Problem occurred during a (longer) system update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.9 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Wed Jun 24 21:21:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-07-08 (1813 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1885013 Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Problem occurred during a (longer) system update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.9 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Wed Jun 24 21:21:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-07-08 (1813 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 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/1885013/+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 1883334] [NEW] Xorg freezes after Lock (win+L or via Menu>Lock)
Public bug reported: This started to happen after installing the last update last week. If I lock the screen (using either Win+L or opening the menu and clicking Lock) the screen turns to black and it doesn't come back anymore. I know the system is still operational since the NumLock button still responds (turns on and off If I press it) and the HotSpot still works on my phone, but the screen just doesn't come back from black. This wasn't an issue before the update, it is very recent. Thank you very much! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 22:51:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640] Subsystem: Dell Radeon R7 M260/M265 [1028:0640] MachineType: Dell Inc. Inspiron 5447 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=45c56570-89cf-4b2d-8f15-ee1ce0d54f68 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0MHP6R dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/12/2014:svnDellInc.:pnInspiron5447:pvrA05:rvnDellInc.:rn0MHP6R:rvrA01:cvnDellInc.:ct8:cvrA05: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.sku: Inspiron 5447 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102+git2006051830.5ab603~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2006110730.27b7b8~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2006110730.27b7b8~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu ** Description changed: - This started to happen after I install the last update last week, at - first it would occur a few times, but now is every time. If I lock the - screen (using either Win+L or opening the menu e click Lock) the screen - turns to black and it doesn't come back anymore. I know the system is - still operational since the NumLock button still responds (turns on and - off If I press it) and the HotSpot still works on my phone, but the - screen just doesn't come back from black. This wasn't an issue before - the update, it is very recent. Thank you very much! + This started to happen after installing the last update last week. If I + lock the screen (using either Win+L or opening the menu and clicking + Lock) the screen turns to black and it doesn't come back anymore. I know + the system is still operational since the NumLock button still responds + (turns on and off If I press it) and the HotSpot still works on my + phone, but the screen just doesn't come back from black. This wasn't an + issue before the update, it is very recent. Thank you very much! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 22:51:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed - virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed + virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed + virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several
[Touch-packages] [Bug 1880293] [NEW] Xorg freeze
Public bug reported: When I click the button "Show Applications" then I click on a icon and drag over another icon, then a group is created. If I open a group then I click on the pen button to edit the group name, the title becomes editable, then If I delete all the letters then click out of the group window to save the changes the UI freezes and there's nothing I can do to unfreeze it. The system is still responsible since the mouse cursor moves (but clicks don't have any effect) and the NUMLOCK indicator is also responsive on the keyboard. I then panic and press a wild combination of CTRL+ALT+Windows button+Esc+Q+F1+F2 untill the terminal appears asking for login and password, but the UI disappears, then I can only reboot from there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 23 06:36:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640] Subsystem: Dell Radeon R7 M260/M265 [1028:0640] MachineType: Dell Inc. Inspiron 5447 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=45c56570-89cf-4b2d-8f15-ee1ce0d54f68 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0MHP6R dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/12/2014:svnDellInc.:pnInspiron5447:pvrA05:rvnDellInc.:rn0MHP6R:rvrA01:cvnDellInc.:ct8:cvrA05: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.sku: Inspiron 5447 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005200630.bf602a~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005230730.5f365a~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2005230730.5f365a~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu ** Attachment added: "This screenshot shows where the bug occurs" https://bugs.launchpad.net/bugs/1880293/+attachment/5375829/+files/Screenshot%20from%202020-05-23%2006-48-29.png -- 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/1880293 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I click the button "Show Applications" then I click on a icon and drag over another icon, then a group is created. If I open a group then I click on the pen button to edit the group name, the title becomes editable, then If I delete all the letters then click out of the group window to save the changes the UI freezes and there's nothing I can do to unfreeze it. The system is still responsible since the mouse cursor moves (but clicks don't have any effect) and the NUMLOCK indicator is also responsive on the keyboard. I then panic and press a wild combination of CTRL+ALT+Windows button+Esc+Q+F1+F2 untill the terminal appears asking for login and password, but the UI disappears, then I can only reboot from there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 23 06:36:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Once a week GpuHangReproducibilit
[Touch-packages] [Bug 1878587] Re: pk-client-error-quarl could not get lock when selecting driver from synaptic
Maybe you would like to set concerned package to "synaptic"... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1878587 Title: pk-client-error-quarl could not get lock when selecting driver from synaptic Status in software-properties package in Ubuntu: New Bug description: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878587/+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 1878587] [NEW] pk-client-error-quarl could not get lock when selecting driver from synaptic
Public bug reported: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of error message with sofware_properties-gtk and synaptic opened." https://bugs.launchpad.net/bugs/1878587/+attachment/5371450/+files/bug_synaptic_software-properties-gtk.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1878587 Title: pk-client-error-quarl could not get lock when selecting driver from synaptic Status in software-properties package in Ubuntu: New Bug description: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) To manage notificat
Re: [Touch-packages] [Bug 1231730] Re: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
Dear Marcus, this was not, as it turned out, strictly a "bug" in Launchpad terms. In fact, as I and my Watcher Raymond discovered from inspired research by a guy whose name I have forgotten, it started life as a deliberate "System Restriction" approved and adopted in the minutes of Ubuntu's Central Committee. Although originally intended as an emergency remedy to cover the imminent release of the upcoming Ubuntu version, it remained in force over the next _half dozen or so_ releases. The story goes like so;- with HDMI becoming accepted it was intended to include suitable drivers in the next Ubuntu, but with the release deadline looming, it was recognised that the "Radeon" drivers for ATI video cards, were not fit to go. The sound sub-system of said drivers was seen to host a nest of insecticide resistant bugs keen to crash the entire system. The official solution was to go ahead with the release _with HDMI sound disabled_ but leaving the video. It effectively _became a bug_ when, possibly from embarrassment (?), all mention of this was omitted from the "Release Notes" of this, and following versions. There were two workarounds:- 1) select the appropriate proprietary ATI driver & install 2) follow instructions from Launchpad contributors, ignore the risk, and _simply re-enable audio._ I had fun with this at the time. Hope you find it of interest. Regards, Bob On 05/03/2020 13:14, Marcus Tomlinson wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: alsa-driver (Ubuntu) > Status: New => Incomplete > -- 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/1231730 Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Invalid Bug description: I have 2 computers; 1) this with Asus M2A-VMHDMI motherboard, 2core AMD CPU and ATI HD 6000 series graphic card where I do not actually use the HDMI output ; 2) the second with Asus M4A 72 PRO motherboard, 4core Phenom and ATI HD 7000 (previously with the 6000 above), which does use the HDMI to connect to a Sharp brand TV. The symptom is the same:- i) turn computer on ii) select "system settings" iii) select "sound" iv) observe that I am presented with only 2 choices for sound "output" ---onboard analogue, or onboard digital; NO HDMI This same symptom occurs with every attempted upgrade from 12.04 Precise Pangolin, whether I upgrade online or from CD ; or erase the entire installation and re-install the later versions fresh from CD (which I often do when out of frustration I have been tempted to load proprietary ATI drivers ...resulting in little pop-ups with AMD kindly informing me that I am mounting "Unsupported Hardware" sic.) NOW:- When ASUS make half the Motherboards on the planet and ATI make half the Graphic cards, then WHY?? , if I choose on account of this prevalence to regard this as a rather general bug and and start writing this report is my computer already telling me that I have to go "unix-nerd" , and open a terminal, and install a program called "pavucontrol" which is a volume control for something called "Pulse Audio" and which as I eventually find instruction; will, if run with no options and no commands, tell me in an extremely frustrating fashion, that somewhere in it's interior it is running my desired HDMI at 100% volume !! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob1848 F pulseaudio /dev/snd/controlC0: bob1848 F pulseaudio /dev/snd/pcmC0D0c: bob1848 F...m puls
[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
I have the same issue. Everything was working fine on 18.04, it only stopped working after upgrading to 20.04. My phone (Android) can see the wifi network (hotspot), it connects to it, it says it is connected but there is no internet. I tried many different configurations, different software, but nothing worked. -- 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/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1795651] Re: ICU data package is grossly outdated
@anrdaemon not sure what you mean. ICU itself doesn't cut a release every time there's a timezone update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Status in icu package in Debian: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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 1864869] Re: ICU returns unexpected length for string
I added a comment to the PHP bug, I think it is working as designed. Please track ICU bugs at https://unicode-org.atlassian.net (project ICU) thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1864869 Title: ICU returns unexpected length for string Status in icu package in Ubuntu: New Status in php7.4 package in Ubuntu: Invalid Bug description: Calculating the grapheme string length for the word 'नमस्ते' returns 3 instead of 4. This version returns unexpected result of 3: ICU version 65.1 ICU Data version 65.1 ICU TZData version2019c ICU Unicode version 12.1 This version returns the expected result of 4: ICU version => 63.1 ICU Data version => 63.1 ICU TZData version => 2018e ICU Unicode version => 11.0 PHP says this is an upstream issue: https://bugs.php.net/bug.php?id=79308 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1864869/+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 1858092] Re: Network Manager not saving OpenVPN password
Can confirm that, after updating from the official repositories (Kubuntu 19.10), saving passwords "for this user only" works as intended again. Thanks! -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858092] Re: Network Manager not saving OpenVPN password
Is there an estimation when this will go from proposed to release? I'm working around it by looking up the connections' UID in the Network- Manager configuration and manually adding the corresponding entries in KWallet as of now.. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1859810] [NEW] som
Public bug reported: o audio esta mudo ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 15 08:28:41 2020 DistUpgraded: 2020-01-14 10:48:30,743 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0764] InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 3268 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=fd473502-2a31-400b-b303-9f46a74c2132 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-01-14 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 07F37C dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/25/2018:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3268 dmi.product.sku: 0764 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jan 13 20:38:33 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8758 vendor AOC xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages 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/1859810 Title: som Status in xorg package in Ubuntu: New Bug description: o audio esta mudo ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 15 08:28:41 2020 DistUpgraded: 2020-01-14 10:48:30,743 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0764] InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 3268 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=fd473502-2a31-400b-b303-9f46a74c2132 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-01-14 (0 days ago)
[Touch-packages] [Bug 104617] Re: CMI8738 5.1 center speaker is mute
CMI8738 is not well-supported by alsa. Running with a center channel volume issue (center volume constant, whatever the master volume). I found out that master volume worked only for front/rear channel, not center which stick to its initial value. Pulseaudio volume for separate channel are not effectless. amixer set no gauge for center/lfe, hence impossible to change it. Seems that with this chip, when in 5.1 mic is not available and Mic-in and center/lfe is on the same control. I don't know if alsa is wrong or if CMI8738 is just a crap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/104617 Title: CMI8738 5.1 center speaker is mute Status in alsa-utils package in Ubuntu: Invalid Bug description: Binary package hint: gnome-media I've spent the past couple of days researching this on the internet. I have a soundcard with the CMI8738 chipset, on a desktop running Ubuntu Edgy. In 5.1 mode all works, except the center-speaker (the subwoofer works, but not the center speaker) I can't see a separate control for the center speaker, only for Master and PCM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/104617/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
here's the log: Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: reg 0x10: [io 0xd000-0xd0ff] Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: reg 0x18: [mem 0x8240-0x82400fff 64bit] Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: reg 0x20: [mem 0xb210-0xb2103fff 64bit pref] Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: supports D1 D2 Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2: PCI bridge to [bus 02] Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2: bridge window [io 0xd000-0xdfff] Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2: bridge window [mem 0x8240-0x824f] Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2: bridge window [mem 0xb210-0xb21f 64bit pref] Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: [168c:0036] type 00 class 0x028000 Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: reg 0x10: [mem 0x8230-0x8237 64bit] Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: reg 0x30: [mem 0x8238-0x8238 pref] Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: supports D1 D2 Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot D3cold Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.3: PCI bridge to [bus 03] Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.3: bridge window [mem 0x8230-0x823f] Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12) *0, disabled. Okt 02 12:41:36 nathsom-X541SC kernel: gpio gpiochip1: (INT33FF:01): detected irqchip that is shared with multiple gpiochips: please fix the driver. Okt 02 12:41:36 nathsom-X541SC kernel: gpio gpiochip2: (INT33FF:02): detected irqchip that is shared with multiple gpiochips: please fix the driver. Okt 02 12:41:36 nathsom-X541SC kernel: gpio gpiochip3: (INT33FF:03): detected irqchip that is shared with multiple gpiochips: please fix the driver. Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: EC: interrupt unblocked Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: EC: event unblocked Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: \_SB_.PCI0.SBRG.EC0_: GPE=0x16, EC_CMD/EC_SC=0x66, EC_DATA=0x62 Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: \_SB_.PCI0.SBRG.EC0_: Used as boot DSDT EC to handle transactions and events Okt 02 12:41:36 nathsom-X541SC kernel: SCSI subsystem initialized Okt 02 12:41:36 nathsom-X541SC kernel: libata version 3.00 loaded. Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:02.0: vgaarb: setting as boot VGA device Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:02.0: vgaarb: bridge control possible Okt 02 12:41:36 nathsom-X541SC kernel: vgaarb: loaded Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: bus type USB registered Okt 02 12:41:36 nathsom-X541SC kernel: usbcore: registered new interface driver usbfs Okt 02 12:41:36 nathsom-X541SC kernel: usbcore: registered new interface driver hub Okt 02 12:41:36 nathsom-X541SC kernel: usbcore: registered new device driver usb Okt 02 12:41:36 nathsom-X541SC kernel: pps_core: LinuxPPS API ver. 1 registered Okt 02 12:41:36 nathsom-X541SC kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti Okt 02 12:41:36 nathsom-X541SC kernel: PTP clock support registered Okt 02 12:41:36 nathsom-X541SC kernel: EDAC MC: Ver: 3.0.0 Okt 02 12:41:36 nathsom-X541SC kernel: Registered efivars operations Okt 02 12:41:36 nathsom-X541SC kernel: PCI: Using ACPI for IRQ routing Okt 02 12:41:36 nathsom-X541SC kernel: PCI: pci_cache_line_size set to 64 bytes Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 0x0003f000-0x0003] Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 0x0009e000-0x0009] Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 0x1f00-0x1fff] Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 0x769b9018-0x77ff] Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM bu
[Touch-packages] [Bug 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
Wait I just realized what you meant, sorry. -- 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/1840817 Title: System won't suspend when closing the lid of my laptop, just shuts down Status in systemd package in Ubuntu: New Bug description: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU 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/systemd/+bug/1840817/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
How do i attach te command? do I do sudo pm-suspend && journalctl -k -b -1 ? -- 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/1840817 Title: System won't suspend when closing the lid of my laptop, just shuts down Status in systemd package in Ubuntu: New Bug description: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU 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/systemd/+bug/1840817/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
Well my lid actions say that the computer should go to sleep, but it doesn't. I also noticed I'm missing a sleep.sh in /etc/acpi. -- 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/1840817 Title: System won't suspend when closing the lid of my laptop, just shuts down Status in systemd package in Ubuntu: New Bug description: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU 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/systemd/+bug/1840817/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
ly: mask: 0x max_cycles: 0x171024fa93b, max_idle_ns: 440795253189 ns Sep 27 18:06:25 nathsom-X541SC kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3200.00 BogoMIPS (lpj=640) Sep 27 18:06:25 nathsom-X541SC kernel: pid_max: default: 32768 minimum: 301 Sep 27 18:06:25 nathsom-X541SC kernel: LSM: Security Framework initializing Sep 27 18:06:25 nathsom-X541SC kernel: Yama: becoming mindful. Sep 27 18:06:25 nathsom-X541SC kernel: AppArmor: AppArmor initialized Sep 27 18:06:25 nathsom-X541SC kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Sep 27 18:06:25 nathsom-X541SC kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) Sep 27 18:06:25 nathsom-X541SC kernel: process: using mwait in idle threads Sep 27 18:06:25 nathsom-X541SC kernel: Last level iTLB entries: 4KB 48, 2MB 0, 4MB 0 Sep 27 18:06:25 nathsom-X541SC kernel: Last level dTLB entries: 4KB 256, 2MB 16, 4MB 16, 1GB 0 Sep 27 18:06:25 nathsom-X541SC kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization Sep 27 18:06:25 nathsom-X541SC kernel: Spectre V2 : Mitigation: Full generic retpoline Sep 27 18:06:25 nathsom-X541SC kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch Sep 27 18:06:25 nathsom-X541SC kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls Sep 27 18:06:25 nathsom-X541SC kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier Sep 27 18:06:25 nathsom-X541SC kernel: MDS: Mitigation: Clear CPU buffers Sep 27 18:06:25 nathsom-X541SC kernel: Freeing SMP alternatives memory: 36K Sep 27 18:06:25 nathsom-X541SC kernel: TSC deadline timer enabled Sep 27 18:06:25 nathsom-X541SC kernel: smpboot: CPU0: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz (family: 0x6, model: 0x4c, stepping: 0x4) Sep 27 18:06:25 nathsom-X541SC kernel: Performance Events: PEBS fmt2+, 8-deep LBR, Silvermont events, 8-deep LBR, full-width counters, Intel PMU driver. Sep 27 18:06:25 nathsom-X541SC kernel: ... version:3 Sep 27 18:06:25 nathsom-X541SC kernel: ... bit width: 40 Sep 27 18:06:25 nathsom-X541SC kernel: ... generic registers: 2 Sep 27 18:06:25 nathsom-X541SC kernel: ... value mask: 00ff Sep 27 18:06:25 nathsom-X541SC kernel: ... max period: 007f Sep 27 18:06:25 nathsom-X541SC kernel: ... fixed-purpose events: 3 Sep 27 18:06:25 nathsom-X541SC kernel: ... event mask: 00070003 Sep 27 18:06:25 nathsom-X541SC kernel: rcu: Hierarchical SRCU implementation. Sep 27 18:06:25 nathsom-X541SC kernel: random: crng done (trusting CPU's manufacturer) Sep 27 18:06:25 nathsom-X541SC kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. Sep 27 18:06:25 nathsom-X541SC kernel: smp: Bringing up secondary CPUs ... Sep 27 18:06:25 nathsom-X541SC kernel: x86: Booting SMP configuration: Sep 27 18:06:25 nathsom-X541SC kernel: node #0, CPUs: #1 #2 #3 Sep 27 18:06:25 nathsom-X541SC kernel: smp: Brought up 1 node, 4 CPUs Sep 27 18:06:25 nathsom-X541SC kernel: smpboot: Max logical packages: 1 Sep 27 18:06:25 nathsom-X541SC kernel: smpboot: Total of 4 processors activated (12800.00 BogoMIPS) Sep 27 18:06:25 nathsom-X541SC kernel: devtmpfs: initialized Sep 27 18:06:25 nathsom-X541SC kernel: x86/mm: Memory block size: 128MB Sep 27 18:06:25 nathsom-X541SC kernel: PM: Registering ACPI NVS region [mem 0x0003f000-0x0003] (4096 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: PM: Registering ACPI NVS region [mem 0x7a098000-0x7ae29fff] (14229504 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns Sep 27 18:06:25 nathsom-X541SC kernel: futex hash table entries: 1024 (order: 4, 65536 bytes) Sep 27 18:06:25 nathsom-X541SC kernel: pinctrl core: initialized pinctrl subsystem Sep 27 18:06:25 nathsom-X541SC kernel: RTC time: 16:06:11, date: 2019-09-27 Sep 27 18:06:25 nathsom-X541SC kernel: NET: Registered protocol family 16 Sep 27 18:06:25 nathsom-X541SC kernel: audit: initializing netlink subsys (disabled) Sep 27 18:06:25 nathsom-X541SC kernel: audit: type=2000 audit(1569600371.048:1): state=initialized audit_enabled=0 res=1 Sep 27 18:06:25 nathsom-X541SC kernel: EISA bus registered Sep 27 18:06:25 nathsom-X541SC kernel: cpuidle: using governor ladder Sep 27 18:06:25 nathsom-X541SC kernel: cpuidle: using governor menu Sep 27 18:06:25 nathsom-
[Touch-packages] [Bug 1843333] [NEW] lvdisplay man page says to use -o help but that does not work.
Public bug reported: The lvdisplay man page suggesting something which does not work. The manpage says: Use -o help to view the list of all available fields. Doing this gives an error: $ sudo lvdisplay -o help /dev/datavg/lv1 Incompatible options selected. Run `lvdisplay --help' for more information. Expected: A correct manpage. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/184 Title: lvdisplay man page says to use -o help but that does not work. Status in lvm2 package in Ubuntu: New Bug description: The lvdisplay man page suggesting something which does not work. The manpage says: Use -o help to view the list of all available fields. Doing this gives an error: $ sudo lvdisplay -o help /dev/datavg/lv1 Incompatible options selected. Run `lvdisplay --help' for more information. Expected: A correct manpage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/184/+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 1840817] [NEW] System won't suspend when closing the lid of my laptop, just shuts down
Public bug reported: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1840817 Title: System won't suspend when closing the lid of my laptop, just shuts down Status in systemd package in Ubuntu: New Bug description: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage not
[Touch-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I also encountered that bug in 19.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1835474] [NEW] When running sudo apt-get remove libasound2 It deletes other apps including brave, gimp, audacity, and more
Public bug reported: I am using ubuntu 18.04 the version of the package was the most up to date, as I ran sudo apt-get install --reinstall libasound2 right before running sudo apt-get remove libasound2 This should not touch other applications, even if they were set up to use the library. It deleted several applications before I force closed it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasound2 1.1.3-5ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 4 20:10:09 2019 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libasound2-data 1.1.3-5ubuntu0.2 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 InstallationDate: Installed on 2018-06-22 (377 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic delete remove -- 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/1835474 Title: When running sudo apt-get remove libasound2 It deletes other apps including brave, gimp, audacity, and more Status in alsa-lib package in Ubuntu: New Bug description: I am using ubuntu 18.04 the version of the package was the most up to date, as I ran sudo apt-get install --reinstall libasound2 right before running sudo apt-get remove libasound2 This should not touch other applications, even if they were set up to use the library. It deleted several applications before I force closed it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasound2 1.1.3-5ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 4 20:10:09 2019 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libasound2-data 1.1.3-5ubuntu0.2 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 InstallationDate: Installed on 2018-06-22 (377 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1835474/+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 1825639] Re: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0]
I have once again removed the BIOS whitelist for the WLAN cards, and switched to a Wifi+Bluetooth Intel 7260 card. Testing with only this cards internal bluetooth seems to work well, and no skipping is going on. This is on a fresh Mint 19.1 install too, so perhaps the coexistence rule works well. I will test more to see if it reappears later on but it seems to work for now. Thanks for your help Daniel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825639 Title: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0] Status in bluez package in Ubuntu: Invalid Bug description: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+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 1830340] Re: icu 63.2 makes acorn ftbfs (*** stack smashing detected ***: terminated)
There's not a lot of information here as to what operation was being done when it failed. Note that we did get a 63.2 bug https://unicode- org.atlassian.net/browse/ICU-20603 which also sounds like corruption. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1830340 Title: icu 63.2 makes acorn ftbfs (*** stack smashing detected ***: terminated) Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: New Bug description: https://launchpad.net/ubuntu/+source/acorn/5.5.3+ds3-3/+build/16839533 As you can see, the package is now FTBFS. I traced down this to be an icu problem, by starting from a disco chroot and then manually upgrading packages until I got the icu update. I can confirm also icu from debian experimental (and Debian chroot) has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1830340/+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 973088] Re: tracker-miner-fs crashed with SIGABRT in g_assertion_message()
Started to show up with 19.04 for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/973088 Title: tracker-miner-fs crashed with SIGABRT in g_assertion_message() Status in tracker package in Ubuntu: Confirmed Status in tracker package in Fedora: Won't Fix Bug description: Description: Ubuntu precise (development branch) Release: 12.04 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: tracker-miner-fs 0.14.0-2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Wed Apr 4 10:33:07 2012 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2) ProcCmdline: /usr/lib/tracker/tracker-miner-fs Signal: 6 SourcePackage: tracker Title: tracker-miner-fs crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/973088/+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 1825735] Re: Display is corrupted after waking from sleep
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Another thing that I have noticed is that this problem only arises when I click suspend or close the lid. If the laptop naturally goes sleep then this problem doesn't occur. -- 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/1825735 Title: Display is corrupted after waking from sleep Status in xorg package in Ubuntu: New Bug description: After I shut the lid of the laptop and turn it back on, I see my open windows for a second and then the lock screen appears. When I log in, my wallpaper is replaced with the image I have attached. This image is also shown in the lock screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 13:58:09 2019 DistUpgraded: 2019-04-18 21:28:53,352 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9] InstallationDate: Installed on 2019-04-16 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc1xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago) dmi.bios.date: 01/12/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/12/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.sku: 2SS26UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825735/+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 1825639] Re: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0]
I will report back once I have had time to re-modify my BIOS to remove the WiFi whitelist, and then test my Intel 7260 on there with coexistance (I'm sure the iwlwifi implements coexistence on all wifi + bt cards, but its there for sure on my one anyway). This may take a few weeks, but thanks for helping me out Daniel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825639 Title: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0] Status in bluez package in Ubuntu: Invalid Bug description: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+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 1825639] Re: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0]
I have disabled Wi-Fi and tested a buffered video in Chrome on Youtube (which is where I stream my music mostly from, though the stuttering and lag was present in all other applications too), and there seems to be almost no lagging or clicking at all. There was a lag of perhaps 100 ms only, but nothing substantial and also not near as frequent as with Wi- Fi on. I then tested again with Wi-Fi on, and it is stuttering again. On my system, I use an Intel 6205 Wi-Fi card, but this card does not have bluetooth on the same card. As seen above, my T430 has a build in bluetooth USB device (Broadcom BCM20702). Because of this, any online solutions about Wifi/Bt coexistance may not apply, and I have even tried them to no effect (Adding modprobe options to enable coexistance on or off in the iwlwifi driver) Many thanks for looking into it. My rfkill list output when wifi was disabled (software switch, not hardware) penguin@thinkpadT430 ~ $ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825639 Title: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0] Status in bluez package in Ubuntu: Incomplete Bug description: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+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 1825735] Re: Display is corrupted after waking from sleep
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 I read the description of bug 1809407 and I don't think this is the same bug. With my problem, I can fix everything by refreshing the screen (alt+f2 'r') but in the other bug, you have to sleep and wake again. My bug also shows me the unlock app, unlike the other bug. Only the wallpaper is changed for me and everything else works fine. -- 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/1825735 Title: Display is corrupted after waking from sleep Status in xorg package in Ubuntu: New Bug description: After I shut the lid of the laptop and turn it back on, I see my open windows for a second and then the lock screen appears. When I log in, my wallpaper is replaced with the image I have attached. This image is also shown in the lock screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 13:58:09 2019 DistUpgraded: 2019-04-18 21:28:53,352 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9] InstallationDate: Installed on 2019-04-16 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc1xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago) dmi.bios.date: 01/12/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/12/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.sku: 2SS26UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825735/+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 1825735] [NEW] Display is corrupted after waking from sleep
Public bug reported: After I shut the lid of the laptop and turn it back on, I see my open windows for a second and then the lock screen appears. When I log in, my wallpaper is replaced with the image I have attached. This image is also shown in the lock screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 13:58:09 2019 DistUpgraded: 2019-04-18 21:28:53,352 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9] InstallationDate: Installed on 2019-04-16 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc1xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago) dmi.bios.date: 01/12/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/12/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.sku: 2SS26UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption disco ubuntu ** Attachment added: "Picture of what happens to the display" https://bugs.launchpad.net/bugs/1825735/+attachment/5257611/+files/Screenshot%20from%202019-04-20%2017-06-53.png ** Summary changed: - Display is corrupted + Display is corrupted after waking from sleep -- 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/1825735 Title: Display is corrupted after waking from sleep Status in xorg package in Ubuntu: New Bug description: After I shut the lid of the laptop and turn it back on, I see my open windows for a second and then the lock screen appears. When I log in, my wallpaper is replaced with the image I have attached. This image is also shown in the lock screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA U
[Touch-packages] [Bug 1825639] [NEW] Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound.
Public bug reported: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825639 Title: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. Status in bluez package in Ubuntu: New Bug description: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post t
[Touch-packages] [Bug 1333024] Re: Bluetooth audio Underruns, dropouts or crackling sound
Same behaviour here - very very similar to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 but the issue persists. I have a T430, Xubuntu 18.10, inbuilt bluetooth, and pulseaudio 12.2. This makes it very hard to use headphones and wifi at the same time. -- 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/1333024 Title: Bluetooth audio Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Confirmed Bug description: My bluetooth performance when connected to an audio device is very poor on my Lenovo T440s. There are multiple problems when I connect to my logitech device: 1) It often disconnects unexpectedly. It will connect for 2-5 seconds before disconnecting. This happens over and over with no messages in dmesg. 2) If I can get it to connect, the audio device is listed in the sound settings only about 50% of the time. I have to disconnect, restart bluetooth (\etc\init.d\bluetooth restart) and try again. 3) If I can get it playing, the audio lags by ~10s and is really, really chopped up. Totally unintelligible. The things I know which might help: Computer Type: Lenovo T440s Operating system: Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty Linux version : 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Bluetooth card: Network controller: Intel Corporation Wireless 7260 (rev 83) Pulseaudio version: pulseaudio 4.0 - I don't think it's pulse audio as the daemon won't start: $ pulseaudio --check $ pulseaudio -D E: [pulseaudio] main.c: Daemon startup failed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seth 2220 F pulseaudio /dev/snd/controlC1: seth 2220 F pulseaudio /dev/snd/pcmC1D0c: seth 2220 F...m pulseaudio CurrentDesktop: Unity Date: Sun Jun 22 14:29:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-21 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: (EE)Logitech Adapter Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [(EE)Logitech Adapter, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET64WW (2.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ006HUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ006HUS dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1333024/+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 1821343] Re: slapd process failure is not detected by systemd
@slashd I don't think we need anything special for systemd in the
debian/{control,rules} files, since we're not shipping full systemd
support with this. The slapd service is still handled by systemd-sysv-
generator(8), so there's no service units that we need to include or
activate in dh_systemd rules.
To make sure things are working fine I went ahead and tested a package
upgrade with this debdiff:
ubuntu@disco:~$ dpkg -l | grep slapd
ii slapd 2.4.47+dfsg-3ubuntu1amd64
OpenLDAP server (slapd)
ubuntu@disco:~$ sudo apt-get --only-upgrade install slapd
ubuntu@disco:~$ dpkg -l | grep slapd
ii slapd 2.4.47+dfsg-3ubuntu2amd64
OpenLDAP server (slapd)
ubuntu@disco:~$ systemctl cat slapd
# /run/systemd/generator.late/slapd.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/slapd
Description=LSB: OpenLDAP standalone server (Lightweight Directory Access
Protocol)
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=remote-fs.target
After=network-online.target
Wants=network-online.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/init.d/slapd start
ExecStop=/etc/init.d/slapd stop
# /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf
[Service]
Type=forking
RemainAfterExit=no
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not detected by systemd
Status in openldap package in Ubuntu:
Confirmed
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Cosmic:
Confirmed
Status in openldap package in Debian:
New
Bug description:
[Impact]
Systemd service reports slapd as active, even though it may have failed
[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service
by generating the unit file using the systemd-sysv-generator(8) utility. The
generated unit file contains Type=forking and RemainAfterExit=yes directives.
If the slapd daemon process exits due to some failure (e.g., it
receives a SIGTERM or SIGKILL), the failure is not detected properly
by systemd. The service is still reported as active even though the
child (daemon) process has exited with a signal.
We can easily fix this by including a proper systemd service file for
slapd in the openldap package. Since the init.d script already does
most of the necessary work (parsing configs, setting up PID files,
etc.), we don't need anything complicated for the systemd unit file.
Just making sure that RemainAfterExit is set to "no" makes the systemd
service behave in the expected way.
[Test Case]
1) Deploy a disco container
$ lxc launch images:ubuntu/disco disco
2) Install slapd
ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y
3) Verify that slapd is running with the auto-generated service
ubuntu@disco:~$ systemctl status slapd
● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory
Access Protocol)
Loaded: loaded (/etc/init.d/slapd; generated)
Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited,
status=0/SUCCESS)
Tasks: 3 (limit: 4915)
Memory: 712.6M
CGroup: /system.slice/slapd.service
└─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u
openldap -F /etc/ldap/slapd.d
4) SIGKILL the slapd process (PID is displayed in systemctl status output)
ubuntu@disco:~$ sudo kill -9 1109
5) Check if systemd service lists slapd as still active, even though it was
terminated
ubuntu@disco:~$ systemctl status slapd
● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory
Access Protocol)
Loaded: loaded (/etc/init.d/slapd; generated)
Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited,
status=0/SUCCESS)
[Regression Potential]
The regression potential for this fix should be very low, if we keep the new
systemd unit file close to the one generated by systemd-sysv-generator(8). The
only significant change would be the RemainAfterExit directive, and this should
make the slapd service behave like a "normal" forking service. Nonetheless,
we'll perform scripted test runs to make sure no regressions arise.
To manage notifications about this bug go to
[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd
** Bug watch added: Debian Bug tracker #926657 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926657 ** Also affects: openldap (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926657 Importance: Unknown Status: Unknown ** Patch added: "lp1821343-disco.debdiff" https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254240/+files/lp1821343-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Status in openldap package in Debian: Unknown Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
I've been doing some research on how we could implement a proper systemd
unit file for slapd, and came up with interesting results.
There are a number of options that we can pass to the slapd service that will
give us lots of troubles on an "idiomatic" service file. To give some examples:
- The PID file can be directly obtained from /etc/default/slapd if set, or it
has to be parsed from /etc/ldap/slapd.d or /etc/ldap/slapd.conf. The /etc/ldap
files don't follow the /etc/default syntax, so we can't just pass them with
"EnvironmentFile=" in the systemd service. We would have to parse those files
as is currently done by the init script.
- slapd has the "-f" and "-F" flags that can be used to specify a config file or
directory, respectively. It does not accept both at the same time, but
SLAPD_CONF in /etc/default/slapd allows either a file or directory. The init
script will figure out which of those is set, and pass the correct flag
accordingly. I don't see a simple way of doing this in systemd without either
polluting the SLAPD_CONF option with the necessary flag, or delegating it to a
helper script which would check whether the option meant a file or a
directory.
- The slapd.conf file is used by other related tools (see slapd.conf(5)), which
prevents us from pulling some of the options to another centralized file
without also updating these tools
I hoped that the upstream package would have some insight on the proper
way of writing the service file, but unfortunately it seems that
upstream Openldap devs are very much against the idea of shipping them
(be they sysv-init or systemd files). There are some discussions on the
openldap lists, one of which deals specifically with adding systemd
support for slapd [0]. From that discussion, it's clear that upstream
openldap is not ready to provide the necessary systemd files out-of-the-
box, even when approached with relevant patches.
I also checked how CentOS implement their slapd.service file since they don't
seem to run into these problems. They don't use an autogenerated unit file, and
have a proper one instead [1]. From what I've checked, this is easier for them
for two reasons:
1) The CentOS configs for slapd are much simpler than what we have in
Debian/Ubuntu (their defaults don't include most of the options that we do)
2) They use helper scripts for the funky parsing we have in the sysv-init
script ("ExecStartPre=/usr/libexec/openldap/check-config.sh", which also
invokes some other helper scripts)
On Debian/Ubuntu, the autogenerated unit file for slapd uses the sysv-init
script as a "shim" to manage the service, which makes it possible to keep the
whole config-parsing insanity consistent between sysv-init and systemd.
It's not the most elegant solution, but for now I believe it makes sense to
include an override file for the "RemainAfterExit=" option until we have a
native systemd unit file for slapd (similar to what was done for apache2 in bug
1488962 mentioned by Ryan Tandy).
[0] https://www.openldap.org/its/index.cgi/Incoming?id=8707
[1] https://git.centos.org/blob/rpms!openldap.git/c7/SOURCES!slapd.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not detected by systemd
Status in openldap package in Ubuntu:
Confirmed
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Cosmic:
Confirmed
Bug description:
[Impact]
Systemd service reports slapd as active, even though it may have failed
[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service
by generating the unit file using the systemd-sysv-generator(8) utility. The
generated unit file contains Type=forking and RemainAfterExit=yes directives.
If the slapd daemon process exits due to some failure (e.g., it
receives a SIGTERM or SIGKILL), the failure is not detected properly
by systemd. The service is still reported as active even though the
child (daemon) process has exited with a signal.
We can easily fix this by including a proper systemd service file for
slapd in the openldap package. Since the init.d script already does
most of the necessary work (parsing configs, setting up PID files,
etc.), we don't need anything complicated for the systemd unit file.
Just making sure that RemainAfterExit is set to "no" makes the systemd
service behave in the expected way.
[Test Case]
1) Deploy a disco container
$ lxc launch images:ubuntu/disco disco
2) Install slapd
ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y
3) Verify that slapd is running with the auto-generated service
ubuntu@disco:~$ systemctl status slapd
● slapd.service -
[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd
The sysv init script does some funky parsing of configuration files that might give us some trouble in an independent service file. I'll check if we can't work around that and do away with the sysv init script altogether, otherwise we might as well go with the drop-in override since the new service wouldn't be much different from it. ** Patch removed: "debdiff for disco" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248489/+files/lp1821343-disco.debdiff ** Patch removed: "debdiff for cosmic" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248490/+files/lp1821343-cosmic.debdiff ** Patch removed: "debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248492/+files/lp1821343-bionic.debdiff ** Patch removed: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248493/+files/lp1821343-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
** Patch added: "debdiff for disco" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248489/+files/lp1821343-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
** Patch added: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248493/+files/lp1821343-xenial.debdiff ** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
** Patch added: "debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248492/+files/lp1821343-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
** Patch added: "debdiff for cosmic" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+attachment/5248490/+files/lp1821343-cosmic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] Re: slapd process failure is not detected by systemd
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+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 1821343] [NEW] slapd process failure is not detected by systemd
Public bug reported: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. ** Affects: openldap (Ubuntu) Importance: Medium Assignee: Heitor R. Alves de Siqueira (halves) Status: Confirmed ** Affects: openldap (Ubuntu Xenial) Importance: Medium Assignee: Heitor R. Alves de Siqueira (halves) Status: Confirmed ** Affects: openldap (Ubuntu Bionic) Importance: Medium Assignee: Heitor R. Alves de Siqueira (halves) Status: Confirmed ** Affects: openldap (Ubuntu Cosmic) Importance: Medium Assignee: Heitor R. Alves de Siqueira (halves) Status: Confirmed ** Tags: sts ** Also affects: openldap (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu Xenial) Status: New => Confirmed ** Changed in: openldap (Ubuntu Bionic) Status: New => Confirmed ** Changed in: openldap (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: openldap (Ubuntu Xenial) Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves) ** Changed in: openldap (Ubuntu Bionic) Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves) ** Changed in: openldap (Ubuntu Cosmic) Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves) ** Changed in: openldap (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: openldap (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: openldap (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Cosmic: Confirmed Bug description: [Impact] System
[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
I've faced the same issue, but in a recently installed Ubuntu Desktop 18.04 on a Asus K46CB. I tried @pujan fix but it didn't work. Several minutes later I've tried to type: ~$ cat /etc/resolv.conf following tips from here (Brazilian forum): https://www.vivaolinux.com.br/topico/Iniciantes-no-Linux/Update-no-Ubuntu-1604-LTS This command input in that thread was in fact intended to see the DNS config, but just the execution of the command seems to solve the guy problem. So I tried to input the same command and after I've (magically) also succeed to update the packages. There are two possible misconceptions here: - The kernel was already updating the packages because of the Ubuntu fresh install and apt in some way get confused; - Or it was a communication/network/ISP problem that got fixed by itself. As I didn't try to directly update the packages after the "several minutes" and type the cat command instead, it's not possible to know if it really was the cat command or the network that got fixed. Also it's kind of weird that the simple fact of checking a config file solve a problem, right? But it is kind of huge coincidence that two different computers in different years (2017 and 2019) got the same fix after that command, isn't it? ** Attachment added: "Outputs" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+attachment/5245772/+files/apt_error.txt -- 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/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS Status in apt package in Ubuntu: Invalid Bug description: Hi, I'm getting weird Hashes mismatch error while trying to update Ubuntu server 18.04.1 LTS server. The error I'm receiving is as follows. $ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [2,676 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [277 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [105 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [157 kB] Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [71.0 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [3,772 B] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,376 B] Err:14 http://download.webmin.com/download/repository sarge InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out Fetched 329 kB in 30s (10.9 kB/s) Reading package lists... Done W: Failed to fetch http://download.webmin.com/download/repository/dists/sarge/InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + W: Some index files failed to download. They have been ignored, or old ones used instea
[Touch-packages] [Bug 1818456] [NEW] Horrible video experience with Intel Graphic after new fresh install
Public bug reported: Since my new fresh install of Ubuntu 18.04 I can't have a good experience. Use a simple gEdit is impossible because the text area is not showed in a white background but "cloning" everything that were in that screen position curiously it not happen with Leafpad editor. But occur with Gnome-claculator. My LibreOffice can't show their buttons in any toolbar. I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf /graphics-drivers) expcting some improve but nothing change. Unhappily. Some years ago I have this same experience in Ubuntu 16.04 but it was over (I don't know how) and even after a dist-upgrade to 18.04 it is OK, but now I had to to new install and the bug is here. Unhappily. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 22:17:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-01 (183 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H87M-HD3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-45-generic root=UUID=3c502856-3b66-4815-8747-59e0fce0d335 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1902261830.d54e54~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1903030730.cb4e3e~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1903030730.cb4e3e~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1902111932.15697e~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1903011933.6afed3~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1901290732.ec2b45~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu ** Attachment added: "Libreoffice Toolbar" https://bugs.launchpad.net/bugs/1818456/+attachment/5243218/+files/Captura%20de%20tela%20de%202019-03-03%2022-28-14.png -- 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/1818456 Title: Horrible video experience with Intel Graphic after new fresh install Status in xorg package in Ubuntu: New Bug description: Since my new fresh install of Ubuntu 18.04 I can't have a good experience. Use a simple gEdit is impossible because the text area is not showed in a white background but "cloning" everything that were in that screen position curiously it not happen with Leafpad editor. But occur with Gnome-claculator. My LibreOffice can't show their buttons in any toolbar. I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf /g
[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file
There are two armhf autopkgtest regressions for apt-1.0.1ubuntu2.20, in tests for apt [0] and autopkgtest [1]. From the autopkgtest pages we can see that these regressions were introduced long before this SRU, so it seems like a long standing issue unrelated to this patch. [0] http://autopkgtest.ubuntu.com/packages/a/apt/trusty/armhf [1] http://autopkgtest.ubuntu.com/packages/a/autopkgtest/trusty/armhf -- 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/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, ... apt | 1.0.1ubuntu2.19 | trusty-security | source, ... apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... apt | 1.2.10ubuntu1 | xenial | source, ... apt | 1.6.1 | bionic | source, ... apt | 1.7.0 | cosmic | source, ... apt | 1.8.0~rc2 | disco| source, ... [Test Case] 1) Deploy a Trusty (14.04 LTS) vm w/ 128M 2) Fetch latest stress-ng src code 2.1) git clone git://kernel.ubuntu.com/cking/stress-ng 2.2) cd stress-ng 2.3) make clean 2.4) make 3) Stress the mmap() with stress-ng 3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90% 4) Disable swap (if any) 4.1) swapoff -a 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done ... vsftpd: Installed: (none) Candidate: 3.0.2-1ubuntu2.14.04.1 Version table: 3.0.2-1ubuntu2.14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.0.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) ... [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815129/+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 1815129] Re: apt segfaults when generating cache file
Tested on apt-1.0.1ubuntu2.20 from trusty-proposed. Tried reproducing according to the test case from description, and verified that apt-cache does not crash: ubuntu@apt-stress:~/stress-ng$ dpkg -l | grep apt ii apt 1.0.1ubuntu2.20 (while having stress-ng running) ubuntu@apt-stress:~/stress-ng$ for i in `seq 1 1`;do apt-cache policy vsftpd;done E: Couldn't make mmap of 30021560 bytes - MMap-mmap (12: Cannot allocate memory) E: The package lists or status file could not be parsed or opened. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done-trusty ** Tags added: verification-needed -- 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/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, ... apt | 1.0.1ubuntu2.19 | trusty-security | source, ... apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... apt | 1.2.10ubuntu1 | xenial | source, ... apt | 1.6.1 | bionic | source, ... apt | 1.7.0 | cosmic | source, ... apt | 1.8.0~rc2 | disco| source, ... [Test Case] 1) Deploy a Trusty (14.04 LTS) vm w/ 128M 2) Fetch latest stress-ng src code 2.1) git clone git://kernel.ubuntu.com/cking/stress-ng 2.2) cd stress-ng 2.3) make clean 2.4) make 3) Stress the mmap() with stress-ng 3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90% 4) Disable swap (if any) 4.1) swapoff -a 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done ... vsftpd: Installed: (none) Candidate: 3.0.2-1ubuntu2.14.04.1 Version table: 3.0.2-1ubuntu2.14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.0.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) ... [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815129/+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 1815129] Re: apt segfaults when generating cache file
** Description changed: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt - apt | 1.0.1ubuntu2| trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el - apt | 1.0.1ubuntu2.19 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el - apt | 1.0.1ubuntu2.19 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el - apt | 1.2.10ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x - apt | 1.6.1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x - apt | 1.7.0 | cosmic | source, amd64, arm64, armhf, i386, ppc64el, s390x - apt | 1.8.0~rc2 | disco| source, amd64, arm64, armhf, i386, ppc64el, s390x - + apt | 1.0.1ubuntu2| trusty | source, ... + apt | 1.0.1ubuntu2.19 | trusty-security | source, ... + apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... + apt | 1.2.10ubuntu1 | xenial | source, ... + apt | 1.6.1 | bionic | source, ... + apt | 1.7.0 | cosmic | source, ... + apt | 1.8.0~rc2 | disco| source, ... [Test Case] - Unfortunately, this issue is not easy to reproduce. It seems to trigger randomly when "apt-cache policy" is called on a system under memory pressure, triggering the failure path in the mmap() allocations. + 1) Deploy a Trusty (14.04 LTS) vm w/ 128M + 2) Fetch latest stress-ng src code + 2.1) git clone git://kernel.ubuntu.com/cking/stress-ng + 2.2) cd stress-ng + 2.3) make clean + 2.4) make + 3) Stress the mmap() with stress-ng + 3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90% + 4) Disable swap (if any) + 4.1) swapoff -a + 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done + ... + vsftpd: + Installed: (none) + Candidate: 3.0.2-1ubuntu2.14.04.1 + Version table: + 3.0.2-1ubuntu2.14.04.1 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 3.0.2-1ubuntu2 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Segmentation fault (core dumped) + Segmentation fault (core dumped) + Segmentation fault (core dumped) + Segmentation fault (core dumped) + Segmentation fault (core dumped) + Segmentation fault (core dumped) + ... [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. -- 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/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt package in Debian: Unknown Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, ... apt | 1.0.1ubuntu2.19 | trusty-security | source, ... apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... apt | 1.2.10ubuntu1 | xenial | source, ... apt | 1.6.1 | bionic
[Touch-packages] [Bug 1815129] [NEW] apt segfaults when generating cache file
Public bug reported: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el apt | 1.0.1ubuntu2.19 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el apt | 1.0.1ubuntu2.19 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el apt | 1.2.10ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x apt | 1.6.1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.7.0 | cosmic | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.8.0~rc2 | disco| source, amd64, arm64, armhf, i386, ppc64el, s390x [Test Case] Unfortunately, this issue is not easy to reproduce. It seems to trigger randomly when "apt-cache policy" is called on a system under memory pressure, triggering the failure path in the mmap() allocations. [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Trusty) Importance: Undecided Status: 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/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: New Status in apt source package in Trusty: New Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el apt | 1.0.1ubuntu2.19 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el apt | 1.0.1ubuntu2.19 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el apt | 1.2.10ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x apt | 1.6.1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.7.0 | cosmic | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.8.0~rc2 | disco| source, amd64, arm64, armhf, i386, ppc64el, s390x [Test Case] Unfortunately, this issue is not easy to reproduce. It seems to trigger randomly when "apt-cache policy" is called on a system under memory pressure, triggering the failure path in the mmap() allocations. [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://
[Touch-packages] [Bug 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
> upstream to solve the bug By upstream this sounds like (as I understand it) it's the ICU consumers that need to be updated to not use icu-config, you shouldn't be waiting on ICU itself. I just want to clarify what you mean, because I'm not aware of any blocker in ICU. (ICU shipped https://github.com/unicode- org/icu/pull/13 in version 63.1). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: New Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
Heh, of course jackpoll_ms=40 doesn't work, anything below 50 ms is
ignored:
https://github.com/torvalds/linux/blob/master/sound/pci/hda/hda_intel.c#L1720
With jackpoll_ms=60 I'm seeing intervals of slightly above 60 ms, so
this makes sense.
--
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/874535
Title:
Volume Slider Jumps, due to rapidly changing hardware jack sense state
Status in alsa-driver package in Ubuntu:
Triaged
Bug description:
In Oneiric Release, The volume slider randomly jump down a notch or
two for fraction of a second, even when there is no audio playing on
the system. If mute is selected, the menu will quickly flip out of
mute mode and back again. This change actually affects the audio
output, resulting in pops correlated with the volume changes.
nVidia GF106 Audio Controller
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jfrorie9959 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,1462522c,00100302'
Controls : 35
Simple ctrls : 20
Card2.Amixer.info:
Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card2.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: pulseaudio 1:1.0-0ubuntu3.1
PackageArchitecture: amd64
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Tags: oneiric running-unity
Uname: Linux 3.0.0-14-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X58A-GD45 (MS-7522)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 5.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
dmi.product.name: MS-7522
dmi.product.version: 5.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
Same here, Gigabyte GA-B250M-DS3H with HDA Intel PCH, ALC887-VD. Ubuntu
18.04.
On my machine, once this starts happening it survives a reboot but goes
away for a while after a _cold_ reboot.
Clicks every few seconds and debounce might indeed be a workaround (~20
ms plug/unplug in my case):
$ ./pulseaudio - --log-time=1 2>&1 | grep -P 'Front Headphone.*is now'
( 0.120| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now unplugged
( 3.134| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now plugged in
( 3.155| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now unplugged
( 5.161| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now plugged in
( 5.182| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now unplugged
( 6.324| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now plugged in
( 6.345| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone
Jack' is now unplugged
I'm yet to see anything other than 21-22 ms. I set jackpoll_ms=40 in
snd_hda_intel options but still seeing the same plug/unplug interval.
Similar reports on this pulseaudio bug:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084
--
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/874535
Title:
Volume Slider Jumps, due to rapidly changing hardware jack sense state
Status in alsa-driver package in Ubuntu:
Triaged
Bug description:
In Oneiric Release, The volume slider randomly jump down a notch or
two for fraction of a second, even when there is no audio playing on
the system. If mute is selected, the menu will quickly flip out of
mute mode and back again. This change actually affects the audio
output, resulting in pops correlated with the volume changes.
nVidia GF106 Audio Controller
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jfrorie9959 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,1462522c,00100302'
Controls : 35
Simple ctrls : 20
Card2.Amixer.info:
Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card2.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: pulseaudio 1:1.0-0ubuntu3.1
PackageArchitecture: amd64
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Tags: oneiric running-unity
Uname: Linux 3.0.0-14-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X58A-GD45 (MS-7522)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 5.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
dmi.product.name: MS-7522
dmi.product.version: 5.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
Reoccurred again on the next day after a cold reboot. Once it starts happening, pulseaudio doesn't need to be running to see the issue (acpi_listen plug/unplug events) so this is likely lower-level than pulseaudio. Similar alsa-driver thread: https://bugs.launchpad.net/ubuntu/+source /alsa-driver/+bug/874535 -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Brad (apeitheo) Thanks that solved this problem. aravind@comp:~$ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Sun 2018-12-09 16:24:21 IST; 2min 32s ago Process: 1686 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=0/SUCCESS) Main PID: 1686 (code=exited, status=0/SUCCESS) Dec 09 16:24:17 comp systemd[1]: Starting Process error reports when automatic reporting is enabled... Dec 09 16:24:21 comp whoopsie-upload-all[1686]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Dec 09 16:24:21 comp whoopsie-upload-all[1686]: All reports processed Dec 09 16:24:21 comp systemd[1]: Started Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
Nope, the same issue reappeared on my machine on the next day. So it was not due to the cabling. Ubuntu 18.04 by the way. It persisted across multiple reboots, but disappeared when I turned the machine off and then immediately turned it back on again. Hardware issue? I guess hdajackretask is the way to go. -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
I ~think~ I just fixed this issue on my PC (GA-B250M-DS3H with HDA Intel PCH, ALC887-VD). Symptoms just like described on this thread: - repeated "Jack 'Front Headphone Jack' is now plugged in" / plugged out messages in pulseaudio logs - acpi_listen showing plug/unplug events - once headphones are plugged into the front jack, issue stops - hdajackretask works as a workaround - side effects: audio stutters, graphics freezes for a split second (looks very much like video card lagging). OSD notifications turned off so I didn't have those. I had the front panel audio cable go behind the motherboard, attached to the other cables in the case. Once I re-connected the cable to go separately from everything else, the problem seems to have completely disappeared. Crosstalk with other cables / motherboard seems like a likely root cause. `pulseaudio - --log-time=1` had 'plugged in' followed by 'plugged out' at very close timestamps (~20ms). Debouncing could avoid the side effects and hide the problem. -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1799693] Re: Stable libopus-1.3 released
I can try doing this myself if someone wants to point me to the documentation of rebasing/repacking/etc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opus in Ubuntu. https://bugs.launchpad.net/bugs/1799693 Title: Stable libopus-1.3 released Status in opus package in Ubuntu: New Bug description: Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now outdated and technically marked as a beta. http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1799693/+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 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
I dont know how Daemo00 manage to start sudo systemctl start whoopsie.service shows noting and when I run service apport-autoreport status. It shows same error: ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-11-06 15:36:56 IST; 35min ago Process: 1491 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=1/FAILURE) Main PID: 1491 (code=exited, status=1/FAILURE) Nov 06 15:36:52 comp systemd[1]: Starting Process error reports when automatic reporting is enabled... Nov 06 15:36:56 comp whoopsie-upload-all[1491]: ERROR: whoopsie is not running Nov 06 15:36:56 comp systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE Nov 06 15:36:56 comp systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. Nov 06 15:36:56 comp systemd[1]: Failed to start Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1799693] [NEW] Stable libopus-1.3 released
Public bug reported: Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now outdated and technically marked as a beta. http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html ** Affects: opus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opus in Ubuntu. https://bugs.launchpad.net/bugs/1799693 Title: Stable libopus-1.3 released Status in opus package in Ubuntu: New Bug description: Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now outdated and technically marked as a beta. http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1799693/+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 1752269] Re: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
primary error is no "com.ubuntu.apport.apport-gtk-root", the second error came in sepperate pop-up for "linux-image- extra-4.13.0.40~16.04.1". This indicates bad support for an AMD 7tr gen processor on my DELL computer. -- 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/1752269 Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: sudo dpkg --configure -a executed the bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Feb 28 09:44:33 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2018-02-27 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 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/1752269/+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 1795764] [NEW] systemd: core: Fix edge case when processing /proc/self/mountinfo
Public bug reported: >From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1795764 Title: systemd: core: Fix edge case when processing /proc/self/mountinfo Status in systemd package in Ubuntu: Confirmed Bug description: From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795764/+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 1795651] Re: ICU data package is grossly outdated
Hi. ICU tz data is kept available such as https://github.com/unicode-org /icu-data/tree/master/tzdata/icunew/2018e/44 ( look in the le / be / ee for different endianness, ee is ebcdic ) . It could be rebuilt into an updated icu package. Or, it could be side loaded (as a separate data file loaded at runtime). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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
