[Touch-packages] [Bug 2016318] Re: free command: in Italian header is misaligned and wrongly translated
In 22.04 the translation was better, it is the case to revert to that? enzotib@ubuntu-enzo:~$ free -m totale utilizzato buff/cache condivisa libera disponibile Mem: 156707635 53811387495 6561 Swap: 31999 9 31990 enzotib@ubuntu-enzo:~$ LC_ALL=C free -m totalusedfree shared buff/cache available Mem: 156707634 53911387495 6561 Swap: 31999 9 31990 Still "buff/cache" and "libera" should be exchanged, and the words should be right aligned with numbers. Also use feminine for "utilizzato" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2016318 Title: free command: in Italian header is misaligned and wrongly translated Status in Ubuntu Translations: Confirmed Status in procps package in Ubuntu: Confirmed Bug description: free command: in Italian header is misaligned and wrongly translated gratuiti is 'for free' or 'gratis' or 'toll free' 'free' may be translated with 'liberi' total = totali ... ok used = usati ... ok free = liberi ... to be changed shared = condivisi ... ok buff/cache ... ok available = disponibili ... ok corrado@corrado-n4-ll-beta:~$ free totalusedfree shared buff/cache available Mem:16151400 223667211599888 517412 3171440 13914728 Swap:8388604 0 8388604 corrado@corrado-n4-ll-beta:~$ corradi@corrado-n4-ll-beta:~$ free buff/cache condivisi gratuiti totali utilizzati disponibili Mem:16151400 175200411850636 333144 3227540 14399396 Swap:8388604 0 8388604 corradi@corrado-n4-ll-beta:~$ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: procps 2:4.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 18:34:49 2023 InstallationDate: Installed on 2023-03-31 (14 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2016318/+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 1907154] [NEW] application menu of pdf and text documents is not visible when the window is resized and made smaller
Public bug reported: 1. When opening a text document (with standard text editor) or a pdf with "Pdf viewer" and clicking on the "menu" icon at the top right of the window, the menu shows up correctly. 2.If I resize the window making it shorter than the menu itself, I would expect the menu to remain fully visible or at least in some way graphically accessible (resized or scrollable). 3. Instead, I can no more see some options of the menu: a part of it is not visible (as it was graphically cut). So you can't see nor select with the mouse the non-visible part of the menu. 4. I noticed you can navigate and select the options (both visible or non-visible) of the menu using arrows and Enter from the keyboard. However this is not a solution because you still cannot see a part of the menu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 23:33:35 2020 DistUpgraded: 2020-12-01 09:42:59,803 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: btusb, 4.0, 5.4.0-54-generic, x86_64: installed btusb, 4.0, 5.4.0-56-generic, x86_64: installed digimend, 10, 5.4.0-54-generic, x86_64: installed digimend, 10, 5.4.0-56-generic, x86_64: installed rtbth, 3.9.6, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6620G] [1002:9641] (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Sumo [Radeon HD 6620G] [1179:fc52] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Radeon HD 7470M [1179:fc52] InstallationDate: Installed on 2020-03-23 (259 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: TOSHIBA SATELLITE L750D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (6 days ago) dmi.bios.date: 11/23/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Torpedo dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.50:bd11/23/2011:svnTOSHIBA:pnSATELLITEL750D:pvrPSK36E-05P00LIT:rvnAMD:rnTorpedo:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.family: Type1Family dmi.product.name: SATELLITE L750D dmi.product.sku: PSK36E-05P00LIT dmi.product.version: PSK36E-05P00LIT dmi.sys.vendor: TOSHIBA 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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1907154 Title: application menu of pdf and text documents is not visible when the window is resized and made smaller Status in xorg package in Ubuntu: New Bug description: 1. When opening a text document (with standard text editor) or a pdf with "Pdf viewer" and clicking on the "menu" icon at the top right of the window, the menu shows up correctly. 2.If I resize the window making it shorter than the menu itself, I would expect the menu to remain fully visible or at least in some way graphically accessible (resized or scrollable). 3. Instead, I can no more see some options of the menu: a part of it is not visible (as it was graphically cut). So you can't see nor select with the mouse the non-visible part of the menu. 4. I noticed you can navigate and select the options (both visible or non-visible) of the menu using arrows and Enter from the keyboard. However this is not a solution because you still cannot see a part of the menu
[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)
Same problem here with Ubuntu 20.04. I have an Asus ZenBook Flip S (UX370UA). I tried two kernels: 5.6.11 and 5.4.2 -- 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/1576844 Title: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly) Status in xorg package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 Several times yesterday and today (April 28-29, 2016) the touchpad (trackpad) on the Dell XPS 13 9343 has frozen. Other functions (keyboard, screen, etc.) have been fine but the pointer has been frozen in place. Then after 1-3 minutes functionality returns. Thank you very much for your assistance and I'd be happy to provide more information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,composite,opengl,cube,rotate] CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Fri Apr 29 16:09:32 2016 DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665] InstallationDate: Installed on 2015-08-06 (267 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 27 15:54:22 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5152 vendor SHP xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+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 1775974] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem
Public bug reported: I have updated the software several times but the sound card is not seen on the settings. Seems a software bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vincenzo 1138 F...m pulseaudio /dev/snd/controlC0: vincenzo 1138 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 08:12:53 2018 InstallationDate: Installed on 2018-05-02 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1775974 Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have updated the software several times but the sound card is not seen on the settings. Seems a software bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vincenzo 1138 F...m pulseaudio /dev/snd/controlC0: vincenzo 1138 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 08:12:53 2018 InstallationDate: Installed on 2018-05-02 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1775974/+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 1774355] [NEW] package python3-apport 2.20.1-0ubuntu2.17 failed to install/upgrade: unable to securely remove '/usr/share/doc/python3-apport/copyright.dpkg-new': Read-only file s
Public bug reported: This came just after a reboot. I did nothing special before that, no installtions or updates. Id automatically lead me here. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apport 2.20.1-0ubuntu2.17 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Thu May 31 09:56:37 2018 DuplicateSignature: package:python3-apport:2.20.1-0ubuntu2.17 Unpacking python3-problem-report (2.20.1-0ubuntu2.18) over (2.20.1-0ubuntu2.17) ... dpkg: error processing archive /var/cache/apt/archives/python3-problem-report_2.20.1-0ubuntu2.18_all.deb (--unpack): unable to securely remove '/usr/share/doc/python3-problem-report/copyright.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/python3-apport/copyright.dpkg-new': Read-only file system InstallationDate: Installed on 2016-12-04 (542 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: apport Title: package python3-apport 2.20.1-0ubuntu2.17 failed to install/upgrade: unable to securely remove '/usr/share/doc/python3-apport/copyright.dpkg-new': Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1774355 Title: package python3-apport 2.20.1-0ubuntu2.17 failed to install/upgrade: unable to securely remove '/usr/share/doc/python3-apport/copyright .dpkg-new': Read-only file system Status in apport package in Ubuntu: New Bug description: This came just after a reboot. I did nothing special before that, no installtions or updates. Id automatically lead me here. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apport 2.20.1-0ubuntu2.17 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Thu May 31 09:56:37 2018 DuplicateSignature: package:python3-apport:2.20.1-0ubuntu2.17 Unpacking python3-problem-report (2.20.1-0ubuntu2.18) over (2.20.1-0ubuntu2.17) ... dpkg: error processing archive /var/cache/apt/archives/python3-problem-report_2.20.1-0ubuntu2.18_all.deb (--unpack): unable to securely remove '/usr/share/doc/python3-problem-report/copyright.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/python3-apport/copyright.dpkg-new': Read-only file system InstallationDate: Installed on 2016-12-04 (542 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: apport Title: package python3-apport 2.20.1-0ubuntu2.17 failed to install/upgrade: unable to securely remove '/usr/share/doc/python3-apport/copyright.dpkg-new': Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774355/+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 1773090] [NEW] package libprocps4 2:3.3.10-4ubuntu2.3 failed to install/upgrade: unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file sys
Public bug reported: I booted after I detected that '/' has been mounted read only. After the reboot the crash reporter appeared, and here I am... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libprocps4 2:3.3.10-4ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 AptOrdering: libprocps4: Install procps: Install libprocps4: Configure procps: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu May 24 08:20:15 2018 DpkgTerminalLog: Preparing to unpack .../libprocps4_2%3a3.3.10-4ubuntu2.4_amd64.deb ... Unpacking libprocps4:amd64 (2:3.3.10-4ubuntu2.4) over (2:3.3.10-4ubuntu2.3) ... dpkg: error processing archive /var/cache/apt/archives/libprocps4_2%3a3.3.10-4ubuntu2.4_amd64.deb (--unpack): unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system DuplicateSignature: package:libprocps4:2:3.3.10-4ubuntu2.3 Unpacking libprocps4:amd64 (2:3.3.10-4ubuntu2.4) over (2:3.3.10-4ubuntu2.3) ... dpkg: error processing archive /var/cache/apt/archives/libprocps4_2%3a3.3.10-4ubuntu2.4_amd64.deb (--unpack): unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system InstallationDate: Installed on 2016-12-04 (535 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: procps Title: package libprocps4 2:3.3.10-4ubuntu2.3 failed to install/upgrade: unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1773090 Title: package libprocps4 2:3.3.10-4ubuntu2.3 failed to install/upgrade: unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz .dpkg-new': Read-only file system Status in procps package in Ubuntu: New Bug description: I booted after I detected that '/' has been mounted read only. After the reboot the crash reporter appeared, and here I am... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libprocps4 2:3.3.10-4ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 AptOrdering: libprocps4: Install procps: Install libprocps4: Configure procps: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu May 24 08:20:15 2018 DpkgTerminalLog: Preparing to unpack .../libprocps4_2%3a3.3.10-4ubuntu2.4_amd64.deb ... Unpacking libprocps4:amd64 (2:3.3.10-4ubuntu2.4) over (2:3.3.10-4ubuntu2.3) ... dpkg: error processing archive /var/cache/apt/archives/libprocps4_2%3a3.3.10-4ubuntu2.4_amd64.deb (--unpack): unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system DuplicateSignature: package:libprocps4:2:3.3.10-4ubuntu2.3 Unpacking libprocps4:amd64 (2:3.3.10-4ubuntu2.4) over (2:3.3.10-4ubuntu2.3) ... dpkg: error processing archive /var/cache/apt/archives/libprocps4_2%3a3.3.10-4ubuntu2.4_amd64.deb (--unpack): unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system InstallationDate: Installed on 2016-12-04 (535 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: procps Title: package libprocps4 2:3.3.10-4ubuntu2.3 failed to install/upgrade: unable to securely remove '/usr/share/doc/libprocps4/NEWS.Debian.gz.dpkg-new': Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1773090/+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 1771081] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails to detect card
Public bug reported: I now have a different problem. I had sound working when i tricked the software by having my phone play music. now it has booted up and the sound is lost and there is a dummy card in the sound profile. if i add a bluetooth speaker it will play to it but with lots of cutting out. i know the quality is good as it has played on my machine and i have used the bluetooth speaker from another source. it seems to be this software? regards Vinnychoff ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 14 09:26:54 2018 InstallationDate: Installed on 2018-05-02 (11 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_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Black Line Out, Rear Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1771081 Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I now have a different problem. I had sound working when i tricked the software by having my phone play music. now it has booted up and the sound is lost and there is a dummy card in the sound profile. if i add a bluetooth speaker it will play to it but with lots of cutting out. i know the quality is good as it has played on my machine and i have used the bluetooth speaker from another source. it seems to be this software? regards Vinnychoff ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 14 09:26:54 2018 InstallationDate: Installed on 2018-05-02 (11 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_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Black Line Out, Rear Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1771081/+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 1770360] [NEW] [Inspiron 530, Realtek ALC888, Blue Line In, Rear] Recording problem
Public bug reported: I had working sound with 16.04 lts. upgraded to 18.04 lts no sound. I found a work around by having my phone play sound while booting it up. I now have sound but can not see a sound card in my settings. before it was dummy sound card. I assume the internal sound card is not configured or talking to the protocols as it is not configured. Could you fix this please. I see lots of sound issues on this release. Vincenzo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincenzo 1037 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:26:57 2018 InstallationDate: Installed on 2018-05-02 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Blue Line In, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Blue Line In, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1770360 Title: [Inspiron 530, Realtek ALC888, Blue Line In, Rear] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: I had working sound with 16.04 lts. upgraded to 18.04 lts no sound. I found a work around by having my phone play sound while booting it up. I now have sound but can not see a sound card in my settings. before it was dummy sound card. I assume the internal sound card is not configured or talking to the protocols as it is not configured. Could you fix this please. I see lots of sound issues on this release. Vincenzo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincenzo 1037 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:26:57 2018 InstallationDate: Installed on 2018-05-02 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Blue Line In, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel successful Symptom_Type: None of the above Title: [Inspiron 530, Realtek ALC888, Blue Line In, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770360/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9
Daniel, thanks I will open a new bug as it is still not right. Thanks On 10 May 2018 at 09:53, Daniel van Vugtwrote: > The fix for this bug was released 7 days ago. > > Please update your system and if you continue to have problems then open > a new bug. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768509). > https://bugs.launchpad.net/bugs/1767784 > > Title: > [regression] output device not recognized anymore since update > 1:8.0-0ubuntu3.9 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+ > bug/1767784/+subscriptions > -- 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/1767784 Title: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9 Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Bug description: SRU Document: [Impact] The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even there is no internal speaker and nothing plugged in the audio jack, the profile is still set available, then the active profile is analog- stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to unavailable, and the active profile is off, after users plug sth in the audio jack, the active profile will not switch automatically, need users to switch manually, this change is unfriendly to users. [Test Case] On the machines without internal speaker, open sound-setting and check if there is some output devices in the UI, and play sound from the UI. Under 1:8.0-0ubuntu3.9 there is no output device, and can't play sound; under 1:8.0-0ubuntu3.8 there is output device, and can play sound. [Regression Potential] This is a revert, after reverting, the content of pulseaudio is exactly same as 1:8.0-0ubuntu3.8 [Other Info] none Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not showing anymore my soundcard. https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9 The command "pacmd list-sinks" only shows a dummy output When running on a fresh install of ubuntu 16.04, the sound is ok. When updating the install with locking the following files to version 1:8.0-0ubuntu3 the sound keeps working: libpulse0:amd64 libpulse-mainloop-glib0:amd64 libpulse-dev:amd64 pulseaudio-module-x11:amd64 pulseaudio-module-bluetooth:amd64 pulseaudio-utils:amd64 When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output". I tried running the following versions of Ubuntu (live usb), and get the same issue (no need to update to get the problem) 17.04 17.10 18.04 I attached the result of command "pactl list" I have also generated logs during the boot but I don't know how to attach multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9
I managed to find a work around. I wonder when this is going to be fixed? I connected a phone to my pc and played music, this kick started the card on boot up and now i have a sound card, although there is no sound card shown in the sound settings. before it was dummy now there is no card shown. i have sound working though. i assume on the next reboot it will loose the sound. look forward to your help and support. I know this is affecting quite a few users on the new update. Vincenzo -- 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/1767784 Title: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9 Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Bug description: SRU Document: [Impact] The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even there is no internal speaker and nothing plugged in the audio jack, the profile is still set available, then the active profile is analog- stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to unavailable, and the active profile is off, after users plug sth in the audio jack, the active profile will not switch automatically, need users to switch manually, this change is unfriendly to users. [Test Case] On the machines without internal speaker, open sound-setting and check if there is some output devices in the UI, and play sound from the UI. Under 1:8.0-0ubuntu3.9 there is no output device, and can't play sound; under 1:8.0-0ubuntu3.8 there is output device, and can play sound. [Regression Potential] This is a revert, after reverting, the content of pulseaudio is exactly same as 1:8.0-0ubuntu3.8 [Other Info] none Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not showing anymore my soundcard. https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9 The command "pacmd list-sinks" only shows a dummy output When running on a fresh install of ubuntu 16.04, the sound is ok. When updating the install with locking the following files to version 1:8.0-0ubuntu3 the sound keeps working: libpulse0:amd64 libpulse-mainloop-glib0:amd64 libpulse-dev:amd64 pulseaudio-module-x11:amd64 pulseaudio-module-bluetooth:amd64 pulseaudio-utils:amd64 When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output". I tried running the following versions of Ubuntu (live usb), and get the same issue (no need to update to get the problem) 17.04 17.10 18.04 I attached the result of command "pactl list" I have also generated logs during the boot but I don't know how to attach multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1768509] [NEW] [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all
Public bug reported: I know it was working before with LTS 16.04. Also the sound card is shown as dummy when I have tried several times to upload the software i have seen two different sound cards. Could you help me fix this? 18/04 LTS upgraded fresh, no updates vincenzo@inspiron530:~$ apt-cache policy pkgname N: Unable to locate package pkgname vincenzo@inspiron530:~$ i thought it would find the card automatically. it seems not to have the right card or be misconfigured. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincenzo949 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 2 12:33:58 2018 InstallationDate: Installed on 2018-05-02 (0 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_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincenzo949 F pulseaudio Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768509 Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: I know it was working before with LTS 16.04. Also the sound card is shown as dummy when I have tried several times to upload the software i have seen two different sound cards. Could you help me fix this? 18/04 LTS upgraded fresh, no updates vincenzo@inspiron530:~$ apt-cache policy pkgname N: Unable to locate package pkgname vincenzo@inspiron530:~$ i thought it would find the card automatically. it seems not to have the right card or be misconfigured. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincenzo949 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 2 12:33:58 2018 InstallationDate: Installed on 2018-05-02 (0 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_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincenzo949 F pulseaudio Symptom_Jack: Black Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0K216C dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https:
[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted
Any updates on this bug? Is there a fix on the way? I'm experiencing this problem on 16.04 Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted Status in rsyslog package in Ubuntu: Confirmed Bug description: This could otherwise be titled, rsyslog reload does not create log files; only restart does. This is happening on a number of machines I work on. It's happening on 10.04 and 11.04. It might be similar to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 But in my case after the restart there is no /var/log/syslog being created, nor auth.log, kern.log, etc. The files are rotated, rsyslog is reloaded, and none of the log files are created and nothing is being logged. This has been plaguing my systems since moving from syslog-ng, which I may return to as it seems it was actually production ready. Without manually restarting those files don't exist so here's what I did on an 11.04 system: logrotate --force --verbose /etc/logrotate.conf gives: rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log /var/log/syslog does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log /var/log/kern.log does not exist -- skipping considering log /var/log/auth.log log /var/log/auth.log does not exist -- skipping considering log /var/log/user.log log /var/log/user.log does not exist -- skipping considering log /var/log/lpr.log log /var/log/lpr.log does not exist -- skipping considering log /var/log/cron.log log /var/log/cron.log does not exist -- skipping considering log /var/log/debug log /var/log/debug does not exist -- skipping considering log /var/log/messages log /var/log/messages does not exist -- skipping not running postrotate script, since no logs were rotated Then /sbin/reload rsyslog logger -i testing At this point there is no /var/log/syslog Then: /sbin/restart rsyslog And voila there is a /var/log/syslog beginning with: Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg started. Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114 Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108 Then to recreate: logrotate --force --verbose /etc/logrotate.conf rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log needs rotating rotating log /var/log/syslog, log->rotateCount is 7 dateext suffix '-20120223' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' compressing log with: /bin/gzip renaming /var/log/syslog to /var/log/syslog-20120223 running postrotate script removing old log /var/log/syslog-20111219.gz rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log needs rotating considering log /var/log/auth.log log needs rotating considering log /var/log/user.log log
[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04
I struggled with this long enough and took some notes about a workaround here: https://thealarmclocksixam.com/2017/08/08/dns-configuration-with- vpns-and-ubuntu-17-04-working-again/ I hope that this can help someone else as well. -- 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/1684854 Title: The default behaviour for search domains changed from 16.10 to 17.04 Status in network-manager package in Ubuntu: Confirmed Bug description: Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default behaviour for search domains changed. By default systemd-resolved does not use the domain supplied by DHCP as a search domain. So network-manager should at least have an option to tell systemd- networkd to change it's behaviour. In systemd-networkd the corresponding option is named "UseDomains". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1684854/+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 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
Thanks to everyone I solved the bug in fact it was the package that was not installed properly. I just had to reinstall the whole thing If anyone may be interested Sudo apt-get install --reinstall libc6-dbg: amd64 Thank you again to everyone!! vincenzo 2017-07-14 11:25 GMT+02:00 carduner <1692...@bugs.launchpad.net>: > It works, after reinstall the packets (libc6-dbg:amd64 and openssl) > Thanks Seth! > > Le 12/07/2017 à 20:52, Seth Arnold a écrit : > > I'm curious how we can work around this bug. If you're affected please > > report the results of: > > > > dpkg -l | awk '/^iH/ { print $2 }' > > > > This shows which specific packages are half-installed on your systems. > > > > With the list of packages this returns, please also report success or > > failure of: > > > > sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED > > LIST > > > > Thanks > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1701676). > https://bugs.launchpad.net/bugs/1692981 > > Title: > package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: > package is in a very bad inconsistent state; you should reinstall it > before attempting configuration > > Status in dpkg package in Ubuntu: > Confirmed > Status in openssl package in Ubuntu: > Confirmed > > Bug description: > package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: > package is in a very bad inconsistent state; you should reinstall it > before attempting configuration > > ProblemType: Package > DistroRelease: Ubuntu 17.04 > Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 > ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 > Uname: Linux 4.10.0-21-generic x86_64 > ApportVersion: 2.20.4-0ubuntu4.1 > AptOrdering: >libssl1.0.0:amd64: Install >NULL: ConfigurePending > Architecture: amd64 > Date: Tue May 23 21:47:55 2017 > DuplicateSignature: >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... >dpkg: error processing package libssl-dev:amd64 (--configure): > package is in a very bad inconsistent state; you should > ErrorMessage: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > InstallationDate: Installed on 2017-05-15 (7 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > RelatedPackageVersions: >dpkg 1.18.10ubuntu2 >apt 1.4 > SourcePackage: openssl > Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to > install/upgrade: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1692981 Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libssl1.0.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:47:55 2017 DuplicateSignature: package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... dpkg: error processing package libssl-dev:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-15 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: openssl Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a
[Touch-packages] [Bug 1701676] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo
Public bug reported: I get a window with this error as ubuntu boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 29 19:03:11 2017 ErrorMessage: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2016-07-14 (351 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1701676 Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") Status in openssl package in Ubuntu: New Bug description: I get a window with this error as ubuntu boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 29 19:03:11 2017 ErrorMessage: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2016-07-14 (351 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1701676/+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 1676762] [NEW] package libgstreamer-plugins-base1.0-0 1.8.3-1ubuntu0.1 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libgsttag-1.0.so.0.803.0.dp
Public bug reported: Got this after system start. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer-plugins-base1.0-0 1.8.3-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 28 08:50:23 2017 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:1.8.3-1ubuntu0.1 Unpacking eject (2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1) over (2.1.5+deb1+cvs20081104-13.1) ... dpkg: error processing archive /var/cache/apt/archives/eject_2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1_amd64.deb (--unpack): unable to securely remove '/usr/bin/volname.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/lib/x86_64-linux-gnu/libgsttag-1.0.so.0.803.0.dpkg-new': Read-only file system InstallationDate: Installed on 2016-12-04 (113 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0 1.8.3-1ubuntu0.1 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libgsttag-1.0.so.0.803.0.dpkg-new': Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1676762 Title: package libgstreamer-plugins-base1.0-0 1.8.3-1ubuntu0.1 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux- gnu/libgsttag-1.0.so.0.803.0.dpkg-new': Read-only file system Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: Got this after system start. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer-plugins-base1.0-0 1.8.3-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 28 08:50:23 2017 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:1.8.3-1ubuntu0.1 Unpacking eject (2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1) over (2.1.5+deb1+cvs20081104-13.1) ... dpkg: error processing archive /var/cache/apt/archives/eject_2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1_amd64.deb (--unpack): unable to securely remove '/usr/bin/volname.dpkg-new': Read-only file system ErrorMessage: unable to securely remove '/usr/lib/x86_64-linux-gnu/libgsttag-1.0.so.0.803.0.dpkg-new': Read-only file system InstallationDate: Installed on 2016-12-04 (113 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0 1.8.3-1ubuntu0.1 failed to install/upgrade: unable to securely remove '/usr/lib/x86_64-linux-gnu/libgsttag-1.0.so.0.803.0.dpkg-new': Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1676762/+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 1652449] Re: dnsmasq requires restart randomly now and then in order to access random URLs
I am affected by the same issue when I am connected to the office VPN. NetworkManager is using dnsmasq (as in /etc/NetworkManager/NetworkManager.conf). If I comment out the line dns=dnsmasq in that file, things work fine, but I prefer to use dnsmasq. I have to restart the service every now and then when DNS resolution stops working :(. sudo service dnsmasq restart -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1652449 Title: dnsmasq requires restart randomly now and then in order to access random URLs Status in dnsmasq package in Ubuntu: Confirmed Bug description: I use dnsmasq along with a long list of domains blocked in order to prevent spyware, malware, etc. on my personal computer. I've begun having frequent DNS problems after upgrading my Ubuntu (64 bit) system from 16.04 to 16.10. From time to time a random URL address suddenly becomes unreachable with varying error messages, most common one that I remember is some sort of a DNS ERROR. I've found that the only remedy is this "sudo /etc/init.d/dnsmasq restart". After that, the problem disappears - for some time. Such URL addresses cannot be accessed system-wide until dnsmasq service is restarted, but they can be accessed via Tor Browser only, which bypasses dnsmasq I guess. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1652449/+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 1624916] [NEW] package libqt5test5:i386 5.5.1+dfsg-16ubuntu7.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo
Public bug reported: I was adding telegram ppa when this error occurred ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5test5:i386 5.5.1+dfsg-16ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: telegram: Install libqt5test5: Configure telegram: Configure NULL: ConfigurePending Architecture: i386 Date: Sun Sep 18 20:40:31 2016 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2016-09-02 (15 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: qtbase-opensource-src Title: package libqt5test5:i386 5.5.1+dfsg-16ubuntu7.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1624916 Title: package libqt5test5:i386 5.5.1+dfsg-16ubuntu7.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in qtbase-opensource-src package in Ubuntu: New Bug description: I was adding telegram ppa when this error occurred ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5test5:i386 5.5.1+dfsg-16ubuntu7.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: telegram: Install libqt5test5: Configure telegram: Configure NULL: ConfigurePending Architecture: i386 Date: Sun Sep 18 20:40:31 2016 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2016-09-02 (15 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: qtbase-opensource-src Title: package libqt5test5:i386 5.5.1+dfsg-16ubuntu7.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1624916/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
I'm seeing exactly the same problem $ sudo dmidecode | grep Product | head -1 Product Name: Inspiron 7548 $ uname -a Linux hawk 4.3.0-040300-generic #201511020949 SMP Mon Nov 2 14:50:44 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a 2>/dev/null Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
** Attachment added: qemu_elementary_dekstop.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/4291236/+files/qemu_elementary_dekstop.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. Status in Cairo Graphics Library: Confirmed Status in cairo package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in xserver-xorg-video-cirrus package in Ubuntu: Won't Fix Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
** Attachment added: qemu_mint_dekstop.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/4291235/+files/qemu_mint_dekstop.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. Status in Cairo Graphics Library: Confirmed Status in cairo package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in xserver-xorg-video-cirrus package in Ubuntu: Won't Fix Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
I have a similar problem using qemu-kvm in kubuntu 14.04.1, while running linux-mint 17.1 or elementary os 0.3 beta 1 in the virtual machine. In the case of linux mint, the desktop is more or less ok, but some objects are corrupted. If you look at the first attached screenshot you will see three windows, two are ok (calculator and software manager) and one is corrupted (system monitor). In the second screenshot you will see the elementary os desktop which is almost unreadable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. Status in Cairo Graphics Library: Confirmed Status in cairo package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in xserver-xorg-video-cirrus package in Ubuntu: Won't Fix Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+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