[Touch-packages] [Bug 1669156] Re: Fails writing with Caps Lock
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1669156 Title: Fails writing with Caps Lock Status in lightdm package in Ubuntu: Expired Bug description: On Ubuntu 16.04: When clicking on the following 3 keyboard keys simultaneously: Left-CTRL + Left-ALT + F1 Then you get to a textual terminal (CLI) where you can type commands. But there is a problem when typing English letters with Caps Lock turned on: Instead of English capital letters - you see squares, so actually you can't login to your user that way if the username/password has Capital letters. The only method which allows you to write capital English letters is to simultaneously click Left-Shift + 'a letter'. That is the only method that works well. Note that the Caps Lock key works well with the graphical terminal (pseudo / pts) that appears on Ubuntu when hitting simultaneously: Left-CTRL + Left-ALT + T --- I assumed the bug report is relevant to "shadow" package because that the "/bin/login" binary comes from that package. Package version of 'shadow' is: 1:4.2-3.1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1669156/+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 1880614] Re: Network Manager and the Menu Bar display a question mark, as though it wasn't able to connect to the internet, but Ubuntu can access the internet just fine; this was
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1880614 Title: Network Manager and the Menu Bar display a question mark, as though it wasn't able to connect to the internet, but Ubuntu can access the internet just fine; this was a false flag Status in network-manager package in Ubuntu: Expired Bug description: A false flag of reporting a network without wifi access. This happens when leaving the computer idle for 20 minutes or more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 19:01:36 2020 InstallationDate: Installed on 2020-05-07 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880614/+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 1881970] Re: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1881970 Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: Problem of son. Sortie Fictive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 23:10:09 2020 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Audio interne - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: auguen 1324 F pulseaudio /dev/snd/controlC0: auguen 1324 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: KTWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd12/18/2009:svnTOSHIBA:pnSatelliteProL550:pvrPSLW9E-01600GFR:rvnTOSHIBA:rnKTWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite Pro L550 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PSLW9E-01600GFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881970/+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 1890001] Re: Random stuttering while in game
This sounds similar to bug 1883456... Please: 1. Try opening the 'Extensions' app and disable 'Ubuntu AppIndicators'. Does that fix it? 2. Run 'top' and tell us if any process is using high CPU. 3. Run the following commands after you have experienced the issue: journalctl -b0 > journal.txt gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890001 Title: Random stuttering while in game Status in gnome-shell package in Ubuntu: Incomplete Bug description: Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday but only experiencing this today. Random stuttering while playing minecraft, no clue what's causing it but I checked system monitor and it shows random spikes of a cpu thread to 100% and some spikes staying at 100% for a prolonged period. It may be related to me updating my video driver that is not recommended so I will see if switching down will resolve the issue. I never had this issue on driver 440. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.12-050712-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.57 Sun Jul 5 14:42:25 UTC 2020 GCC version: gcc version 10.2.0 (GCC) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 13:57:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 Rev. A] [1462:3726] InstallationDate: Installed on 2020-07-31 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS MASTER-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS MASTER dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/gnome-shell/+bug/1890001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1890084] Re: show app not work
It sounds like you're referring to a dock button. So that we can find out more about the system please run: gsettings list-recursively org.gnome.shell > settings.txt and then attach the resulting text file. Please also attach a screenshot of the issue/button/menu if you can. Just press PrtScn and look in the Pictures folder. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890084 Title: show app not work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 menu "show app" not work works after pressing the window key on the keyboard ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:34:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed DpkgLog: GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1da2:e387] InstallationDate: Installed on 2018-08-26 (707 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d2cdd1b7-f30e-4dbf-80af-703216601328 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102+git2007100630.669e10~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2007261930.18fe13~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2007261930.18fe13~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/gnome-shell/+bug/1890084/+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 1890050] Re: Mouse malfunction when launching steam
The attached XorgLog.txt shows the mouse is repeatedly: [ 28256.417] (II) event4 - USB OPTICAL MOUSE: device removed So this might be a hardware problem or a kernel bug. Try plugging it into a different port, or try a different mouse. ** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890050 Title: Mouse malfunction when launching steam Status in linux package in Ubuntu: Incomplete Bug description: When launching Steam mouse automatically stops working. Only way to fix it is closing Steam and plugging the mouse again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 19:30:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d6] InstallationDate: Installed on 2020-01-29 (185 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1555f7ff-6084-4156-b1cd-6e9c57ec0e76 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD PLUS (MS-7A15) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd10/28/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VDPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A15 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890050/+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 1889991] Re: Highlight for the task switcher is too subtle
This was declared fixed in bug 1871416 but clearly that's not high enough contrast for everyone. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Package changed: gnome-shell (Ubuntu) => yaru-theme (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/1889991 Title: Highlight for the task switcher is too subtle Status in yaru-theme package in Ubuntu: New Bug description: The task switcher has a highlight to enable the user to see which task has focus. In Ubuntu 20.04 (but not earlier versions, I think) this highlight is so subtle that one can easily miss it. I'm all for subtlety, but this is *too* subtle. I find myself repeatedly choosing the wrong task. My vision is not perfect but decent. Users with poor vision may find this problem particularly difficult. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 12:50:46 2020 DistUpgraded: 2020-04-20 13:45:34,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen [17aa:224f] InstallationDate: Installed on 2017-12-08 (966 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20HRCTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a890597b-ae6f-4f55-a929-cdd87de29f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (102 days ago) dmi.bios.date: 06/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET63W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET63W(1.48):bd06/03/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/yaru-theme/+bug/1889991/+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 1890084] [NEW] show app not work
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 menu "show app" not work works after pressing the window key on the keyboard ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:34:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed DpkgLog: GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1da2:e387] InstallationDate: Installed on 2018-08-26 (707 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d2cdd1b7-f30e-4dbf-80af-703216601328 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102+git2007100630.669e10~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2007261930.18fe13~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2007261930.18fe13~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 performance third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890084 Title: show app not work Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 menu "show app" not work works after pressing the window key on the keyboard ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:34:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed DpkgLog: GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1da2:e387] InstallationDate: Installed on 2018-08-26 (707 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d2cdd1b7-f30e-4dbf-80af-703216601328 ro quiet splash radeon.si_support=0 radeon.cik_support=0
[Touch-packages] [Bug 1889941] Re: AMD Navi10 GPU powerplay issues when using two DisplayPort connectors
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #929 https://gitlab.freedesktop.org/drm/amd/-/issues/929 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/929 Importance: Unknown Status: Unknown ** Summary changed: - AMD Navi10 GPU powerplay issues when using two DisplayPort connectors + [amdgpu] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: amdgpu ** Tags added: multimonitor -- 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/1889941 Title: [amdgpu] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors Status in Linux: Unknown Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Connecting two displayport monitors to a 5700XT causes flickering on one of the screens, issue appears to be occurring upstream and is being tracked here: https://gitlab.freedesktop.org/drm/amd/-/issues/929 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 21:45:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1682:5701] InstallationDate: Installed on 2020-06-28 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=f17edc40-7eaf-4768-977d-f0e067db9b04 ro amdgpu.noretry=0 processor.max_cstate=5 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/linux/+bug/1889941/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
** Changed in: pulseaudio (Ubuntu) Assignee: Marcelo Pires (marcelo-pires-silva) => (unassigned) -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Touch-packages] [Bug 1886585] Re: Restarting display / screen
Can you attach a video of the problem? If not, then can you please describe the problem in more detail? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886585 Title: Restarting display / screen Status in Ubuntu: Incomplete Bug description: The computer stops and restarts the screen and after about 2 secs the display works normally in maybe 30 secs . The proces repeats for several minutes (maybe 24 mins) and then suddenly everything works normally. If I go into some serous work like this report I am able to do that without disturbance. If I go back to no working apps the operation continues with on/off working. My system is the latest 20.04 software upgrade from the Beta-version. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.20 ProcVersionSignature: Ubuntu 5.4.0-41.45-generic 5.4.44 Uname: Linux 5.4.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 6 22:52:53 2020 InstallationDate: Installed on 2019-10-20 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. VarLogDistupgradeAptlog: Log time: 2020-06-25 21:27:41.194955 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886585/+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 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30
If you are experiencing any problems in Ubuntu 20.04 or 18.04 then please run: ubuntu-bug mutter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Won't Fix Status in ukwm package in Ubuntu: Fix Released Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 We could easily add a dummy key with the old name but I'm thinking the way forward is just to package the newer mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+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 1759014] Re: Netplan has no way to control DHCP client
@ddstreet I've been looking into a different issue, which is due to the Netplan
renderer.
The renderer defaults to networkd on server/cloud and NetworkManager on
Desktop. Some apps expect NetworkManager, and break on systems configured with
networkd (e.g. UI network config, apt-daily, etc).
It's possible that the issue above needs to be tested against both
renderers as it may behave differently in each case?
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in Default settings and artwork for Baltix OS:
New
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Fix Released
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1759014/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
I'm seeing another fun intermittent issue after waking from sleep on my system. sometimes after resume, the audio is really static-y, until i turn the volume down one notch and back up again. next time it happens I'll attach the logs again, just to see if there's anything illuminating there. it only happens maybe ~5% of the time, so it might be a while until I can reproduce. -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1870088] Re: xz-utils ftbfs in focal
This bug was fixed in the package xz-utils - 5.2.4-1ubuntu1 --- xz-utils (5.2.4-1ubuntu1) focal; urgency=medium * Use the generic % rule in debian/rules, otherwise it FTBFS with debhelper 12.5. Closes: #945961. LP: #1870088. -- Tiago Stürmer Daitx Mon, 20 Apr 2020 21:43:24 + ** Changed in: xz-utils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Fix Committed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1890006] Re: Hash mismatch on "apt update"
VT-x status in BIOS is a red herring. Turns out modern Virtualbox won't even start VM's without VT-x. A true cause turned out to be "Windows Sandbox" feature (although I imagine for some other users the problem might be triggered by "Windows Subsystem for Linux" or anti-virus software). Here is how to reproduce it in Windows 10: 1. Enable "Windows Sandbox" (Control panel -> Programs and Features -> Turn Windows features on or off) 2. After restart run Ubuntu live ISO in virtualbox and notice that a) VM slows to a crawl, some apps (firefox) start crashing randomly, etc b) Virtualbox shows "green turtle" icon (third from the right on the lower panel) which lists Execution engine as "native API" instead of "VT-x" c) Running "apt update" produces error mentioning "hash mismatch" d) Running workaround (mkdir -p /etc/gcrypt; echo intel-ssse3 > /etc/gcrypt/hwf.deny) fixes the apt error 3. Disable "Windows Sandbox" feature 4. After Windows restart run Ubuntu in Virtualbox and be surprised by green turtle still being there, all mentioned problems still present 5. Restart Windows second time, run Ubuntu in Virtualbox again, this time there is a blue chip instead of green turtle and apt works without workarounds Clearly it seems that gcrypt isnt at fault here and the true culprits are Windows Sandbox (possibly some other mechanism that Windows Sandbox enables) and/or Virtualbox. However the result is that new users are getting wrong impression about GNU/Linux and Ubuntu in particular (it appears slow and lags during "live" phase, fails to update after install). So I'd say Ubuntu should detect that it's being run in this broken virtualization mode, show the informative explanation to user (that their current experience isn't representative && how they can fix that) or at least enable the workaround for gcrypt (although if SSSE3 is buggy in this mode, I imagine more things are stealthily broken). Surprisingly Ubuntu still finishes installation, even with default "update from internet" option enabled. After installation, "apt update" still produces the same "hash mismatch" errors though. Enabling workaround and rerunning "apt update" predictably finds many more (292 right now) packages that are to be upgraded. This fail-open behavior (installer and updater ignoring the errors) will no doubt lead to subtle bug down the road for the users as well (I'd argue that it's a security issue as well - users not being informed about security patches they're missing). -- 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/1890006 Title: Hash mismatch on "apt update" Status in apt package in Ubuntu: New Bug description: This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a single PC (as far as I know). All testing was done in Virtualbox and moving VM's to another PC fixed issue (without changing anything inside the VM). On running "apt update", there is an error "Hash Sum mismatch" which shows that SHA1 and SHA256 hashes differ from expected (while MD5 and file size is correct). E.g.: Hash Sum mismatch Hashes of expected file: - Filesize:314536 [weak] - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] Hashes of received file: - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] - Filesize:314536 [weak] I ran packet capture and extracted archives which are getting verified. All of their hashes are correct (exactly as expected). It seems that calculating SHA1 and SHA256 the way APT does it produces wrong result, while running command line tools sha1sum and sha256sum (on the same PC inside the same VM) produces correct result. I wrote the minimal reproducible example (hashtest.cc) that produces output such as this: Calculating hashes same way apt does. - MD5Sum:c89b13b76197d0d554400e00e46c0740 - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 - Checksum-FileSize:892549 Calculating hashes through command line tools. - md5sum: c89b13b76197d0d554400e00e46c0740 - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - sha512sum:
[Touch-packages] [Bug 1890006] Re: Hash mismatch on "apt update"
Here is apport stuff, and there are more news.
I confirmed that the problem was in the gcrypt. More precisely,
disabling SSSE3 fixes this issue (echo intel-ssse3 >
/etc/gcrypt/hwf.deny).
The Virtualbox (running on Windows 10) was using software virtualization
("execution engine: native API") instead of VT-x - this might be the
root cause (i.e. bug is in Virtualbox), but I'm helping a friend and
don't have direct access to that PC, so can't test what's blocking VT-x.
Hyper-V and WSL are disabled in Windows features, the person hasn't
checked whether VT-x is enabled in BIOS yet.
--
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/1890006
Title:
Hash mismatch on "apt update"
Status in apt package in Ubuntu:
New
Bug description:
This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
on a single PC (as far as I know). All testing was done in Virtualbox
and moving VM's to another PC fixed issue (without changing anything
inside the VM).
On running "apt update", there is an error "Hash Sum mismatch" which
shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
file size is correct). E.g.:
Hash Sum mismatch
Hashes of expected file:
- Filesize:314536 [weak]
- SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
- SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
- MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
- SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
- SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
- MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
- Filesize:314536 [weak]
I ran packet capture and extracted archives which are getting
verified. All of their hashes are correct (exactly as expected).
It seems that calculating SHA1 and SHA256 the way APT does it produces
wrong result, while running command line tools sha1sum and sha256sum
(on the same PC inside the same VM) produces correct result.
I wrote the minimal reproducible example (hashtest.cc) that produces
output such as this:
Calculating hashes same way apt does.
- MD5Sum:c89b13b76197d0d554400e00e46c0740
- SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
- SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
-
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
- Checksum-FileSize:892549
Calculating hashes through command line tools.
- md5sum: c89b13b76197d0d554400e00e46c0740
- sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
- sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
- sha512sum:
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
It's in the attachment alongside with an example file that causes this
hash mismatch. There's also debug.log which contains various versions,
etc (although as I said, it has been verified on latest Ubuntu Live
ISO).
I have a suspicion that the bug is in the gcrypt library, not apt itself, but
I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1
(in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.445
DistroRelease: Ubuntu 20.04
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: apt 2.0.2
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Tags: focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1890006/+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 1890050] [NEW] Mouse malfunction when launching steam
Public bug reported: When launching Steam mouse automatically stops working. Only way to fix it is closing Steam and plugging the mouse again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 19:30:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d6] InstallationDate: Installed on 2020-01-29 (185 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1555f7ff-6084-4156-b1cd-6e9c57ec0e76 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD PLUS (MS-7A15) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd10/28/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VDPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A15 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1890050 Title: Mouse malfunction when launching steam Status in xorg package in Ubuntu: New Bug description: When launching Steam mouse automatically stops working. Only way to fix it is closing Steam and plugging the mouse again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 19:30:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d6] InstallationDate: Installed on 2020-01-29 (185 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1555f7ff-6084-4156-b1cd-6e9c57ec0e76 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably
[Touch-packages] [Bug 1890006] Re: Hash mismatch on "apt update"
apport information ** Tags added: apport-collected focal ** Description changed: This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a single PC (as far as I know). All testing was done in Virtualbox and moving VM's to another PC fixed issue (without changing anything inside the VM). On running "apt update", there is an error "Hash Sum mismatch" which shows that SHA1 and SHA256 hashes differ from expected (while MD5 and file size is correct). E.g.: Hash Sum mismatch Hashes of expected file: - Filesize:314536 [weak] - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] Hashes of received file: - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] - Filesize:314536 [weak] I ran packet capture and extracted archives which are getting verified. All of their hashes are correct (exactly as expected). It seems that calculating SHA1 and SHA256 the way APT does it produces wrong result, while running command line tools sha1sum and sha256sum (on the same PC inside the same VM) produces correct result. I wrote the minimal reproducible example (hashtest.cc) that produces output such as this: Calculating hashes same way apt does. - MD5Sum:c89b13b76197d0d554400e00e46c0740 - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 - Checksum-FileSize:892549 Calculating hashes through command line tools. - md5sum: c89b13b76197d0d554400e00e46c0740 - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - sha512sum: 7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 It's in the attachment alongside with an example file that causes this hash mismatch. There's also debug.log which contains various versions, etc (although as I said, it has been verified on latest Ubuntu Live ISO). - I have a suspicion that the bug is in the gcrypt library, not apt - itself, but I haven't yet verified it. The libgcrypt20 version in Ubuntu - is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which isn't - affected) uses 1.8.4-5. + I have a suspicion that the bug is in the gcrypt library, not apt itself, but I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckMismatches: ./casper/filesystem.squashfs + CasperMD5CheckResult: fail + CasperVersion: 1.445 + DistroRelease: Ubuntu 20.04 + LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: apt 2.0.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 + Tags: focal + Uname: Linux 5.4.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1890006/+attachment/5397968/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1890006 Title: Hash mismatch on "apt update" Status in apt package in Ubuntu: New Bug description: This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a single PC (as far as I know). All testing was done in Virtualbox and moving VM's to another PC fixed issue (without changing anything inside the VM). On running "apt update", there is an error "Hash Sum mismatch" which shows that SHA1 and SHA256 hashes differ from expected (while MD5 and file size is correct). E.g.: Hash Sum mismatch Hashes of expected file: - Filesize:314536 [weak] - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak] -
[Touch-packages] [Bug 1890006] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1890006/+attachment/5397969/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1890006 Title: Hash mismatch on "apt update" Status in apt package in Ubuntu: New Bug description: This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a single PC (as far as I know). All testing was done in Virtualbox and moving VM's to another PC fixed issue (without changing anything inside the VM). On running "apt update", there is an error "Hash Sum mismatch" which shows that SHA1 and SHA256 hashes differ from expected (while MD5 and file size is correct). E.g.: Hash Sum mismatch Hashes of expected file: - Filesize:314536 [weak] - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] Hashes of received file: - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] - Filesize:314536 [weak] I ran packet capture and extracted archives which are getting verified. All of their hashes are correct (exactly as expected). It seems that calculating SHA1 and SHA256 the way APT does it produces wrong result, while running command line tools sha1sum and sha256sum (on the same PC inside the same VM) produces correct result. I wrote the minimal reproducible example (hashtest.cc) that produces output such as this: Calculating hashes same way apt does. - MD5Sum:c89b13b76197d0d554400e00e46c0740 - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 - Checksum-FileSize:892549 Calculating hashes through command line tools. - md5sum: c89b13b76197d0d554400e00e46c0740 - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - sha512sum: 7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 It's in the attachment alongside with an example file that causes this hash mismatch. There's also debug.log which contains various versions, etc (although as I said, it has been verified on latest Ubuntu Live ISO). I have a suspicion that the bug is in the gcrypt library, not apt itself, but I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.445 DistroRelease: Ubuntu 20.04 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: apt 2.0.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1890006/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I booted a live image of 20.10 and their my bluetooth does work. I also downloaded a version of 20.04.1 which also worked fine. -- 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 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/pulseaudio/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I booted up my laptop today and hsp/hfp mode failed again. So my idea about the firmware seems to be wrong. So i was wrong about that. -- 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 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/pulseaudio/+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 1890047] Re: Sessions crash, all X11 remote users disconnected
Here status for journalctl when it crash ** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1890047/+attachment/5397965/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1890047 Title: Sessions crash, all X11 remote users disconnected Status in glib-networking package in Ubuntu: New Bug description: Hello, I have a Ubuntu 16.04.6 LTS (Xenial Xerus) used by many X11 remote user. When upgrading to glib-networking, glib-networking-common and lib- networking-services to 2.48.2-1~ubuntu16.04.2; all sessions crash randomly at the same time many times a day. When it happens, all users are disconnected and it looks like lightdm is restarted. Downgrading to 2.48.2-1~ubuntu16.04.1 resolve the problem. X11 terminals were not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1890047/+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 1890047] [NEW] Sessions crash, all X11 remote users disconnected
Public bug reported: Hello, I have a Ubuntu 16.04.6 LTS (Xenial Xerus) used by many X11 remote user. When upgrading to glib-networking, glib-networking-common and lib- networking-services to 2.48.2-1~ubuntu16.04.2; all sessions crash randomly at the same time many times a day. When it happens, all users are disconnected and it looks like lightdm is restarted. Downgrading to 2.48.2-1~ubuntu16.04.1 resolve the problem. X11 terminals were not upgraded. ** Affects: glib-networking (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport bug report" https://bugs.launchpad.net/bugs/1890047/+attachment/5397964/+files/apport.glib-networking.wdpy_fx6.apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1890047 Title: Sessions crash, all X11 remote users disconnected Status in glib-networking package in Ubuntu: New Bug description: Hello, I have a Ubuntu 16.04.6 LTS (Xenial Xerus) used by many X11 remote user. When upgrading to glib-networking, glib-networking-common and lib- networking-services to 2.48.2-1~ubuntu16.04.2; all sessions crash randomly at the same time many times a day. When it happens, all users are disconnected and it looks like lightdm is restarted. Downgrading to 2.48.2-1~ubuntu16.04.1 resolve the problem. X11 terminals were not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1890047/+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 1890006] Re: Hash mismatch on "apt update"
Don't see any reason for any apport collecting here. This needs a clean reproducer or someone with the issue to do the work to analyse what's wrong. Looking at the bug report, the output from the reproducer matches that of the commandline tools? -- 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/1890006 Title: Hash mismatch on "apt update" Status in apt package in Ubuntu: New Bug description: This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs on a single PC (as far as I know). All testing was done in Virtualbox and moving VM's to another PC fixed issue (without changing anything inside the VM). On running "apt update", there is an error "Hash Sum mismatch" which shows that SHA1 and SHA256 hashes differ from expected (while MD5 and file size is correct). E.g.: Hash Sum mismatch Hashes of expected file: - Filesize:314536 [weak] - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] Hashes of received file: - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak] - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak] - Filesize:314536 [weak] I ran packet capture and extracted archives which are getting verified. All of their hashes are correct (exactly as expected). It seems that calculating SHA1 and SHA256 the way APT does it produces wrong result, while running command line tools sha1sum and sha256sum (on the same PC inside the same VM) produces correct result. I wrote the minimal reproducible example (hashtest.cc) that produces output such as this: Calculating hashes same way apt does. - MD5Sum:c89b13b76197d0d554400e00e46c0740 - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 - Checksum-FileSize:892549 Calculating hashes through command line tools. - md5sum: c89b13b76197d0d554400e00e46c0740 - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6 - sha512sum: 7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036 It's in the attachment alongside with an example file that causes this hash mismatch. There's also debug.log which contains various versions, etc (although as I said, it has been verified on latest Ubuntu Live ISO). I have a suspicion that the bug is in the gcrypt library, not apt itself, but I haven't yet verified it. The libgcrypt20 version in Ubuntu is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which isn't affected) uses 1.8.4-5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1890006/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Thansk, the hardware ax200 will load ibt-20-1-3.ddc and ibt-20-1-3.sfi, do you mean the ibt-20-1-3 is version 48 or the ibt-20-1-3 has version 46 and 48? -- 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 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/pulseaudio/+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 1890042] [NEW] KDE: Key shortcuts no longer working
Public bug reported: In the KDE menu editor, you can define keyboard shortcuts for each program that, when pressed, will launch that respective program. However, since 20.04, that mechanism no longer works -- pressing any shortcut key (e.g., Meta+E) no longer starts the assigned program (e.g., Emacs GUI). Of course I don't know if the issue is with menu editor, or kwin, or something else in Plasma. Further information: Description:Ubuntu 20.04.1 LTS Release:20.04 plasma-workspace: Installed: 4:5.18.5-0ubuntu0.1 Candidate: 4:5.18.5-0ubuntu0.1 Version table: *** 4:5.18.5-0ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:5.18.4.1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1890042 Title: KDE: Key shortcuts no longer working Status in apport package in Ubuntu: New Bug description: In the KDE menu editor, you can define keyboard shortcuts for each program that, when pressed, will launch that respective program. However, since 20.04, that mechanism no longer works -- pressing any shortcut key (e.g., Meta+E) no longer starts the assigned program (e.g., Emacs GUI). Of course I don't know if the issue is with menu editor, or kwin, or something else in Plasma. Further information: Description:Ubuntu 20.04.1 LTS Release:20.04 plasma-workspace: Installed: 4:5.18.5-0ubuntu0.1 Candidate: 4:5.18.5-0ubuntu0.1 Version table: *** 4:5.18.5-0ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:5.18.4.1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890042/+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 1890041] [NEW] Apport does not work without Chrome
Public bug reported: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: New Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+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 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox
** Tags removed: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox Status in Ubuntu MATE: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854588/+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 1815553] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Still happening in 20.04. -- 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/1815553 Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 10 Status in openssh package in Ubuntu: Expired Bug description: It creates problem on installing. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: avahi-autoipd:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Feb 12 09:09:51 2019 DuplicateSignature: package:openssh-server:1:7.6p1-4ubuntu0.1 Setting up gns3 (0.8.7-2) ... dpkg: error processing package gns3 (--configure): installed gns3 package post-installation script subprocess returned error exit status 10 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-09-29 (135 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.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.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1815553/+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 1854383] Re: Extra window decorations are created on windows with client-side decorations.
** Tags removed: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1854383 Title: Extra window decorations are created on windows with client-side decorations. Status in Ubuntu MATE: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Steps to reproduce after a minimal/full install of Ubuntu MATE: 1. Start up a Gtk3 application with a header bar (tested with Gnome Software) or a browser (such as Firefox) without using a standard window title bar that saves the position and size of the window before it was closed. 2. Maximize the application window, then close it without changing the window size 3. Relaunch the application and resize/unmaximize it After this, dummy window decorations will be created around the window. This issue has been tested on a Dell XPS 9570 and using Gnome Boxes 3.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854383/+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 269441] Re: Trash always full
** Tags removed: eoan lucid maverick -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/269441 Title: Trash always full Status in Ubuntu MATE: New Status in glib2.0 package in Ubuntu: Confirmed Bug description: I've seen other users having problems with that the trash appears empty even though it isn't. I have the opposite problem: my trash icon on the desktop always appears full, even if empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+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 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
** Tags removed: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in Ubuntu MATE: New Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+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 1883477] Re: When closing the lid of laptop, WiFi disconnects and doesn't reconnect afterwards
Another thing I noticed recently: I've disabled standby when closing the Lid. If I trigger standby manually and then close the lid, the networking resumes as expected after waking the computer up. HTH, Markus -- 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/1883477 Title: When closing the lid of laptop, WiFi disconnects and doesn't reconnect afterwards Status in network-manager package in Ubuntu: New Bug description: I am getting this issue since about a year on my Lenovo Thinkpad x240 with Ubuntu Mate I have configured the computer to stay awake and empty the screen (system settings > power management) when I close the lid with the power plugged in. What I expect to happen: Wifi network stays connected and network related programs (like bit-torrent or http downloads) continue to run. What actually happens: Wifi always disconnects after closing the lid and doesn't come back upon opening it. I just see a "two arrows"-symbol on the top bar. When I try to reconnect manually, the wifi symbol is blinking, but the network manager eventually gives up. I have to disable wifi (or network as a whole) for a second and enable it again, to then automatically reconnect to my home wifi network. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Jun 15 06:09:25 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2019-12-06 (191 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.2.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.2.0/24 dev wlp3s0 proto kernel scope link src 192.168.2.105 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-05-07 (38 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1883477/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
version 48 is for AX201 AND version 46 is for ax200. -- 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 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/pulseaudio/+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 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
** Changed in: json-c (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Fix Released Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+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
