[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Yoga Slim 9 14ITL5 Ubuntu 20.04 kernel 5.13.0-30-generic No sound on front speakers -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1943130] Re: Nvidia drivers info
Sending this bug after, solved by change drivers, i can change it back to 470, and perform debug commands if needed (gather logs etc.) -- 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/1943130 Title: Nvidia drivers info Status in xorg package in Ubuntu: New Bug description: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1943130/+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 1943130] [NEW] Nvidia drivers info
Public bug reported: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 15:15:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8803] InstallationDate: Installed on 2021-08-31 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C91 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550 TOMAHAWK (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943130 Title: Nvidia drivers info Status in xorg package in Ubuntu: New Bug description: After turn on mu PC, it doesn't send signal to the second monitor. (with driver "nvidia-driver-470(proprietary tested)" After change it to: "nvidia-driver-460(proprietary)" problem solved. Looks like new kernel update have conflict with nvidia - 470 driver. (because yesterday it was fine but today is broken, and made me to change the driver) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same problem: - Kernel: 5.8.0-50-generic - OS: Ubuntu 20.04.1 - Machine: HP EliteBook 830 G6 - Headset: BUXTON BHP 7501 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same problem: - Kernel: 5.8.0-50-generic - OS: Ubuntu 20.04.1 - Machine: HP EliteBook 830 G6 - Headset: BUXTON BHP 7501 -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 This is also happening with my JBL TUNE120TWS on Ubuntu 20.04.1 Can not switch to HFP/HSP profile in a GUI-settings menu. Sound works fine, but have nothing to pick up from in the list of inputs. Hope this could help. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1875424] [NEW] The image breaks after exiting the mode suspend
Public bug reported: radeon :01:00.0: ring 0 stalled for more than 30212msec ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 18:19:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RV620/M82 [Mobility Radeon HD 3450/3470] [1043:19d3] InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. M51SE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1407f934-4717-4e84-bb64-fef8e4687821 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51SE 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.:bvr204:bd02/20/2008:svnASUSTeKComputerInc.:pnM51SE:pvr1.0:rvnASUSTeKComputerInc.:rnM51SE:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51SE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "20200427_182027.jpg" https://bugs.launchpad.net/bugs/1875424/+attachment/5361731/+files/20200427_182027.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875424 Title: The image breaks after exiting the mode suspend Status in xorg package in Ubuntu: New Bug description: radeon :01:00.0: ring 0 stalled for more than 30212msec ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 18:19:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RV620/M82 [Mobility Radeon HD 3450/3470] [1043:19d3] InstallationDate: Installed on 2020-04-25 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. M51SE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1407f934-4717-4e84-bb64-fef8e4687821 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51SE 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.:bvr204:bd02/20/2008:svnASUSTeKComputerInc.:pnM51SE:pvr1.0:rvnASUSTeKComputerInc.:rnM51SE:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51SE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core:
[Touch-packages] [Bug 1768026] Re: echo message hides cursor
1 for adding the fix to 18.04 LTS. When will it be fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1768026 Title: echo message hides cursor Status in vim: Fix Released Status in vim package in Ubuntu: Confirmed Bug description: https://github.com/w0rp/ale/issues/1536#issuecomment-385056702 upstream bug https://github.com/vim/vim/issues/2612 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:16:35 2018 InstallationDate: Installed on 2017-05-17 (347 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1768026/+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 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
Still have it in Ubuntu 19.10. -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: Fix Released Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+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 1815615] [NEW] Xorg freeze
Public bug reported: [ 290.765205] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=20358, emitted seq=20361 [ 290.765212] [drm] GPU recovery disabled. [ 485.063911] INFO: task kworker/u32:1:50 blocked for more than 120 seconds. [ 485.063922] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 485.063925] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 485.063929] kworker/u32:1 D050 2 0x8000 [ 485.063952] Workqueue: events_unbound commit_work [drm_kms_helper] [ 485.063955] Call Trace: [ 485.063967] __schedule+0x29e/0x840 [ 485.063971] schedule+0x2c/0x80 [ 485.063974] schedule_preempt_disabled+0xe/0x10 [ 485.063977] __ww_mutex_lock.isra.11+0x3d8/0x760 [ 485.063981] __ww_mutex_lock_slowpath+0x16/0x20 [ 485.063983] ww_mutex_lock+0x34/0x50 [ 485.064115] amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu] [ 485.064213] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 485.064216] ? __switch_to_asm+0x40/0x70 [ 485.064219] ? __switch_to_asm+0x34/0x70 [ 485.064221] ? wait_for_completion_timeout+0x38/0x140 [ 485.064223] ? __switch_to_asm+0x40/0x70 [ 485.064225] ? __switch_to_asm+0x34/0x70 [ 485.064227] ? __switch_to_asm+0x40/0x70 [ 485.064239] commit_tail+0x42/0x70 [drm_kms_helper] [ 485.064248] commit_work+0x12/0x20 [drm_kms_helper] [ 485.064253] process_one_work+0x20f/0x410 [ 485.064256] worker_thread+0x34/0x400 [ 485.064258] kthread+0x120/0x140 [ 485.064261] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 485.064263] ? __kthread_parkme+0x70/0x70 [ 485.064266] ret_from_fork+0x22/0x40 [ 485.064463] INFO: task kworker/u32:14:2793 blocked for more than 120 seconds. [ 485.064467] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 485.064468] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 485.064470] kworker/u32:14 D0 2793 2 0x8000 [ 485.064483] Workqueue: events_unbound commit_work [drm_kms_helper] [ 485.064484] Call Trace: [ 485.064487] __schedule+0x29e/0x840 [ 485.064489] schedule+0x2c/0x80 [ 485.064491] schedule_timeout+0x258/0x360 [ 485.064584] ? optc1_get_crtc_scanoutpos+0x69/0xa0 [amdgpu] [ 485.064590] dma_fence_default_wait+0x20a/0x280 [ 485.064592] ? dma_fence_release+0xa0/0xa0 [ 485.064595] dma_fence_wait_timeout+0xe7/0x110 [ 485.064598] reservation_object_wait_timeout_rcu+0x201/0x340 [ 485.064663] ? amdgpu_get_vblank_counter_kms+0x111/0x160 [amdgpu] [ 485.064757] amdgpu_dm_do_flip+0x12c/0x3a0 [amdgpu] [ 485.064852] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 485.064855] ? __switch_to_asm+0x40/0x70 [ 485.064857] ? __switch_to_asm+0x34/0x70 [ 485.064859] ? wait_for_completion_timeout+0x38/0x140 [ 485.064861] ? __switch_to_asm+0x40/0x70 [ 485.064863] ? __switch_to_asm+0x34/0x70 [ 485.064865] ? __switch_to_asm+0x40/0x70 [ 485.064876] commit_tail+0x42/0x70 [drm_kms_helper] [ 485.064886] commit_work+0x12/0x20 [drm_kms_helper] [ 485.064889] process_one_work+0x20f/0x410 [ 485.064891] worker_thread+0x34/0x400 [ 485.064894] kthread+0x120/0x140 [ 485.064896] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 485.064898] ? __kthread_parkme+0x70/0x70 [ 485.064901] ret_from_fork+0x22/0x40 [ 538.507722] r8169 :02:00.0: invalid short VPD tag 00 at offset 1 [ 538.507750] pcieport :00:01.3: AER: Multiple Corrected error received: :00:01.0 [ 538.507772] pcieport :00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 538.507781] pcieport :00:01.3: device [1022:15d3] error status/mask=1100/6000 [ 538.507787] pcieport :00:01.3:[ 8] Rollover [ 538.507791] pcieport :00:01.3:[12] Timeout [ 574.828588] RTW: WARN [TXFOVW] [ 574.831312] RTW: WARN [TXFOVW] [ 605.900149] INFO: task kworker/u32:1:50 blocked for more than 120 seconds. [ 605.900156] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 605.900159] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 605.900162] kworker/u32:1 D050 2 0x8000 [ 605.900183] Workqueue: events_unbound commit_work [drm_kms_helper] [ 605.900185] Call Trace: [ 605.900195] __schedule+0x29e/0x840 [ 605.900199] schedule+0x2c/0x80 [ 605.900202] schedule_preempt_disabled+0xe/0x10 [ 605.900204] __ww_mutex_lock.isra.11+0x3d8/0x760 [ 605.900208] __ww_mutex_lock_slowpath+0x16/0x20 [ 605.900210] ww_mutex_lock+0x34/0x50 [ 605.900322] amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu] [ 605.900420] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 605.900423] ? __switch_to_asm+0x40/0x70 [ 605.900425] ? __switch_to_asm+0x34/0x70 [ 605.900428] ? wait_for_completion_timeout+0x38/0x140 [ 605.900430] ? __switch_to_asm+0x40/0x70 [ 605.900432] ? __switch_to_asm+0x34/0x70 [ 605.900434] ? __switch_to_asm+0x40/0x70 [ 605.900445] commit_tail+0x42/0x70 [drm_kms_helper] [ 605.900455]
[Touch-packages] [Bug 1788286] [NEW] The screen collapses after getting out of sleep
Public bug reported: E): enp2s0: link becomes ready Aug 20 13:49:02 M51SE kernel: [ 272.572110] radeon :01:00.0: ring 0 stalled for more than 10236msec Aug 20 13:49:02 M51SE kernel: [ 272.572126] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:03 M51SE kernel: [ 273.084086] radeon :01:00.0: ring 0 stalled for more than 10748msec Aug 20 13:49:03 M51SE kernel: [ 273.084099] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:03 M51SE kernel: [ 273.596091] radeon :01:00.0: ring 0 stalled for more than 11260msec Aug 20 13:49:03 M51SE kernel: [ 273.596107] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:04 M51SE kernel: [ 274.108084] radeon :01:00.0: ring 0 stalled for more than 11772msec Aug 20 13:49:04 M51SE kernel: [ 274.108098] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:04 M51SE kernel: [ 274.620076] radeon :01:00.0: ring 0 stalled for more than 12284msec Aug 20 13:49:04 M51SE kernel: [ 274.620088] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:05 M51SE kernel: [ 275.136059] radeon :01:00.0: ring 0 stalled for more than 12800msec Aug 20 13:49:05 M51SE kernel: [ 275.136069] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:05 M51SE kernel: [ 275.644077] radeon :01:00.0: ring 0 stalled for more than 13308msec Aug 20 13:49:05 M51SE kernel: [ 275.644090] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:06 M51SE kernel: [ 276.156083] radeon :01:00.0: ring 0 stalled for more than 13820msec Aug 20 13:49:06 M51SE kernel: [ 276.156097] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:06 M51SE kernel: [ 276.668078] radeon :01:00.0: ring 0 stalled for more than 14332msec Aug 20 13:49:06 M51SE kernel: [ 276.668090] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:07 M51SE kernel: [ 277.180071] radeon :01:00.0: ring 0 stalled for more than 14844msec Aug 20 13:49:07 M51SE kernel: [ 277.180083] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:07 M51SE kernel: [ 277.692072] radeon :01:00.0: ring 0 stalled for more than 15356msec Aug 20 13:49:07 M51SE kernel: [ 277.692085] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:08 M51SE kernel: [ 278.204077] radeon :01:00.0: ring 0 stalled for more than 15868msec Aug 20 13:49:08 M51SE kernel: [ 278.204090] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:08 M51SE kernel: [ 278.716072] radeon :01:00.0: ring 0 stalled for more than 16380msec Aug 20 13:49:08 M51SE kernel: [ 278.716085] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:09 M51SE kernel: [ 279.228080] radeon :01:00.0: ring 0 stalled for more than 16892msec Aug 20 13:49:09 M51SE kernel: [ 279.228093] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:09 M51SE kernel: [ 279.740071] radeon :01:00.0: ring 0 stalled for more than 17404msec Aug 20 13:49:09 M51SE kernel: [ 279.740083] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:10 M51SE kernel: [ 280.252071] radeon :01:00.0: ring 0 stalled for more than 17916msec Aug 20 13:49:10 M51SE kernel: [ 280.252083] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:10 M51SE kernel: [ 280.764076] radeon :01:00.0: ring 0 stalled for more than 18428msec Aug 20 13:49:10 M51SE kernel: [ 280.764089] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:11 M51SE kernel: [ 281.276048] radeon :01:00.0: ring 0 stalled for more than 18940msec Aug 20 13:49:11 M51SE kernel: [ 281.276059] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:11 M51SE kernel: [ 281.788070] radeon :01:00.0: ring 0 stalled for more than 19452msec Aug 20 13:49:11 M51SE kernel: [ 281.788082] radeon :01:00.0: GPU
[Touch-packages] [Bug 1770706] [NEW] openvswitch with ifupdown after reboot
Public bug reported: Recently I needed to install OVS on fresh ubuntu 18.04. 1). # lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 2). # apt-cache policy openvswitch-switch openvswitch-switch: Installed: 2.9.0-0ubuntu1 Candidate: 2.9.0-0ubuntu1 Version table: *** 2.9.0-0ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3). OVS configured after reboot. 4). OVS was not configured after reboot. After this actions: - remove netplan.io - install ifupdown - install openvswitch-switch - add verified ovs related statements to /etc/network/interfaces - reboot I got this in journal: мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1328]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1368]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1392]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1424]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. мая 11 16:28:42 host2.lab.atlantis.ru ovs-vsctl[2041]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2091]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2137]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. мая 11 16:30:05 host2.lab.atlantis.ru ovs-vsctl[2243]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:30:06 host2.lab.atlantis.ru ovs-vsctl[2293]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:30:07 host2.lab.atlantis.ru ovs-vsctl[2339]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. Problem was fixed after the following changes to unit files: # diff /lib/systemd/system/ovsdb-server.service /etc/systemd/system/ovsdb-server.service 4c4 < Before=network.target network.service --- > Before=network.target networking.service # diff /lib/systemd/system/ovs-vswitchd.service /etc/systemd/system/ovs-vswitchd.service 4c4 < Before=network.target network.service --- > Before=network.target networking.service ** 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/1770706 Title: openvswitch with ifupdown after reboot Status in systemd package in Ubuntu: New Bug description: Recently I needed to install OVS on fresh ubuntu 18.04. 1). # lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 2). # apt-cache policy openvswitch-switch openvswitch-switch: Installed: 2.9.0-0ubuntu1 Candidate: 2.9.0-0ubuntu1 Version table: *** 2.9.0-0ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3). OVS configured after reboot. 4). OVS was not configured after reboot. After this actions: - remove netplan.io - install ifupdown - install openvswitch-switch - add verified ovs related statements to /etc/network/interfaces - reboot I got this in journal: мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1328]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1368]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1392]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1424]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. мая
[Touch-packages] [Bug 1767143] [NEW] package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1.3 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-39-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 26 17:27:57 2018 DuplicateSignature: package:ifupdown:0.8.10ubuntu1.3 Setting up ubuntu-make (17.03~xenial1) ... /var/lib/dpkg/info/ubuntu-make.postinst: 6: /var/lib/dpkg/info/ubuntu-make.postinst: register-python-argcomplete3: not found dpkg: error processing package ubuntu-make (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-04-01 (24 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: ifupdown Title: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed third-party-packages xenial -- 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/1767143 Title: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ifupdown package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1.3 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-39-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 26 17:27:57 2018 DuplicateSignature: package:ifupdown:0.8.10ubuntu1.3 Setting up ubuntu-make (17.03~xenial1) ... /var/lib/dpkg/info/ubuntu-make.postinst: 6: /var/lib/dpkg/info/ubuntu-make.postinst: register-python-argcomplete3: not found dpkg: error processing package ubuntu-make (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-04-01 (24 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: ifupdown Title: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1767143/+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 1694692] [NEW] Some GTK apps have empty window on the kernel 4.11.3
Public bug reported: After the kernel update on Linux Ubuntu 16.04 x64 from 4.11.2 to 4.11.3 some GUI apps become broken, the visual image is attached. For example, geary email app has empty GUI window and the following log: $ grep gear /var/log/syslog May 31 13:02:58 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed May 31 13:02:59 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop.dpkg-new file: cannot process file of type text/plain May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop.dpkg-tmp file: cannot process file of type text/plain May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop.dpkg-new file: cannot process file of type text/plain May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop.dpkg-tmp file: cannot process file of type text/plain May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop file: cannot process file of type application/x-desktop May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop file: cannot process file of type application/x-desktop May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop.dpkg-new file: cannot process file of type text/plain May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop.dpkg-new file: cannot process file of type text/plain May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop file: cannot process file of type application/x-desktop May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop file: cannot process file of type application/x-desktop May 31 13:08:46 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop.dpkg-new file: cannot process file of type text/plain May 31 13:08:46 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop.dpkg-new file: cannot process file of type text/plain May 31 13:08:47 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary.desktop file: cannot process file of type application/x-desktop May 31 13:08:47 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/geary-autostart.desktop file: cannot process file of type application/x-desktop May 31 13:12:10 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed May 31 13:21:51 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed Updating the Geary itself from the Ubuntu-default version 0.10 to 0.11 did not fixed the issue. Most of other apps works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) Uname: Linux 4.11.3-041103-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: 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 May 31 13:13:14 2017 DistUpgraded: 2016-09-11 19:36:31,920 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2218] InstallationDate: Installed on 2014-10-25 (948 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release
[Touch-packages] [Bug 1690520] Re: Scaling resets from 1.5 to 1 after screen lock / unlock
*** This bug is a duplicate of bug 1689356 *** https://bugs.launchpad.net/bugs/1689356 ** This bug has been marked a duplicate of bug 1689356 UI scale being reset to 1 everytime when display sleeps for a while -- 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/1690520 Title: Scaling resets from 1.5 to 1 after screen lock / unlock Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 17.04, I have a 4K (3840x2160) monitor connected to my computer. I have set the scaling to 1.5 (System Settings / Displays / Scale for menu and title bars). When I walk away from the computer, after a while the screen is locked. When I unlock it by entering my password, the scaling is reset to 1 and the Ubuntu menu bar at the top of the screen, the launcher and windows are all small. I have to go back to System Settings / Displays and set it back to 1.5. Locking / unlocking the desktop should not affect the scaling factor setting. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Sat May 13 11:06:24 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Graphics 540 [8086:2063] InstallationDate: Installed on 2017-05-06 (6 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=2278e5dc-858b-486d-9d4f-363aef26fab7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corp. dmi.board.vendor: Intel corporation version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 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: Sat May 13 09:02:20 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690520/+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 1587730] Re: graphic system freezes after a while, can still ssh into machine
Have the similar issue under lubuntu 16.04. Virtualbox 5.20. i5 GTX 960 Freez in firefox/libreoffice/chromium.. It helps to switch terminals CtrlAlt-F1 and back CtrlAlt-F7 Usaly I killall firefox from CtrlAlt-F1 (terminal alway works) But today I have just switched to new terminal and back and it helps. -- 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/1587730 Title: graphic system freezes after a while, can still ssh into machine Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 desktop with all updates up to date Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 SSD, Gigabyte GEForce GT710 graphics (nvidia chipset) Very light load. A few terminal windows, a few Firefox pages, Thunderbird, and VirtualBox (with the extension pack loaded) running one small Linux VM with 512Mb memory (very lightly loaded as it's only running bind9). I think (but don't have perfect certainty on this) that some of the crashes have happened without VirtualBox running. Also running rsync so that backuppc on a separate machine can back it up over the network (backuppc has been a real lifesaver with all the reinstallations!) After booting the system runs happily for a while then the GUI freezes. This can take a few hours or up to a day or two. You can still ssh into the system, and if you do "top" it typically shows 100% CPU load on systemd-timesync. The same happens whether I use nouveau or the proprietary nvidia driver (361) I have tried a complete reinstallation (4 times already, starting to get quite frustrating) using the proprietary drivers and NOT using the proprietary drivers and the same still happens. The most recent time was with nouveau, and Xorg.log has a number of entries like this: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) [0x7f31f98621f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) [0x7f31f9862a5d] (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228] (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) [0x7f3202d244a0] (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) [0x7f3202d244a0] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307] (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee] (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f3202d0f830] (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. Then at the end the last few are: [ 6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events. [ 6265.543] [mi] EQ processing has resumed after 1070 dropped events. [ 6265.543] [mi] This may be caused by a misbehaving driver monopolizing the server's resources. What cna the problem possibly be, especially as 16.04 is meant to be a stable release and an Nvidia GT710 card is hardly bleeding-edge? Help greatly appreciated! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Date: Wed Jun 1 13:22:13 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec] InstallationDate: Installed on 2016-06-01 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
[Touch-packages] [Bug 1539348] Re: udevadm info reports wrong ID_MODEL_ID and ID_VENDOR_ID for USB serial port
I have this bug on Fedora 23 with systemd-222 so it isn't Ubuntu specific. -- 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/1539348 Title: udevadm info reports wrong ID_MODEL_ID and ID_VENDOR_ID for USB serial port Status in qtserialport-opensource-src package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Running udevadm info with the device path of a virtual serial port created by a USB device (in this case a Particle Photon development board) returns the ID_MODEL_ID and ID_VENDOR_ID for the USB host controller instead of the Particle device. The consequence is mis-detection of the device associated with a virtual serial port in applications. udevadm info with the virtual serial port. Expect ID_MODEL_ID=c00a and ID_VENDOR_ID=2b04 $ udevadm info --query=property -p /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/tty/ttyACM0 DEVLINKS=/dev/serial/by-id/pci-Particle_Electron_050C-if00 /dev/serial/by-path/pci-:00:14.0-usb-0:1:1.0 DEVNAME=/dev/ttyACM0 DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/tty/ttyACM0 ID_BUS=pci ID_MODEL=Electron ID_MODEL_ENC=Electron ID_MODEL_FROM_DATABASE=7 Series/C210 Series Chipset Family USB xHCI Host Controller (Zenbook Prime UX31A) ID_MODEL_ID=0x1e31 ID_PATH=pci-:00:14.0-usb-0:1:1.0 ID_PATH_TAG=pci-_00_14_0-usb-0_1_1_0 ID_PCI_CLASS_FROM_DATABASE=Serial bus controller ID_PCI_INTERFACE_FROM_DATABASE=XHCI ID_PCI_SUBCLASS_FROM_DATABASE=USB controller ID_REVISION=0200 ID_SERIAL=Particle_Electron_050C ID_SERIAL_SHORT=050C ID_TYPE=generic ID_USB_CLASS_FROM_DATABASE=Communications ID_USB_DRIVER=cdc_acm ID_USB_INTERFACES=:020201:0a: ID_USB_INTERFACE_NUM=00 ID_VENDOR=Particle ID_VENDOR_ENC=Particle ID_VENDOR_FROM_DATABASE=Intel Corporation ID_VENDOR_ID=0x8086 MAJOR=166 MINOR=0 SUBSYSTEM=tty TAGS=:systemd: USEC_INITIALIZED=4586285779 Running udevadm info with the base device path gives expected IDs $ udevadm info --query=property -p /devices/pci:00/:00:14.0/usb1/1-1 BUSNUM=001 DEVNAME=/dev/bus/usb/001/008 DEVNUM=008 DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=Electron ID_MODEL_ENC=Electron ID_MODEL_ID=c00a ID_REVISION=0200 ID_SERIAL=Particle_Electron_050C ID_SERIAL_SHORT=050C ID_USB_INTERFACES=:020201:0a: ID_VENDOR=Particle ID_VENDOR_ENC=Particle ID_VENDOR_ID=2b04 MAJOR=189 MINOR=7 PRODUCT=2b04/c00a/200 SUBSYSTEM=usb TYPE=2/0/0 USEC_INITIALIZED=4585731209 Running lsusb gives the expected IDs. $ lsusb -v Bus 001 Device 008: ID 2b04:c00a Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x2b04 idProduct 0xc00a bcdDevice2.00 iManufacturer 1 Particle iProduct2 Electron iSerial 3 050C bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 67 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 1 AT-commands (v.25ter) iInterface 0 CDC Header: bcdCDC 1.10 CDC Call Management: bmCapabilities 0x00 bDataInterface 1 CDC ACM: bmCapabilities 0x02 line coding and serial state CDC Union: bMasterInterface0 bSlaveInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 255 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2
[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field
Tooo tired of this bug. Sometimes i need to fill some forms in Russian but Evince still doesn't provide this feature working properly. Do something please! -- 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: Confirmed 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 1450224] Re: Ubuntu 15.04: Boot with systemd stops asking for cryptoswap password
*** This bug is a duplicate of bug 1447282 *** https://bugs.launchpad.net/bugs/1447282 I have mbr disk, no EFI, and text boot. -- 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/1450224 Title: Ubuntu 15.04: Boot with systemd stops asking for cryptoswap password Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 15.04: - booting with systemd stops asking for cryptoswap password - booting stops; system don't boot - boot process with upstart works How can I fix the boot process? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450224/+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 1450224] Re: Ubuntu 15.04: Boot with systemd stops asking for cryptoswap password
*** This bug is a duplicate of bug 1447282 *** https://bugs.launchpad.net/bugs/1447282 After some time recovery shell is appeared. Here you can type `exit` or ctrl-D and password prompt appears! type password and boot process continues. Seems password entry program (plymouth) can't communicate with tty or whatever and exited by timeout on normal systemd boot. There are some plymouth timeout in `journalctl -xb` -- 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/1450224 Title: Ubuntu 15.04: Boot with systemd stops asking for cryptoswap password Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 15.04: - booting with systemd stops asking for cryptoswap password - booting stops; system don't boot - boot process with upstart works How can I fix the boot process? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450224/+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 1352975] Re: GUI symbol for Wi-fi in 14.10 shows not connected even when connected
The same for me - question mark instead of connection strength. Ubuntu 14.10, GNOME Shell 3.12.2, asus ux303ln. iwlist scan shows the strength. -- 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/1352975 Title: GUI symbol for Wi-fi in 14.10 shows not connected even when connected Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in wifi-radar package in Ubuntu: Invalid Bug description: Using Ubuntu 14.10 alpha 2 with all updates. Clean install. Network manager 0.9.8.8-0ubuntu23 Wifi-card: Intel Wireless 7260 (Rev 73) The Wi-fi symbol in the top right corner does not indicate that it is connected to Wi-fi even when it is connected. (It shows a question mark instead) Expected behavior is that it would show signal strength, or at the very least make it grey and remove the question mark. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 5 17:42:57 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-08-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140730) IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.110 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 18b6987c1-3f15-4b41-be88-ea9f5ae9eff6 802-3-ethernet1407252000 ti. 05. aug. 2014 kl. 17.20 +0200 yes no /org/freedesktop/NetworkManager/Settings/1 Diskokatt 5Ghz6a2433b7-9e20-4c4a-9c9d-455fee3505ef 802-11-wireless 1407253201 ti. 05. aug. 2014 kl. 17.40 +0200 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1352975/+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 1381530] [NEW] the system crashes and restarts.
Public bug reported: the system crashes and restarts. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 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 15 20:29:41 2014 DistUpgraded: 2014-05-05 22:15:46,699 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3530] InstallationDate: Installed on 2014-02-01 (255 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=b0cad534-93c5-43ff-afd9-ad7cb8e505f4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-05 (162 days ago) dmi.bios.date: 08/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Oct 15 20:04:24 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputGenius NetScroll + Traveler MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/1381530 Title: the system crashes and restarts. Status in “xorg” package in Ubuntu: New Bug description: the system crashes and restarts. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 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 15 20:29:41 2014 DistUpgraded: 2014-05-05 22:15:46,699 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3530] InstallationDate: Installed on 2014-02-01 (255 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine:
