[Touch-packages] [Bug 2046367] Re: AlphaSSL SHA256 G4 Intermediate Certificate missing
Thank you! I reported it to technical support, I hope they will fix it in the right way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2046367 Title: AlphaSSL SHA256 G4 Intermediate Certificate missing Status in ca-certificates package in Ubuntu: Won't Fix Bug description: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2046367/+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 2046367] Re: AlphaSSL SHA256 G4 Intermediate Certificate missing
There were problems with the site https://smsc.kz, we wrote to technical support, they uploaded a full bundle of certificates to solve the problem with the lack of an intermediate CA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2046367 Title: AlphaSSL SHA256 G4 Intermediate Certificate missing Status in ca-certificates package in Ubuntu: Incomplete Bug description: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2046367/+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 2046367] [NEW] AlphaSSL SHA256 G4 Intermediate Certificate missing
Public bug reported: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2046367 Title: AlphaSSL SHA256 G4 Intermediate Certificate missing Status in ca-certificates package in Ubuntu: New Bug description: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2046367/+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 2041715] Re: Sudden freeze/crash (with audio flickering)
** Attachment added: "prev_journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2041715/+attachment/5713947/+files/prev_journal.txt -- 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/2041715 Title: Sudden freeze/crash (with audio flickering) Status in xorg package in Ubuntu: New Bug description: All of the sudden screen just got frozen (in that moment I was listening to the song and audio did not continue playing as usual, but started "flickering"). I put the note about audio here, because usually freeze affected only the screen itself and audio was playing as usual. I've been reporting the xorg freeze/hang a number of times, I thought it was about new kernel version. But recently I updated xorg package and today this happened. Will try to roll back and see what happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Sat Oct 28 15:18:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (190 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2041715/+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 2041715] [NEW] Sudden freeze/crash (with audio flickering)
Public bug reported: All of the sudden screen just got frozen (in that moment I was listening to the song and audio did not continue playing as usual, but started "flickering"). I put the note about audio here, because usually freeze affected only the screen itself and audio was playing as usual. I've been reporting the xorg freeze/hang a number of times, I thought it was about new kernel version. But recently I updated xorg package and today this happened. Will try to roll back and see what happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Sat Oct 28 15:18:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (190 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 -- 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/2041715 Title: Sudden freeze/crash (with audio flickering) Status in xorg package in Ubuntu: New Bug description: All of the sudden screen just got frozen (in that moment I was listening to the song and audio did not continue playing as usual, but started "flickering"). I put the note about audio here, because usually freeze affected only the screen itself and audio was playing as usual. I've been reporting the xorg freeze/hang a number of times, I thought it was about new kernel version. But recently I updated xorg package and today this happened. Will try to roll back and see what happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Sat Oct 28 15:18:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (190 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID
[Touch-packages] [Bug 2041715] Re: Sudden freeze/crash (with audio flickering)
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2041715/+attachment/5713946/+files/journal.txt -- 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/2041715 Title: Sudden freeze/crash (with audio flickering) Status in xorg package in Ubuntu: New Bug description: All of the sudden screen just got frozen (in that moment I was listening to the song and audio did not continue playing as usual, but started "flickering"). I put the note about audio here, because usually freeze affected only the screen itself and audio was playing as usual. I've been reporting the xorg freeze/hang a number of times, I thought it was about new kernel version. But recently I updated xorg package and today this happened. Will try to roll back and see what happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Sat Oct 28 15:18:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (190 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2041715/+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 2038922] [NEW] Sudden screen crash
Public bug reported: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 -- 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/2038922 Title: Sudden screen crash Status in xorg package in Ubuntu: New Bug description: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18
[Touch-packages] [Bug 2037325] [NEW] Sudden screen freeze
Public bug reported: Out of nowhere screen got frozen and didn't respond to any input, although I could get my pointer moving with touchpad. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Mon Sep 25 23:03:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (158 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 -- 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/2037325 Title: Sudden screen freeze Status in xorg package in Ubuntu: New Bug description: Out of nowhere screen got frozen and didn't respond to any input, although I could get my pointer moving with touchpad. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Mon Sep 25 23:03:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (158 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 2019010] Re: environment variable SSH_ORIGINAL_COMMAND on server side set with wrong value
Hello I so that when it using scp with -O option " Use the legacy SCP protocol ..." it is working. The problem is that it is not always possible to force client to use additional switch. it is many cases when SSH_ORIGINAL_COMMAND is checked on server and additional decision is made on it . Is it possible to set this variable on server side to "original" meaning even when SFTP protocol is used for file transfer ? Thnaks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2019010 Title: environment variable SSH_ORIGINAL_COMMAND on server side set with wrong value Status in openssh package in Ubuntu: Incomplete Bug description: After updating to Ubuntu 23.04 when running scp command environment variable SSH_ORIGINAL_COMMAND on server side is set with SSH_ORIGINAL_COMMAND=/usr/libexec/openssh/sftp-server. With previous version this environment variable was set to "scp -t " or "scp -f " depends on if it was push or get command to copy file from or to remote system SSH_ORIGINAL_COMMAND environment variable is used to validate scp command on server side. System information: lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 apt-cache policy openssh-client openssh-client: Installed: 1:9.0p1-1ubuntu8 Candidate: 1:9.0p1-1ubuntu8 Version table: *** 1:9.0p1-1ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2019010/+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 2000649] Re: Xorg crashes or freezes
** Attachment added: "I was able to get a crash (when xorg goes black and throws me to login screen)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2000649/+attachment/5638687/+files/_usr_lib_xorg_Xorg.0.crash -- 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/2000649 Title: Xorg crashes or freezes Status in xorg package in Ubuntu: New Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 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.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2000649/+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 2000649] [NEW] Xorg crashes or freezes
Public bug reported: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 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.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 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/2000649 Title: Xorg crashes or freezes Status in xorg package in Ubuntu: New Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a
[Touch-packages] [Bug 1926095] Re: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently.
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1926095 Title: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently. Status in bluez package in Ubuntu: Confirmed Bug description: I have described the issue here with screenshots https://askubuntu.com/q/1333848/1022606. Please have a look at the screenshots. Turning on the Bluetooth toggle has no effect. The system doesn't turn on the Bluetooth and does no scan for devices. Turning it on just moves the toggle, even the system doesn't acknowledge by showing that Bluetooth is on. The status remains off. It happened only after the upgrade I did yesterday. It was working fine before that. Please look into it. I cannot connect my Bluetooth earphones to my PC. This poses a lot of problems since my classes and courses are all online. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 00:09:35 2021 InstallationDate: Installed on 2019-12-05 (507 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-24 (1 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926095/+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 1905472] Re: Something starts dhcclient for every intrface on boot
Oh, and just noticed that it was marked as "incomplete". Truly, I CAN see the future... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot Status in ifupdown package in Ubuntu: Incomplete Status in initramfs-tools package in Ubuntu: Incomplete Status in netplan.io package in Ubuntu: Incomplete Bug description: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1905472/+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 1905472] Re: Something starts dhcclient for every intrface on boot
This has nothing to do with network, as mentioned earlier netplan is masked and ifupdown works as expected. Moreover it is known EXACTLY what happens (in initramfs): local_top/aoe calls configure_networking In absence of any kernel args, configure_networking tries to bring up every interface, by launching dhcpc for 3(?) seconds. This succeeds for interface that will be configured as part of bridge by ifupdown later, so bridge is left unconfigured and network is lost. The current workaround is to add ip=none to kernel line The proper fix is to change configure_networking to have a mode/arg where it brings up network interfaces bot does not try to assign ip addresses, and call it this way from local_top/aoe . Probably even split configure_networking into two functions... p.s. I can predict the future though (I have such a gift) - the resolution would be "AOE is used by 0.01% of ubuntu users, we power the word and store petabytes of data, mark this as enhancement for a future version N+5". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot Status in ifupdown package in Ubuntu: Incomplete Status in initramfs-tools package in Ubuntu: Incomplete Status in netplan.io package in Ubuntu: Incomplete Bug description: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1905472/+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 1905472] Re: Something starts dhcclient for every intrface on boot
The culprit is intramfs. Starting with 20 LTS, having an AOE device brings in local_top/aoe, which calls configure_networking . This causes dhcp configuration of the primary net interface, which screws up all network later (as this physical interface is part of the bridge, and bridge can't get a dhcp lease later). AOE stands for "ATA over ETHERNET", not ATA over IP. There is zero need to bring up ip stack for aoe to function. ** Also affects: ubuntu-core-initramfs Importance: Undecided Status: New ** No longer affects: isc-dhcp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot Status in ubuntu-core-initramfs: New Bug description: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1905472/+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 1905472] [NEW] Something starts dhcclient for every intrface on boot
Public bug reported: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot Status in isc-dhcp package in Ubuntu: New Bug description: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1905472/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
Focal release is affected as well. -- 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/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Each time I am upgrading Xenial to Bionic I'm getting exactly the same message after few minutes: "*** ntp.conf (Y/I/N/O/D/Z) [default=N] ? " Can this fix get delivered to Ubuntu Xenial? ubuntu-release-upgrader-core 1:16.04.26 -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Released Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Released Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Released Status in apt source package in Eoan: Invalid Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 521677] Re: /usr/bin/rename.ul not in rename alternatives list
rename.ul from util-linux package was removed from alternatives intentionnaly. It was a fix for Debian bug #439935, because other rename alternatives (e.g. prename) have incompatible usage syntax. See also https://unix.stackexchange.com/a/444524/290955 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/521677 Title: /usr/bin/rename.ul not in rename alternatives list Status in util-linux package in Ubuntu: Triaged Bug description: Binary package hint: util-linux Hello, I recently migrated my system from another Linux distribution (Gentoo) and noticed, that the rename-tool behaves differently. I tried to change the rename tool using "sudo update-alternatives --config rename" but was unsuccessful with the message that there were no alternatives to select. After a quick research on the net I found the following article: https://lists.ubuntu.com/archives/ubuntu-users/2009-May/184585.html. It states that not the rename tool of util-linux is used but the perl- script prename and the rename tool of util-linux can be found at "/usr/bin/rename.ul". According to the article the following command can be used to add "rename.ul" to the list of alternatives: update-alternatives --install /usr/bin/rename rename /usr/bin/rename.ul 50 --slave /usr/share/man/man1/rename.1.gz rename.1.gz /usr/share/man/man1/rename.ul.1.gz After this I was able to use the util-linux based rename. Is it possible to enable this selection by default, e.g. using a post- install trigger for util-linux or prename? Or are there other considerations for not including the standard rename? Yours sincerely, Ingo -- Ubuntu release: Description: Ubuntu 9.10 Release: 9.10 Packages: util-linux: Installed: 2.16-1ubuntu5 Candidate: 2.16-1ubuntu5 Version table: *** 2.16-1ubuntu5 0 500 http://at.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status Expected to happen: Find /usr/bin/rename.ul in the rename alternatives list using sudo update-alternatives --config rename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/521677/+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 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Yes, it is latest - the cluster is being re-deployed as part of Bootstack handover. Corey, The bug you point to is fixing the sequence of ceph/udev. Here however udev can't create any devices as they don't exist at the moment of udev run seems so - when the host boots and settles down - there is no PVs exist at all. -- 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/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration Status in systemd package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+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 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Steve, This is MAAS who creates these udev rules. We requested this feature to be implemented in order to be able to use persistent names in further services configuration (using templating). We couldn't go with /dev/sdX names as they may change after the reboot, and can't use wwn names as they are unique per node and don't allow us to use templates with FCB. -- 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/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration Status in systemd package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+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 1828617] [NEW] Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Public bug reported: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. ** 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/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+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 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Description changed: Ubuntu will not unlock non-root LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) - https://my.nixaid.com/s/epxpwHckGipcB6D + https://my.nixaid.com/s/odG8zEJ2Z75TdHG It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit. /etc/crypttab: sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks -- 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/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument Status in systemd package in Ubuntu: New Bug description: Ubuntu will not unlock non-root LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) https://my.nixaid.com/s/odG8zEJ2Z75TdHG It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit. /etc/crypttab: sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809819/+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 1820944] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2
Public bug reported: I tried to command "sudo apt-get install ssh" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 19 10:15:17 2019 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 InstallationDate: Installed on 2018-08-11 (220 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1820944 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 Status in openssh package in Ubuntu: New Bug description: I tried to command "sudo apt-get install ssh" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 19 10:15:17 2019 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 InstallationDate: Installed on 2018-08-11 (220 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1820944/+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 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls
Thank you, Johnny Westerlund! At least adding "sasl_secprops minssf=0,maxssf=0" to /etc/openldap/ldap.conf works around the error, so things seem to work for me. Not sure whether it is different now for Michael Osipov. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: [Status] Awaiting upstream fix. [Workaround] Unknown. [Description] Not sure if this is a problem with openldap or cyrus-sasl2 at this point. Using sasl binding only works with ldapsearch when not using ssl or tls. If either ssl or tls is used I see this ouput from -d 1 from ldapsearch: sb_sasl_generic_pkt_length: received illegal packet length of 813957120 bytes sasl_generic_read: want=16, got=16 : 00 7e 02 01 00 78 84 00 00 00 5d 0a 01 02 04 00 .~...x]. sb_sasl_cyrus_decode: failed to decode packet: generic failure sb_sasl_generic_read: failed to decode packet ldap_read: want=8 error=Input/output error # numResponses: 0 ldap_result: Can't contact LDAP server (-1) tls_write: want=165 error=Connection reset by peer tls_write: want=165 error=Bad file descriptor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+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 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls
Exact same error here in 2019. I set Windows Server 2019 up, default AD DS & AD CS (for TLS). Clients tried: Ubuntu 18.04: libsasl2-modules-gssapi-mit:amd64 2.1.27~101-g0780600+dfsg-3ubuntu2 Alpine Edge: cyrus-sasl-gssapiv2-2.1.27-r1 Have anyone tried asking in Cyrus SASL mailing list? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: [Status] Awaiting upstream fix. [Workaround] Unknown. [Description] Not sure if this is a problem with openldap or cyrus-sasl2 at this point. Using sasl binding only works with ldapsearch when not using ssl or tls. If either ssl or tls is used I see this ouput from -d 1 from ldapsearch: sb_sasl_generic_pkt_length: received illegal packet length of 813957120 bytes sasl_generic_read: want=16, got=16 : 00 7e 02 01 00 78 84 00 00 00 5d 0a 01 02 04 00 .~...x]. sb_sasl_cyrus_decode: failed to decode packet: generic failure sb_sasl_generic_read: failed to decode packet ldap_read: want=8 error=Input/output error # numResponses: 0 ldap_result: Can't contact LDAP server (-1) tls_write: want=165 error=Connection reset by peer tls_write: want=165 error=Bad file descriptor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+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 1483989] Re: apt prints wrong duration after update
Ubuntu 18.04.2 LTS here.. got same # apt update && apt -y upgrade && apt -y dist-upgrade && apt -y autoremove Hit:1 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu bionic InRelease Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.ubuntu.com/ubuntu disco InRelease [243 kB] Hit:8 http://archive.ubuntu.com/ubuntu disco-updates InRelease Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB] Hit:10 http://security.ubuntu.com/ubuntu disco-security InRelease Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66.6 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [202 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [176 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [348 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,468 B] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7,352 B] Get:18 http://archive.ubuntu.com/ubuntu disco/universe i386 Packages [9,115 kB] Get:19 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B] Get:20 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages [9,171 kB] Get:21 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20.8 kB] Get:22 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12.2 kB] Get:23 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [45.2 kB] Get:24 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2,464 B] Get:25 http://archive.ubuntu.com/ubuntu disco/universe amd64 DEP-11 Metadata [3,492 kB] Get:26 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 48x48 Icons [2,757 kB] Get:27 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 64x64 Icons [8,459 kB] Fetched 34.8 MB in 213503982334601d 6h 0min 21s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. ... apt 1.6.8 -- 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/1483989 Title: apt prints wrong duration after update Status in apt package in Ubuntu: Confirmed Bug description: Today I have got this from "sudo apt-get update" ... Fetched 128 kB in 213503982334601d 7h 0min 15s (0 B/s) ... It lasted, very likely, 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apt 1.0.9.2ubuntu2 Uname: Linux 4.1.0-pf1+ x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: amd64 CurrentDesktop: KDE Date: Wed Aug 12 08:24:29 2015 InstallationDate: Installed on 2014-12-01 (253 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1483989/+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.
This should fix the issue: # EDITOR=vim systemctl edit apport-autoreport.service [Unit] After=whoopsie.service Wants=whoopsie.service Save. Or instead of doing "systemctl edit", you can just drop these 3 lines to the "/etc/systemd/system/apport-autoreport.service.d/override.conf" file and issue "systemctl daemon-reload" command. Tested: systemctl stop whoopsie.service systemctl stop apport-autoreport.service systemctl start apport-autoreport.service This worked for me. -- 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: Confirmed 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 1807189] Re: occasional graphical artefacts after loggin out or rebooting in ubuntu 18.04 and 18.10
** Package changed: ubuntu => mesa (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/1807189 Title: occasional graphical artefacts after loggin out or rebooting in ubuntu 18.04 and 18.10 Status in mesa package in Ubuntu: New Bug description: I have amd rx 560 graphics card. And sometimes graphical artefacts appear after loggin out and rebooting in ubuntu 18.10 and ubuntu 18.04. It doesn't happen with another linux distros and it didn't happen with older ubuntu versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1807189/+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 1288182]
(In reply to fidanjan-karen from comment #35) > https://freedomsponsors.org/issue/807/problem-with-cyrillic-and-japanese-at- > pdf-forms-evince-okular I've added myself as a sponsor to the bounty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1288182]
You can create bounty for this for example here: https://freedomsponsors.org/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1288182]
Confirm the issue in Gnome 3.20.1 in Debian/Testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
The patch
https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056
did work for me on my mid-2017 MacBookPro (HW, not VM).
Thank you, Andrea!
--
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/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
In Progress
Bug description:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 459730] Re: rsyslog doesn't create /dev/xconsole
k--andrey@kandrey:/tmp$ cat /etc/issue
Ubuntu 16.04.4 LTS \n \l
k--andrey@kandrey:/tmp$ uname -a
Linux kandrey.kitsoft.kiev.ua 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar
14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Apr 27 12:12:41 kandrey rsyslogd-2039: Could not open output pipe
'/dev/xconsole':: No such file or directory [v8.16.0 try
http://www.rsyslog.com/e/2039 ]
--
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/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Fix Released
Status in rsyslog package in Ubuntu:
Fix Released
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+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 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
I also have this issue. My PPTP connection was working fine and then I probably added some routes. And now I can't connect. Attach output from 'journalctl -u NetworkManager.service' command. ** Attachment added: "journalctl -u NetworkManager.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+attachment/5021227/+files/pptp_logs.txt -- 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/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 1699340] [NEW] 1
Public bug reported: 1 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CompositorRunning: None Date: Wed Jun 21 00:10:12 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:0005] InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA PORTEGE Z30-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.20 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnPORTEGEZ30-B:pvrPT253U-0C501R:rvnTOSHIBA:rnPORTEGEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z30-B dmi.product.version: PT253U-0C501R dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Wed Jun 21 00:04:11 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu zesty -- 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/1699340 Title: 1 Status in xorg package in Ubuntu: New Bug description: 1 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CompositorRunning: None Date: Wed Jun 21 00:10:12 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:0005] InstallationDate: Installed on 2017-06-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA PORTEGE Z30-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.20 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnPORTEGEZ30-B:pvrPT253U-0C501R:rvnTOSHIBA:rnPORTEGEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z30-B dmi.product.version: PT253U-0C501R dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
[Touch-packages] [Bug 492290] Re: Apport console frontend (ubuntu-bug, apport-cli) doesn't work with non-English locales
I confirm this bug on 14.04.1 for russian. -- 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/492290 Title: Apport console frontend (ubuntu-bug, apport-cli) doesn't work with non-English locales Status in apport package in Ubuntu: Triaged Bug description: Binary package hint: apport I try to report bug using ubuntu-bug: divius@divius-laptop:~/Work/pkibd/cbuild$ ubuntu-bug gnome-system- monitor *** Сбор информации о проблеме Собранная информация может быть направлена разработчикам для улучшения приложения. Это может занять несколько минут. .. *** Отправить отчёт об ошибке разработчикам? После того, как отчёт будет отправлен, заполните форму в автоматически открывшемся окне обозревателя. Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (5.0 KiB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо Т: Отменить Пожалуйста, выберите (О/П/С/Т):ы /usr/bin/apport-cli:84: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal return self.keys.index(response[0].upper()) + 1 Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (5.0 KiB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо Т: Отменить Пожалуйста, выберите (О/П/С/Т): Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (5.0 KiB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо Т: Отменить Пожалуйста, выберите (О/П/С/Т):s Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (5.0 KiB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо Т: Отменить Пожалуйста, выберите (О/П/С/Т):d Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (5.0 KiB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо Т: Отменить Пожалуйста, выберите (О/П/С/Т):О Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (5.0 KiB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо Т: Отменить Пожалуйста, выберите (О/П/С/Т): And so on. No matter what letter (Russian or English) I input it simply reask. Only Ctrl+C helps. apport 1.9.3-0ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/492290/+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 1684463] [NEW] [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all
Public bug reported: There is no sound on my pc. I had sound yesterday! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: work 2046 F...m pulseaudio /dev/snd/pcmC0D0c: work 2046 F...m pulseaudio /dev/snd/controlC0: work 2046 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Apr 20 10:12:51 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-07 (164 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: work 2046 F...m pulseaudio /dev/snd/pcmC0D0c: work 2046 F...m pulseaudio /dev/snd/controlC0: work 2046 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1684463 Title: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: There is no sound on my pc. I had sound yesterday! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: work 2046 F...m pulseaudio /dev/snd/pcmC0D0c: work 2046 F...m pulseaudio /dev/snd/controlC0: work 2046 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Apr 20 10:12:51 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-07 (164 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: work 2046 F...m pulseaudio /dev/snd/pcmC0D0c: work 2046 F...m pulseaudio /dev/snd/controlC0: work 2046 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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:
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
The patch fixes the issue for me as well. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+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 1673850] [NEW] Problem with video after suspend
Public bug reported: After my laptop goes from suspended state (sleep) I'm not able to adjust screen brightness. It goes to maximum brightness and no longer adjusted until laptop reboot. It's hard for my eyes to continue work. I don't know is it xorg problem, or amdgpu but I will do my best to help you to solve this issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 17 20:09:53 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: amdgpu-pro, 16.60-379184, 4.4.0-66-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-64-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b5] Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] [103c:80b5] InstallationDate: Installed on 2017-03-07 (10 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=433c8aa2-a343-4d03-8144-288b5cbc37f9 ro nopat vesafb.invalid=1 splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B5 dmi.board.vendor: HP dmi.board.version: 81.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd08/06/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.28:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 17 20:03:39 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1673850 Title: Problem with video after suspend Status in xorg package in Ubuntu: New Bug description: After my laptop goes from suspended state (sleep) I'm not able to adjust screen brightness. It goes to maximum brightness and no longer adjusted until laptop reboot. It's hard for my eyes to continue work. I don't know is it xorg problem, or amdgpu but I will do my best to help you to solve this issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 17 20:09:53 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: amdgpu-pro, 16.60-379184, 4.4.0-66-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-64-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b5] Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] [103c:80b5] InstallationDate:
[Touch-packages] [Bug 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem
ASUS UX501VW. Same issue with the background noise after suspend resume. Ubuntu 16.04. I've tried to use Kernel version 4.3.5, 4.4.0 and 4.8.17. Still buggy. -- 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/1547024 Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm not sure what's happening, my sound works great, there's just a static noise in the background that can get very annoying. Let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.5.0-040500rc4-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zkanda 1519 F pulseaudio CurrentDesktop: MATE Date: Thu Feb 18 21:34:15 2016 InstallationDate: Installed on 2016-02-16 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160216) 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: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.204:bd11/12/2015:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547024/+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 1665785] [NEW] [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise or low volume
Public bug reported: There is a background hissing/squeaking noise in my headphones every time I resume suspend. Speakers and HDMI audio are not affected. I've tried many solutions to fix it (alsa force-reload etc.), but none of them worked well. More detailes you can find here: http://askubuntu.com/questions/884051/constant-hissing-sound-after-suspend-asus-zenbook-ux501-vw Standard four questions: 1) Ubuntu 16.04.1 LTS 2) Kernel 4.8.17-040817-generic (also tried 4.4.0 and 4.3.5) 3) When I resume suspend I hear no noise unless I play something 4) Right after suspend resume there is a background noise Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.8.17-040817-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: firesword 3563 F...m pulseaudio /dev/snd/pcmC0D0p: firesword 3563 F...m pulseaudio /dev/snd/controlC0: firesword 3563 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 17 23:54:52 2017 InstallationDate: Installed on 2017-02-17 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-17T21:26:16.180413 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1665785 Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: There is a background hissing/squeaking noise in my headphones every time I resume suspend. Speakers and HDMI audio are not affected. I've tried many solutions to fix it (alsa force-reload etc.), but none of them worked well. More detailes you can find here: http://askubuntu.com/questions/884051/constant-hissing-sound-after-suspend-asus-zenbook-ux501-vw Standard four questions: 1) Ubuntu 16.04.1 LTS 2) Kernel 4.8.17-040817-generic (also tried 4.4.0 and 4.3.5) 3) When I resume suspend I hear no noise unless I play something 4) Right after suspend resume there is a background noise Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.8.17-040817-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: firesword 3563 F...m pulseaudio /dev/snd/pcmC0D0p: firesword 3563 F...m pulseaudio /dev/snd/controlC0: firesword 3563 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 17 23:54:52 2017 InstallationDate: Installed on 2017-02-17 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW
[Touch-packages] [Bug 1639675] [NEW] [X555UB, Realtek ALC256, Speaker, Internal] No sound at all
Public bug reported: On ubuntu 16.04 only mic does not work but now 16.10 sounds don`t play too ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 2177 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 7 05:17:43 2016 InstallationDate: Installed on 2016-11-07 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 2177 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1639675 Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: On ubuntu 16.04 only mic does not work but now 16.10 sounds don`t play too ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 2177 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 7 05:17:43 2016 InstallationDate: Installed on 2016-11-07 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 2177 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1639675/+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 1639674] [NEW] tearing
Public bug reported: Video tearing is all time. Nvidia and novus drivers ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: wl 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 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 7 05:13:25 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.8.0-22-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 520 [1043:1ccd] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2016-11-07 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUSTeK COMPUTER INC. X555UB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=16c193c2-1248-47f0-91ce-31ece06b8894 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Nov 7 05:08:52 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety -- 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/1639674 Title: tearing Status in xorg package in Ubuntu: New Bug description: Video tearing is all time. Nvidia and novus drivers ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: wl 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 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 7 05:13:25 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8,
[Touch-packages] [Bug 1639085] [NEW] package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2
Public bug reported: 14.04 -> 16.04 upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 3 18:09:59 2016 ErrorMessage: subprocess new pre-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: lvm2 Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-11-03 (0 days ago) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- 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/1639085 Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 Status in lvm2 package in Ubuntu: New Bug description: 14.04 -> 16.04 upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 3 18:09:59 2016 ErrorMessage: subprocess new pre-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: lvm2 Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1639085/+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 1605260] [NEW] Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04
Public bug reported: There is a memory leak in libnl 3.2.21 fixed by upstream here: http://lists.infradead.org/pipermail/libnl/2013-April/000985.html and released as part of libnl-3.2.22 (git commit rev df66b0f267af636848d7f0301d3f5863c58fb313). However, this fix doesn't make it into Ubuntu 14.04LTS. Please, apply. $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy libnl-3-200 libnl-3-200: Installed: 3.2.21-1ubuntu3 Candidate: 3.2.21-1ubuntu3 Version table: *** 3.2.21-1ubuntu3 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.2.21-1 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages $ ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1605260 Title: Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04 Status in libnl3 package in Ubuntu: New Bug description: There is a memory leak in libnl 3.2.21 fixed by upstream here: http://lists.infradead.org/pipermail/libnl/2013-April/000985.html and released as part of libnl-3.2.22 (git commit rev df66b0f267af636848d7f0301d3f5863c58fb313). However, this fix doesn't make it into Ubuntu 14.04LTS. Please, apply. $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy libnl-3-200 libnl-3-200: Installed: 3.2.21-1ubuntu3 Candidate: 3.2.21-1ubuntu3 Version table: *** 3.2.21-1ubuntu3 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.2.21-1 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1605260/+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 1224756] Re: Pulseaudio should integrate with trust-store
Hi, I see the bug is closed and bugfix is released. There was bounty for fixing
this bug.
Person who fixed the issue, can claim to bountysource.com to get money. The
amount is small, but still.
https://www.bountysource.com/issues/3820281-pulseaudio-should-integrate-
with-trust-store
--
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/1224756
Title:
Pulseaudio should integrate with trust-store
Status in Canonical System Image:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
Currently the 'audio' policy group allows access to pulseaudio which
allows apps to use the microphone and eavesdrop on the user.
Pulseaudio needs to be modified to use trust-store, like location-
service does. Integrating with trust-store means that when an app
tries use the microphone via pulseaudio, pulseaudio will contact
trust-store, the trust-store will prompt the user ("Foo wants to use
the microphone. Is this ok? Yes|No"), optionally cache the result and
return the result to pulseaudio. In this manner the user is given a
contextual prompt at the time of access by the app. Using caching this
decision can be remembered the next time. If caching is used, there
should be a method to change the decision in settings.
Targeting to T-Series for now, since the trust-store is not in a
reusable form yet.
Original description:
David and the security team (inspired by an observation from Rick) discussed
that when recording, pulseaudio should somehow unobtrusively show the user that
it is recording. The easiest thing to do would be for pulseaudio to alert
indicator-sound which would then turn its icon red (similar to
indicator-message turning blue with new messages). Marking 'high' because apps
with access to pulseaudio can currently eavedrop on users. If the app is
allowed to do networking (the default for apps), then it can ship that
information off to a server somewhere.
Note 1, the alert to indicator-sound must happen via the out of
process pulseaudio server and not the confined app itself to be
effective.
Note 2, we should consider how to enforce this for foreground apps
only. Application lifecycle should probably handle this for 13.10
(apps are suspended if not in foreground or if the screensaver is on),
but we don't want an app on the converged device to record in the
background when the user isn't paying attention. Example eavesdropping
attack: start recording only when the screensaver is on (perhaps
inhibiting the screensaver during recording would be enough).
: "On the phone, if
an app tries to access your ... microphone ... or video recording,
this should be subject to permission. “Video recording” should be
separate from “Camera” so that an app does not need two permissions
when recording video, one for the camera and one for the microphone.
If an app has permission to record video, it should have access to the
microphone whenever it is recording video..."
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1224756/+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 1581470] Re: gnome-language-selector crashes when trying to drag English to the top
*** This bug is a duplicate of bug 1581567 *** https://bugs.launchpad.net/bugs/1581567 I have error when i tried change regional format to Russian: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 67, in wrapper res = f(*args, **kwargs) File "/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 79, in wrapper res = f(*args, **kwargs) File "/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 1096, in on_combobox_locale_chooser_changed self.writeUserFormats() File "/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", line 777, in writeUserFormats self.writeUserFormatsSetting(userFormats=code) File "/usr/lib/python3/dist-packages/LanguageSelector/LanguageSelector.py", line 75, in writeUserFormatsSetting iface.SetFormatsLocale(macr['SYSLOCALE']) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.Accounts.Error.PermissionDenied: Not authorized -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1581470 Title: gnome-language-selector crashes when trying to drag English to the top Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: Fix Committed Bug description: CID: 201409-15485 I have this 16.04 system configured in Traditional Chinese (Taiwan), but when I was trying to drag "English (United States)" back to the top, the language selector will crash. Steps: 1. Boot and make sure the system using Traditional Chinese (Taiwan) 2. Open Language Settings 3. Try to change the order by dragging English (United States) to the top. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: language-selector-gnome 0.165.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 13 06:55:03 2016 InstallationDate: Installed on 2016-05-04 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1581470/+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 971864] Re: ValueError: could not convert string to float: k_latency=0.850
Gordon Mckeown (thefluffyone), thanks! -- 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/971864 Title: ValueError: could not convert string to float: k_latency=0.850 Status in apt package in Ubuntu: Confirmed Bug description: /etc/cron.daily/apt: Traceback (most recent call last): File "/usr/sbin/update-apt-xapian-index", line 101, in if not indexer.setupIndexing(force=opts.force, system=opts.pkgfile is None): File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 513, in setupIndexing addon.obj.init(dict(values=self.values), self.progress) File "/usr/share/apt-xapian-index/plugins/cataloged_time.py", line 72, in init self._package_cataloged_time = cPickle.load(open(self._packages_cataloged_file)) ValueError: could not convert string to float: k_latency=0.850 This error is thrown from time to time from all versions of Ubuntu from 10.10 on upward: Ubuntu 10.10 Ubuntu 11.04 Ubuntu 11.10 Ubuntu 12.04 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: apt 0.8.16~exp5ubuntu13.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-virtual 3.0.22 Uname: Linux 3.0.0-17-virtual x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Apr 2 22:08:38 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to oneiric on 2011-09-16 (199 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/971864/+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 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor
Is 12.04 Precise affected by this vulnerability? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1476662 Title: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor Status in lxc package in Ubuntu: Fix Released Bug description: lxc-start shuffles around mounts using helper directory /usr/lib/x86_64-linux-gnu/lxc (guest root fs is mounted here) It then modifies mounts operating in guest root directory before invoking init. As it does not check if all mount points are directories, a malicious guest may modify its internal structure before shutdown (or was created using manipulated image) and then when started again, guest may * Access the whole host root filesystem * Block switching from lxc-start apparmor profile to lxc-container- default # Real putold before pivot-root (root fs will end here) mkdir -p /x/lxc_putold # Faked putold ln -s /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold lxc_putold mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc touch /usr/lib/x86_64-linux-gnu/lxc/x/lxc_putold/proc/mounts # proc fake mkdir -p /x/proc umount /proc rmdir /proc ln -s /usr/lib/x86_64-linux-gnu/lxc/x/proc proc mkdir -p /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr /usr/lib/x86_64-linux-gnu/lxc/x/proc/self touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/1/attr/current touch /usr/lib/x86_64-linux-gnu/lxc/x/proc/self/status The issue was also found during https://service.ait.ac.at/security/2015/LxcSecurityAnalysis.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+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 1027428] Re: half-maximized window follows to other desktop views
Hello ! Since I have upgraded to Trusty this bug does not appear. I'm not sure whether or not it still exists in 12.04 or somewhere in the middle. Thanks, Andrey Gelman On 09/18/2015 02:45 PM, Andrea Azzarone wrote: > hank you for taking the time to report this bug. We have tried to > recreate this on the latest release of Ubuntu and cannot reproduce it. > This bug is being marked as Invalid. If you believe the problem to > still exist in the latest version of Ubuntu please comment on why that > is the case and change the bug status to NEW. > > ** Changed in: unity > Status: New => Invalid > > ** Changed in: unity (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1027428 Title: half-maximized window follows to other desktop views Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: gnome-terminal window maximized to half-size (shortcut Ctrl-Alt-Keypad8) ... When I switch the desktop view using the view switcher (as opposed to using keyboard shortcuts Ctrl-Alt-Arrow), this half-maximized window follows to that desktop view as well. However, this behaviour does not copy the 'Always on Visible Workspace' behaviour, as on the 'stranger desktop' the terminal window is not focused (and cannot be focused) - the cursor bar is not filled, it does not respond to keystrokes, if one right-clicks its area, the appearing menu is related to the underlying desktop. Notes: - doesn't happen only with gnome-terminal. Observed also with nautilus, firefox ... everyone ? - doesn't happen only with top-half-maximized windows, but (!) doesn't seem to happen with left/right-half-maximized windows. - persists from Oneiric - as was already mentioned, doesn't occur with keyboard shortcuts switching the desktop. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Jul 21 18:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1027428/+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 1187552] Re: a window is shifted when I switch workspaces
As of Trusty - this bug seems to disappear. I am not sure whether or not it still appears in 12.04 or somewhere in the middle. Thanks, Andrey On 09/18/2015 04:13 PM, Andrea Azzarone wrote: > Thank you for taking the time to report this bug. We have tried to > recreate this on the latest release of Ubuntu and cannot reproduce it. > This bug is being marked as Invalid. If you believe the problem to > still exist in the latest version of Ubuntu please comment on why that > is the case and change the bug status to NEW. > > ** Changed in: unity > Status: New => Invalid > > ** Changed in: unity (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1187552 Title: a window is shifted when I switch workspaces Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Reproduce scenario: - Ctrl-Alt-T - open new gnome-terminal - Ctrl-Alt-KP2 - half-maximize this gnome-terminal - Ctrl-Alt-ArrowDown - switch to another workspace - Ctrl-Alt-ArrowUp - switch workspace back The result: the terminal window is shifted left below the Unity bar. Refer to attached screenshots. Note: - With other applications (not gnome-terminal) might work and might not work. - If one uses workspace switcher instead of keyboard shortcuts, for workspace switching, might not get reproduced - Persists for long time ... I think from Oneiric ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.18.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44 Uname: Linux 3.2.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,place,imgpng,resize,compiztoolbox,unitymtgrabhandles,mousepoll,gnomecompat,grid,move,regex,session,vpswitch,snap,animation,wall,expo,workarounds,fade,ezoom,scale,unityshell] Date: Tue Jun 4 23:07:57 2013 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1187552/+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 772214] Re: default state file location is wrong in manpage
** Changed in: logrotate (Ubuntu) Status: Confirmed => Fix Committed -- 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/772214 Title: default state file location is wrong in manpage Status in logrotate package in Ubuntu: Fix Committed Status in logrotate package in Debian: New Bug description: Binary package hint: logrotate manpage says that /var/lib/logrotate.status is the default state file, but it's actually /var/lib/logrotate/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/772214/+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 772214] Re: default state file location is wrong in manpage
** Bug watch added: Debian Bug tracker #775421 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775421 ** Also affects: logrotate (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775421 Importance: Unknown Status: Unknown -- 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/772214 Title: default state file location is wrong in manpage Status in logrotate package in Ubuntu: Confirmed Status in logrotate package in Debian: Unknown Bug description: Binary package hint: logrotate manpage says that /var/lib/logrotate.status is the default state file, but it's actually /var/lib/logrotate/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/772214/+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 1484474] [NEW] mktime throwing an exception when special time tuple passed
Public bug reported:
How to discover a bug.
Run the following command
python -c import time; time.mktime((2011, 3, 27, 2, 0, 0, 6, 86, 0));
print('OK')
On Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-44-generic x86_64) with tzdata package
version 2014i-0ubuntu0.14.04 it will say:
OK
On Ubuntu Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-37-generic x86_64) with tzdata
package version 2015d-0ubuntu0.14.04 it will say:
Traceback (most recent call last):
File string, line 1, in module
OverflowError: mktime argument out of range
** Affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Tags: mktime overflowerror tzdata
--
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/1484474
Title:
mktime throwing an exception when special time tuple passed
Status in tzdata package in Ubuntu:
New
Bug description:
How to discover a bug.
Run the following command
python -c import time; time.mktime((2011, 3, 27, 2, 0, 0, 6, 86, 0));
print('OK')
On Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-44-generic x86_64) with tzdata
package version 2014i-0ubuntu0.14.04 it will say:
OK
On Ubuntu Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-37-generic x86_64) with tzdata
package version 2015d-0ubuntu0.14.04 it will say:
Traceback (most recent call last):
File string, line 1, in module
OverflowError: mktime argument out of range
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1484474/+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 1484474] Re: mktime throwing an exception when special time tuple passed
** Description changed:
- How to discover a bug.
- Run the following command
-
- python -c import time; time.mktime((2011, 3, 27, 2, 0, 0, 6, 86, 0));
print('OK')
-
- On Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-44-generic x86_64) with tzdata
package version 2014i-0ubuntu0.14.04 it will say:
- OK
-
- On Ubuntu Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-37-generic x86_64) with tzdata
package version 2015d-0ubuntu0.14.04 it will say:
- Traceback (most recent call last):
- File string, line 1, in module
- OverflowError: mktime argument out of range
+ I was wrong. It is not a bug. Delete this.
** Changed in: tzdata (Ubuntu)
Status: New = Invalid
--
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/1484474
Title:
mktime throwing an exception when special time tuple passed
Status in tzdata package in Ubuntu:
Invalid
Bug description:
I was wrong. It is not a bug. Delete this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1484474/+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 1481671] Re: [mos] rsyslog periodically crashes with *** glibc detected *** rsyslogd: double free or corruption (fasttop) preventing log into the system
** Also affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- 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/1481671 Title: [mos] rsyslog periodically crashes with *** glibc detected *** rsyslogd: double free or corruption (fasttop) preventing log into the system Status in Mirantis OpenStack: Incomplete Status in rsyslog package in Ubuntu: New Bug description: Rsyslog crashes every 10-14 days on MogoDB nodes with coredump in /var/log/messages: 46Aug 4 15:01:56 node-115 rsyslogd: rsyslogd's groupid changed to 103 46Aug 4 15:01:56 node-115 rsyslogd: rsyslogd's userid changed to 101 6Aug 4 15:02:12 node-115 kernel: imklog 5.8.6, log source = /proc/kmsg started. 46Aug 4 15:02:12 node-115 rsyslogd: [origin software=rsyslogd swVersion=5.8.6 x-pid=58757 x-info=http://www. rsyslog.com] start 46Aug 4 15:02:12 node-115 rsyslogd: rsyslogd's groupid changed to 103 46Aug 4 15:02:12 node-115 rsyslogd: rsyslogd's userid changed to 101 6Aug 4 15:02:13 node-115 kernel: imklog 5.8.6, log source = /proc/kmsg started. 46Aug 4 15:02:13 node-115 rsyslogd: [origin software=rsyslogd swVersion=5.8.6 x-pid=58773 x-info=http://www. rsyslog.com] start 46Aug 4 15:02:13 node-115 rsyslogd: rsyslogd's groupid changed to 103 46Aug 4 15:02:13 node-115 rsyslogd: rsyslogd's userid changed to 101 6Aug 4 15:02:21 node-115 kernel: imklog 5.8.6, log source = /proc/kmsg started. 46Aug 4 15:02:21 node-115 rsyslogd: [origin software=rsyslogd swVersion=5.8.6 x-pid=58788 x-info=http://www. rsyslog.com] start 46Aug 4 15:02:21 node-115 rsyslogd: rsyslogd's groupid changed to 103 46Aug 4 15:02:21 node-115 rsyslogd: rsyslogd's userid changed to 101 *** glibc detected *** rsyslogd: double free or corruption (fasttop): 0x7f5e88032100 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7e846)[0x7f5ea2101846] rsyslogd[0x42ee36] rsyslogd[0x431697] rsyslogd[0x431ce7] rsyslogd(wtiWorker+0xc3)[0x42b513] rsyslogd[0x42a78a] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f5ea2855e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5ea217731d] === Memory map: 0040-00456000 r-xp 08:03 8132346 /usr/sbin/rsyslogd 00656000-00658000 r--p 00056000 08:03 8132346 /usr/sbin/rsyslogd 00658000-0065e000 rw-p 00058000 08:03 8132346 /usr/sbin/rsyslogd 0065e000-0065f000 rw-p 00:00 0 00f18000-00f39000 rw-p 00:00 0 [heap] 00f39000-00f7b000 rw-p 00:00 0 [heap] 7f5e8400-7f5e8404 rw-p 00:00 0 7f5e8404-7f5e8800 ---p 00:00 0 7f5e8800-7f5e88043000 rw-p 00:00 0 7f5e88043000-7f5e8c00 ---p 00:00 0 7f5e8c00-7f5e8c1eb000 rw-p 00:00 0 7f5e8c1eb000-7f5e9000 ---p 00:00 0 ... memory map ... Full memory map could be found in attached 'messages' log. When rsyslog crashes in this manner it is impossible to login into the system. Process /bin/login successfully authenticates user, but does not born shell process, constantly waiting for rsyslog reading login log message from Unix socket. Obviously Fuel master reports that node in 'False' state (because it becomes non-sshable too). Workaround: fully restart rsyslog after crash (service rsyslog restart) if some active login session is present or reboot the server if not. MOS 6.0, Ubuntu 12.04. Rsyslog v. 5.8.6 (from Fuel node repos). Rsyslog config files placed in rsyslog folder of attached archive. To manage notifications about this bug go to: https://bugs.launchpad.net/mos/+bug/1481671/+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 1463327] [NEW] Cannot Lock to Launcher Android Studio icon
Public bug reported: It does not matter if you select Lock to Launcher or not. Upon exiting Android Studio editor, the icon would disappear. Creating the .desktop file manually, also solves the problem only partially: upon clicking on the Android Studio icon, yet another Android Studio icon would appear in the bottom of the Unity bar -- see screenshot attached (look at the icon with a green calipers). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150521.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Tue Jun 9 12:20:06 2015 InstallationDate: Installed on 2011-10-23 (1324 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (380 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: screenshot.png https://bugs.launchpad.net/bugs/1463327/+attachment/4411955/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1463327 Title: Cannot Lock to Launcher Android Studio icon Status in unity package in Ubuntu: New Bug description: It does not matter if you select Lock to Launcher or not. Upon exiting Android Studio editor, the icon would disappear. Creating the .desktop file manually, also solves the problem only partially: upon clicking on the Android Studio icon, yet another Android Studio icon would appear in the bottom of the Unity bar -- see screenshot attached (look at the icon with a green calipers). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150521.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Tue Jun 9 12:20:06 2015 InstallationDate: Installed on 2011-10-23 (1324 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (380 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1463327/+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 1437447] Re: avconv error couldn't load module ... gnome-keyring-pkcs11.so
** Package changed: devede (Ubuntu) = libav (Ubuntu) ** Description changed: Calling avconv -version prints error: - $ avconv -version - p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory + $ avconv -version + p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory - - Error disappears after installing package libp11-kit-gnome-keyring, but it is not a dependency of avconv. + Error disappears after installing package libp11-kit-gnome-keyring, + but it is not a dependency of libav-tools. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1437447 Title: avconv error couldn't load module ... gnome-keyring-pkcs11.so Status in libav package in Ubuntu: New Bug description: Calling avconv -version prints error: $ avconv -version p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory Error disappears after installing package libp11-kit-gnome-keyring, but it is not a dependency of libav-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1437447/+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 995473] Re: no way to use dconf-editor with keyboard only
I would like to start editing values with Ret or F2 or Space or whatever, without needing to double click. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/995473 Title: no way to use dconf-editor with keyboard only Status in d-conf package in Ubuntu: Confirmed Bug description: I can't open items on the left panel with a keyboard only, are there any shortcuts [planned]? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dconf-tools 0.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sun May 6 15:57:55 2012 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: d-conf UpgradeStatus: Upgraded to precise on 2012-05-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/995473/+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 995473] Re: no way to use dconf-editor with keyboard only
Or via context menu (key between Alt and Control -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/995473 Title: no way to use dconf-editor with keyboard only Status in d-conf package in Ubuntu: Confirmed Bug description: I can't open items on the left panel with a keyboard only, are there any shortcuts [planned]? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dconf-tools 0.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sun May 6 15:57:55 2012 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: d-conf UpgradeStatus: Upgraded to precise on 2012-05-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/995473/+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 1387134] Re: when enabled nvidia graphics card, desktop freezes
Still same in Xubuntu 14.04/14.10 also it is not only related to Asus UX32 series laptops, found same issue on Asus U36 SD with Nvidia 520 GT on board. I supprised that only a few people reported this, believe a lot of people have this pain -- 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/1387134 Title: when enabled nvidia graphics card, desktop freezes Status in xorg package in Ubuntu: Confirmed Bug description: Screen freezes occasionally while simply browsing the web, can be recovered by ctrl+alt+f1 and ctrl+alt+f7 This has been the case in 14.04, and it's still the case in 14.10 (64 bit) Asus UX32V 331.89-0ubuntu5 *** 331.89-0ubuntu5 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Oct 29 12:40:01 2014 DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1507] Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507] InstallationDate: Installed on 2014-05-31 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash processor.ignore_ppc=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Oct 29 12:00:13 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4931 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1387134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1057186] Re: Modem functionality of the Huawei E173 and E3131 doesn't work
Thank you, Danillo. This was the only thing that worked for me on Ubuntu 14.04 and Mint. Yes, the bug is still happening in saucy and trusty. Haven't tested utopic yet but I bet it's the same there because every bug I have found on this topic has been marked as allegedly resolved or expired despite people commenting that it's still broken. This isn't just Huawei devices, it's ANY modem that spawns multiple /dev/ttyUSB interfaces - Sierra devices, for instance. Why can't at least an option be added to manually choose the correct port? Fedora Network Manager apparently has that, as indicated by Huawei's installation manual, and it's a very simple solution. Either way, it's unacceptable that this bug exists for so long and is ignored, forcing people to resort to wvdial or to buy another modem. Here is a list of related bugs: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/819784 https://bugs.launchpad.net/bugs/504035 https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/557449 Can something please be done about it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1057186 Title: Modem functionality of the Huawei E173 and E3131 doesn't work Status in ModemManager (with NetworkManager support): Fix Released Status in modemmanager package in Ubuntu: Triaged Bug description: Modem functionality of Huawei E173 works in 12.04 but not in later releases, although it can be read as a drive. Otherwise, the modem itself is recognized by the modem-manager but fails to connect to Internet. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: modemmanager 0.6~git201206221719.8289a64-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Wed Sep 26 23:37:21 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) There is a potential fix in upstream branch 06-huawei. To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1057186/+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 1177934] Re: open window follows when I switch workspace
Apparently no. On 12/11/2014 07:47 AM, Andrea Azzarone wrote: Is this still a problem? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1177934 Title: open window follows when I switch workspace Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: This bug persists from Oneiric - fix it already ! On empty desktop open gnome-terminal. Using the workspace switcher (not the keyboard shortcut) switch to another workspace. The gnome-terminal window follows to that workspace as well. This behaviour is bogus and should really be fixed ! This bug happens with other applications as well, but this particular scenario is one that never misses the target. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed May 8 22:10:31 2013 InstallationDate: Installed on 2013-05-04 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1177934/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access
I now have 3 clients (all up to date, 32 and 64 bit installations) for whom it's happening on 14.04: 1) 24 inch 1920x1080 Samsung screen connected via HDMI (desktop) 2) 10 inch 1280x800 screen (netbook) 3) 15.6 inch 1920x1080 screen (laptop I mentioned previously) Yet on my own 15.6 1920x1080 screen (another laptop) this never happened. I think it's safe to assume that this has little to nothing to do with high DPI judging by examples above. Now what we need is a way to permanently deactivate this annoying setting so it never comes back unless we want it to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 66 Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at a000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 828538] Re: Europe/Moscow not updated
Please see bug #1377813 -- 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/828538 Title: Europe/Moscow not updated Status in “tzdata” package in Ubuntu: Confirmed Bug description: Please, update zone Russia (Europe/Moscow, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/828538/+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 1377813] Re: tzdata SRU to 2014f because of law changes in Russia
This is critial bug for users in Russia -- 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/1377813 Title: tzdata SRU to 2014f because of law changes in Russia Status in “tzdata” package in Ubuntu: Confirmed Status in “tzdata” source package in Precise: Confirmed Status in “tzdata” source package in Trusty: Confirmed Status in “tzdata” package in Debian: Unknown Bug description: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1377813/+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 1377813] [NEW] tzdata SRU to 2014f because of law changes in Russia
Public bug reported: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- 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/1377813 Title: tzdata SRU to 2014f because of law changes in Russia Status in “tzdata” package in Ubuntu: New Bug description: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1377813/+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 1358827] [NEW] /etc/bash.bashrc checks for admin instead of sudo group
Public bug reported: Since ubuntu 12.04 sudo group is used for granting root privileges. AFAIK admin group was retained for backward compatibility only, at least Server Guige for Ubuntu 14.04 says that one should use sudo group for root access. Currently /etc/bash.bashrc check only for admin group. If the user belong to admin group, hint message on how to get root access may be printed. I think bashrc should check for sudo group also. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1358827 Title: /etc/bash.bashrc checks for admin instead of sudo group Status in “bash” package in Ubuntu: New Bug description: Since ubuntu 12.04 sudo group is used for granting root privileges. AFAIK admin group was retained for backward compatibility only, at least Server Guige for Ubuntu 14.04 says that one should use sudo group for root access. Currently /etc/bash.bashrc check only for admin group. If the user belong to admin group, hint message on how to get root access may be printed. I think bashrc should check for sudo group also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1358827/+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
