[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
This bug was fixed in the package network-manager - 1.22.10-1ubuntu3 --- network-manager (1.22.10-1ubuntu3) groovy; urgency=medium * No-change rebuild to bump Groovy version number. network-manager (1.22.10-1ubuntu2) focal; urgency=medium * d/t/killswitches-no-urfkill - Call udevadm settle before nmcli radio wifi To make sure that change is updated. (LP: #1733321) -- Dan Streetman Thu, 30 Apr 2020 07:47:49 -0400 ** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's c
[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Kai, What do you think on #21, it's a regression or not? -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
For what I observed (both focal and bionic), I'm not sure (and I think it's not) it's a regression, due the the bug it's already there before this patch. And I tried one hp dm, one hp sff, one hp laptop and one dell laptop, only can be reproduced in Dell laptop. For what I observed: [[[1:11.1-1ubuntu7.5]]] Before I plugged headset there is only one device shown on input device, which is 1. Internal Microphone - Built-in Audio After I plugged headset into the jack, dialog shown up, I choice "headset", then three input device shown up, which are: 1. Headset Microphone - Built-in Audio 2. Internal Microphone - Built-in Audio 3. Microphone - Built-in Audio [[[1:11.1-1ubuntu7.6]]] Before I plugged headset there are two devices shown on input device, which are 1. Headset Microphone - Built-in Audio 2. Internal Microphone - Built-in Audio After I plugged headset into the jack, dialog shown up, I choice "headset", then three input device shown up, which are: 1. Headset Microphone - Built-in Audio 2. Internal Microphone - Built-in Audio 3. Microphone - Built-in Audio [[[result]]] No matter which cases, once you choice (3. Microphone - Built-in Audio), then there is no headset output audio. Select others, the audio output came back. -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Quite some investigations you did there ironincoder, don't forget to post here if you manage to get the speakers going. ;) I was actually wondering where the correct place to post and get codec issues fixed is, because this probably isn't the place? Is there a bug tracker for Alsa? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnvir
[Touch-packages] [Bug 1876416] [NEW] Xorg freeze
Public bug reported: I have been using the operating system for the past week,and i have seen lot of problem with it.when i am turning on the computer sometimes its black screen and does not open.sometime when i open and browsing the system was suddenly hangs and does not turn off.even after i turn of the power the computer not shutting down .it would be grade if someone could help . " i was trying to fix using "nomodeset" but it does not work for me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 08:28:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2020-04-20 (11 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H 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.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 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 false-gpu-hang freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876416 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have been using the operating system for the past week,and i have seen lot of problem with it.when i am turning on the computer sometimes its black screen and does not open.sometime when i open and browsing the system was suddenly hangs and does not turn off.even after i turn of the power the computer not shutting down .it would be grade if someone could help . " i was trying to fix using "nomodeset" but it does not work for me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 08:28:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2020-04-20 (11 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh ins
[Touch-packages] [Bug 1876415] [NEW] Fonts in the GNOME shell not shown.
Public bug reported: GNOME does not show any text in the DE itself. Examples of text that is missing: The activities button on the top left, date and time, text of notifications, authentication dialogs, the telegram icon not displaying the number of unread messages, searches in the search bar. The text however is drawn in applications that are not an integral part of the shell itself, such as the settings application, terminals, Firefox, Rhythmbox, GNOME System montior. The bug appeared seemingly out of nowhere, can be worked around though pretty easily by chainging the fonts of the user interface in the GNOME tweak tool. The problem reappears, if the user interface fonts are changed back to the fonts which were not appearing on the screen originally. Changing the font size does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 04:28:41 2020 DistUpgraded: 2020-04-24 10:02:52,848 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-26-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-28-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] InstallationDate: Installed on 2019-11-07 (176 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=45a49275-be6c-418c-86a5-c57794b70427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (7 days ago) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Missing fonts in the calendar, clock and the notifications." https://bugs.launchpad.net/bugs/1876415/+attachment/5364816/+files/Bildschirmfoto%20von%202020-05-02%2004-49-19.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876415 Title: Fonts in the GNOME shell not shown. Status in xorg package in Ubuntu: New Bug description: GNOME does not show any text in the DE itself. Examples of text that is missing: The activities button on the top left, date and time, text of notifications, authentication dialogs, the telegram ic
[Touch-packages] [Bug 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled
This bug was fixed in the package ibus - 1.5.22-4ubuntu1 --- ibus (1.5.22-4ubuntu1) groovy; urgency=medium * Merge from Debian unstable, remaining changes: - d/p/ubuntu-forward-panel-properties.patch (for Unity) - d/control: Build-Depend on gnome-pkg-tools (for translations) - d/rules: Use dh_translations when built on Ubuntu * Dropped patches: - d/p/ubuntu-disable-trigger.patch (LP: #1870945) - d/p/ubuntu-unicode-keybinding.patch (discussed at https://github.com/ibus/ibus/issues/2163) - d/p/git-Use-WAYLAND_DISPLAY-on-Wayland-sessions.patch (equivalent patch now in Debian) * Dropped breaks for older libglib2.0-0 versions - No equivalent in Debian; not needed post 20.04 * Build-Depend on gnome-pkg-tools instead of dh_translations * d/rules: Use dh_translations in Ubuntu -- Gunnar Hjalmarsson Thu, 30 Apr 2020 09:43:00 +0200 ** Changed in: ibus (Ubuntu) Status: In Progress => Fix Released ** Bug watch added: github.com/ibus/ibus/issues #2163 https://github.com/ibus/ibus/issues/2163 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870945 Title: ubuntu-disable-trigger.patch is effectively not enabled Status in Unity: New Status in ibus package in Ubuntu: Fix Released Bug description: ubuntu-disable-trigger.patch has effectively not been enabled since XDG_CURRENT_DESKTOP was turned into a list of values instead of a single value. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1870945/+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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo
I can confirm this is not working on Bionic. vainfo output: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 error: failed to resolve wl_drm_interface(): /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+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 1752635] Re: [patch] Please add command-not-found hints
has this landed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1752635 Title: [patch] Please add command-not-found hints Status in python2.7 package in Ubuntu: New Bug description: The new command-not-found extractor uses hints from the binary packages. The attached fix adds renaming for python2.7-minimal -> python2.7. We probably want the same for python3.6,3.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1752635/+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 809302] Re: pydoc -k launches kwallet
For me on bionic, that command tries to launch gourmet, a totally unrelated application. $ pydoc -k "hello" boto.pyami.helloworld usage: gourmet [-h] [--version] [--database-url DB_URL] [--plugin-directory HTML_PLUGIN_DIR] [--use-threads] [--disable-threads] [--gourmet-directory GOURMETDIR] [--debug-threading-interval THREAD_DEBUG_INTERVAL] [--debug-threading] [--debug-file DEBUG_FILE] [--showtimes] [--disable-psyco] [-q | -v] gourmet: error: unrecognized arguments: -k hello ** Changed in: python2.7 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/809302 Title: pydoc -k launches kwallet Status in python2.7 package in Ubuntu: Confirmed Bug description: steps to reproduce 1) run pydoc -k "hello" It seems to begin to operate correctly, but always includes the following details, and opens kwallet (?) [... Package names - descriptions...] Usage: pydoc2.7 [options] A simple dialog based tool for basic configuration of Speech Dispatcher and problem diagnostics. pydoc2.7: error: no such option: -k """ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/809302/+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 1853525] Re: no python 2.7.17 in LTS version
The requested version is in the repos and the changelog suggests that at the time of filing the reporter's installation was not uptodate. http://changelogs.ubuntu.com/changelogs/pool/main/p/python2.7/python2.7_2.7.17-1~18.04ubuntu1/changelog ** Changed in: python2.7 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1853525 Title: no python 2.7.17 in LTS version Status in python2.7 package in Ubuntu: Invalid Bug description: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+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 1505670] Re: "uncaptured python exception"
filing against python2.7 as well based on comment #4 ** Also affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1505670 Title: "uncaptured python exception" Status in python2.7 package in Ubuntu: New Status in squid-deb-proxy package in Ubuntu: Confirmed Bug description: I get the following error when running the discovery script on the command line. $ /usr/share/squid-deb-proxy-client/apt-avahi-discover error: uncaptured python exception, closing channel ('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection refused [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|446] [/usr/lib/python2.7/asyncore.py|handle_connect_event|454]) error: uncaptured python exception, closing channel ('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection refused [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|446] [/usr/lib/python2.7/asyncore.py|handle_connect_event|454]) error: uncaptured python exception, closing channel ('172.24.74.129', 3142): 2147483647 (:[Errno 111] Connection refused [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|446] [/usr/lib/python2.7/asyncore.py|handle_connect_event|454]) http://172.24.74.145:3142/ The last line still returns the proper proxy URI so as far as I can tell things are still working. The IP 10.1.2.3 is for an n2n VPN. This is on trusty with version 0.8.6ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+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 1804444] Re: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 127
from DpkgTerminalLog.txt: Setting up python2.7 (2.7.15~rc1-1ubuntu0.1) ... /var/lib/dpkg/info/python2.7.postinst: 9: /var/lib/dpkg/info/python2.7.postinst: /usr/bin/python2.7: not found [1mdpkg:[0m error processing package python2.7 (--configure): installed python2.7 package post-installation script subprocess returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/180 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 127 Status in python2.7 package in Ubuntu: New Bug description: I uninstalled python2.7 using apt purge python-minimal and later installed it again ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python2.7 2.7.15~rc1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Nov 21 09:19:33 2018 ErrorMessage: installed python2.7 package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2017-05-04 (566 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: python2.7 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-10-02 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/180/+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 1876382] Re: Ubuntu 20.04 Fractional scaling
** Package changed: ubuntu => xorg (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/1876382 Title: Ubuntu 20.04 Fractional scaling Status in xorg package in Ubuntu: New Bug description: I have 2 screens 1 x 1440 x 2560 (2k) 1 x 3840 x 2160 (4k) I just upgraded to ubuntu 20.04 (From 19.10). I have tried to use the fractional scaling option and it seem its not working. When setting the fractional scaling on the 4k monitor (to 125% or 150%) it glitches out (Goes black) and when it comes back it has set the scaling to 200% and changed the screen positions to be on top of one another, Seems there is no way for me to set the correct scaling. Just for information purposes I am currently using the nvidia-435 driver (I have also tried with the nvidia-440-driver) to no avail ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 22:00:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6183] InstallationDate: Installed on 2020-01-15 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:0892 Logitech, Inc. OrbiCam Bus 001 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370P D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=bd37a70e-316f-4716-a253-481f8f785d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: Z370P D3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370PD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370PD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370P D3 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876382/+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 1876383] Re: issues with full screen videos
** Package changed: ubuntu => xorg (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/1876383 Title: issues with full screen videos Status in xorg package in Ubuntu: New Bug description: When watching MP4 clips using the default app (videos) I have a display issue. When clicking on the full screen button here is what happens: 1- screen goes blank for a few seconds 2- a new videos window opens up with displaying the move but it it is not maximized or in full screen 3- The original maximized window stays in the background with a still picture ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 17:21:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068] InstallationDate: Installed on 2020-04-24 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0070.2018.1019.1503 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0070.2018.1019.1503:bd10/19/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876383/+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 1876382] [NEW] Ubuntu 20.04 Fractional scaling
You have been subscribed to a public bug: I have 2 screens 1 x 1440 x 2560 (2k) 1 x 3840 x 2160 (4k) I just upgraded to ubuntu 20.04 (From 19.10). I have tried to use the fractional scaling option and it seem its not working. When setting the fractional scaling on the 4k monitor (to 125% or 150%) it glitches out (Goes black) and when it comes back it has set the scaling to 200% and changed the screen positions to be on top of one another, Seems there is no way for me to set the correct scaling. Just for information purposes I am currently using the nvidia-435 driver (I have also tried with the nvidia-440-driver) to no avail ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 22:00:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6183] InstallationDate: Installed on 2020-01-15 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:0892 Logitech, Inc. OrbiCam Bus 001 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370P D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=bd37a70e-316f-4716-a253-481f8f785d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: Z370P D3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370PD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370PD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370P D3 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Ubuntu 20.04 Fractional scaling https://bugs.launchpad.net/bugs/1876382 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1876383] [NEW] issues with full screen videos
You have been subscribed to a public bug: When watching MP4 clips using the default app (videos) I have a display issue. When clicking on the full screen button here is what happens: 1- screen goes blank for a few seconds 2- a new videos window opens up with displaying the move but it it is not maximized or in full screen 3- The original maximized window stays in the background with a still picture ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 17:21:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068] InstallationDate: Installed on 2020-04-24 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0070.2018.1019.1503 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0070.2018.1019.1503:bd10/19/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- issues with full screen videos https://bugs.launchpad.net/bugs/1876383 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1876305] Re: Open Gl error
** Information type changed from Private Security to Public -- 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/1876305 Title: Open Gl error Status in xorg package in Ubuntu: New Bug description: Not able to run Paraview it shows the OpenGl error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:02:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0441] InstallationDate: Installed on 2020-04-28 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Vostro 3500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=1532e72e-3f77-4b25-b954-43bbc1c813d0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 058DK5 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn058DK5:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Vostro 3500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2004301830.057275~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005010730.60912f~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876305/+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 1876335] Re: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1876335 Title: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 Status in lvm2 package in Ubuntu: New Bug description: Nie mam pojęcia o co chodzi. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 AptOrdering: ovmf:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 1 15:20:02 2020 DpkgHistoryLog: Start-Date: 2020-05-01 15:19:54 Commandline: /usr/bin/unattended-upgrade Upgrade: ovmf:amd64 (0~20190606.20d2e5a1-2ubuntu1, 0~20190606.20d2e5a1-2ubuntu1.1) ErrorMessage: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2020-04-16 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lvm2 Title: package lvm2 2.03.02-2ubuntu6 failed to install/upgrade: podproces zainstalowany pakiet lvm2 skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1876335/+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 1875577] Re: Encrypted swap won't load on 20.04 with zfs root
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1875577 Title: Encrypted swap won't load on 20.04 with zfs root Status in systemd package in Ubuntu: New Bug description: root@eu1:/var/log# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal root@eu1:/var/log# apt-cache policy cryptsetup cryptsetup: Installed: (none) Candidate: 2:2.2.2-3ubuntu2 Version table: 2:2.2.2-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages OTHER BACKGROUND INFO: == 1. machine has 2 drives. each drive is partitioned into 2 partitions, zfs and swap 2. Ubuntu 20.04 installed on ZFS root using debootstrap (debootstrap_1.0.118ubuntu1_all) 3. The ZFS root pool is a 2 partition mirror (the first partition of each disk) 4. /etc/crypttab is set up as follows: swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 WHAT I EXPECTED === I expected machine would reboot and have encrypted swap that used two devices under /dev/mapper WHAT HAPPENED INSTEAD = On reboot, swap setup fails with the following messages in /var/log/syslog: Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@swap.service/start Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: Found dependency on zfs-load-module.service/start Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting with cryptsetup.target/start . . . . . . Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed Also, /dev/mapper does not contain any swap devices: root@eu1:/var/log# ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Apr 28 17:13 control root@eu1:/var/log# And top shows no swap: MiB Swap: 0.0 total, 0.0 free, 0.0 used. 63153.6 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875577/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support Status in packagekit package in Ubuntu: Triaged Status in packagekit source package in Eoan: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.2, the problem page at https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. [Back trace] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish results = self._pktask.generic_finish(result) gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support (8) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish Gtk.ButtonsType.CANCEL, _("Error while refreshing cache")) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in __init__ self._init(*args, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in __init__ _window_init(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1876354] Re: Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch
** Package changed: ubuntu => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1876354 Title: Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch Status in software-properties package in Ubuntu: New Bug description: Two days ago I have reported a bug describing the complete path starting from the software updater button settings/lifepatch > lifepatch > sign in/lifepatch Then a window was opened Line at top: X [] Ubuntu Single Sign-on Account Next line: same title as above without X [] Next line: Email address: field Next line: (*) I have an Ubuntu Single Sign-on Account Next line: Password: field Next line: ( ) I want to register for an account now Next line: ( ) I've forgotten my password Bottom line: link Privacy Policy There is no button to confirm any action above I looked for help at https://help.ubuntu.com/community/CommunityHelpWiki and clicked on support on the next page https://ubuntu.com/support/community-support I clicked on Lifepatch. Then on https://ubuntu.com/livepatch I found: free for personal use Get Lifepatch. Next page: https://auth.livepatch.canonical.com/?_ga=2.18896568.1031641790.1588091589-177936974.1572286294 Get your Lifepatch token. On the next page I got a key and two command lines to enable Lifepatch https://auth.livepatch.canonical.com/?user_type=ubuntu-user sudo snap install canonical-livepatch sudo canonical-livepatch enable ***key*** (a 32 digits code with letters and numbers) My problem was easily solved using the commands above in a terminal I feel silly that I have reported this two days ago as a bug. I took me two days to find a solution. Now an icon on top toolbar shows that lifepatch is activated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1876354/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
In a virtual machine I can reproduce this by installing pulseaudio and docker.io. I'm attaching a Vagrantfile that reproduces the issue for me. :; vagrant up :; vagrant ssh -t -- journalctl -u rtkit-daemon ** Attachment added: "vagrantfile to reproduce issue" https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+attachment/5364696/+files/Vagrantfile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Incomplete Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1876379] Re: Screen is broken into triangles
Another screen shot, just because it is pretty ** Attachment added: "Screenshot from 2020-04-28 14-15-56.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876379/+attachment/5364697/+files/Screenshot%20from%202020-04-28%2014-15-56.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876379 Title: Screen is broken into triangles Status in xorg package in Ubuntu: New Bug description: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: stem manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876379/+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 1876379] [NEW] Screen is broken into triangles
Public bug reported: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: stem manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Screenshot from 2020-05-01 16-30-30.png" https://bugs.launchpad.net/bugs/1876379/+attachment/5364677/+files/Screenshot%20from%202020-05-01%2016-30-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876379 Title: Screen is broken into triangles Status in xorg package in Ubuntu: New Bug description: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManuf
[Touch-packages] [Bug 1876354] [NEW] Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch
You have been subscribed to a public bug: Two days ago I have reported a bug describing the complete path starting from the software updater button settings/lifepatch > lifepatch > sign in/lifepatch Then a window was opened Line at top: X [] Ubuntu Single Sign-on Account Next line: same title as above without X [] Next line: Email address: field Next line: (*) I have an Ubuntu Single Sign-on Account Next line: Password: field Next line: ( ) I want to register for an account now Next line: ( ) I've forgotten my password Bottom line: link Privacy Policy There is no button to confirm any action above I looked for help at https://help.ubuntu.com/community/CommunityHelpWiki and clicked on support on the next page https://ubuntu.com/support/community-support I clicked on Lifepatch. Then on https://ubuntu.com/livepatch I found: free for personal use Get Lifepatch. Next page: https://auth.livepatch.canonical.com/?_ga=2.18896568.1031641790.1588091589-177936974.1572286294 Get your Lifepatch token. On the next page I got a key and two command lines to enable Lifepatch https://auth.livepatch.canonical.com/?user_type=ubuntu-user sudo snap install canonical-livepatch sudo canonical-livepatch enable ***key*** (a 32 digits code with letters and numbers) My problem was easily solved using the commands above in a terminal I feel silly that I have reported this two days ago as a bug. I took me two days to find a solution. Now an icon on top toolbar shows that lifepatch is activated. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch https://bugs.launchpad.net/bugs/1876354 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- 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 1841274] Re: update to 2.3.0
** Changed in: ilmbase (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ilmbase in Ubuntu. https://bugs.launchpad.net/bugs/1841274 Title: update to 2.3.0 Status in ilmbase package in Ubuntu: Fix Released Bug description: The new version includes a soname change and is still in experimental in Debian, no real reason to update now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1841274/+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 1841276] Re: Update to 2.3
** Changed in: openexr (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1841276 Title: Update to 2.3 Status in openexr package in Ubuntu: Fix Released Bug description: The new version is in Debian experimental and requires a transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1841276/+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 1841295] Re: Update to 2.3.0?
** Changed in: cups (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1841295 Title: Update to 2.3.0? Status in cups package in Ubuntu: Fix Released Bug description: There is a new cups version out, likely not for this cycle though? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1841295/+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 1848008] Re: eoan needs iproute2 v5.3.0
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: iproute2 (Ubuntu) Importance: Undecided => Low ** Changed in: iproute2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1848008 Title: eoan needs iproute2 v5.3.0 Status in iproute2 package in Ubuntu: Fix Released Bug description: As eoan will ship a 5.3 kernel it needs iproute v5.3.0. There are important updates, e.g. to the 'rdma' command which are needed in order to activate certain kernel features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1848008/+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 1857692] Re: [needs-packaging] logrotate -v error compressing - add logrotate 3.14 to bionic (18.04)
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: logrotate (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1857692 Title: [needs-packaging] logrotate -v error compressing - add logrotate 3.14 to bionic (18.04) Status in logrotate package in Ubuntu: Fix Released Bug description: Hi Guys, currently Logrotate 3.11 is shipped with bionic 18.04. logrotate -v /etc/logrotate.conf prints error messages like ``` compressing log with: /bin/gzip error: Compressing program wrote following message to stderr when compressing log /var/log/auth.log-20190716: switching uid to 0 and gid to 109 ``` This is fixed in version 3.14 Source: https://github.com/logrotate/logrotate/blob/3.15.0/ChangeLog.md#3140---2018-03-09 Please add 3.14 to bionic (18.04). If you have any questions, do not hesitate to contact me. Cheers Tim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1857692/+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 1332114] Re: Please update mawk to latest upstream release
https://bugs.launchpad.net/ubuntu/+source/mawk/1.3.4.20200120-2 ** Changed in: mawk (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1332114 Title: Please update mawk to latest upstream release Status in mawk package in Ubuntu: Fix Released Status in mawk package in Debian: Fix Released Bug description: mawk in Ubuntu is 18 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk 1.3.4-2014. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than saving from regressions, see for example bug #1005077 :( Please, update mawk package before major Ubuntu 16.04 LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+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 1536158] Re: Upgrade to 1.1.1 that was released in March 2016
** Changed in: alsa-driver-2.6.28-12 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1536158 Title: Upgrade to 1.1.1 that was released in March 2016 Status in alsa-driver package in Ubuntu: Fix Released Status in alsa-driver-2.6.28-12 package in Ubuntu: Fix Released Bug description: Please, upgrade to 1.1.1 that was released in March 2016, see http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1536158/+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 1876376] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876376 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: package failed to install during 18.04 to 20.04 upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 1 21:41:12 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-05-14 (2179 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876376/+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 1797064] Re: Update to 2.9.8
https://bugs.launchpad.net/ubuntu/+source/libxml2/2.9.10+dfsg-5 ** Changed in: libxml2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1797064 Title: Update to 2.9.8 Status in libxml2 package in Ubuntu: Fix Released Bug description: The new version is in Debian experimental only, why? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1797064/+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 1732566] Re: Update request: protobuf-compiler
https://bugs.launchpad.net/ubuntu/+source/protobuf/3.6.1.3-2ubuntu5 ** Changed in: protobuf (Ubuntu) Importance: Undecided => Wishlist ** Changed in: protobuf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1732566 Title: Update request: protobuf-compiler Status in protobuf package in Ubuntu: Fix Released Status in protobuf package in Debian: Fix Released Bug description: Please can you update the protobuf-compiler package to something fairly recent in the 3.x.x series. (a) backport >=3.5.x to Xenial for LTS, (currently 2.6.0) (b) update Atomic/Bionic (currently 3.0.0, which is vintage 2016) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1732566/+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 1797063] Re: Update to 130
https://bugs.launchpad.net/ubuntu/+source/cron/3.0pl1-136ubuntu1 ** Changed in: cron (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1797063 Title: Update to 130 Status in cron package in Ubuntu: Fix Released Bug description: The new version is in Debian but the changes are not trivial enough to update in cosmic, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1797063/+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 1823700] Re: broken docker-compose version
Bionic has 1.17.1 no 1.23; newer serie are updated https://launchpad.net/ubuntu/+source/docker-compose ** Package changed: file (Ubuntu) => docker-compose (Ubuntu) ** Changed in: docker-compose (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1823700 Title: broken docker-compose version Status in docker-compose package in Ubuntu: Invalid Bug description: Docker-compose version 1.23.1 is buggy and has many issues. Docker-compose team has released a specific release for fixing them. https://github.com/docker/compose/releases/tag/1.23.2 Description:Ubuntu 18.04.2 LTS Release:18.04 Kindly update it to 1.23.2 or higher. Best Regards, Abdullah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1823700/+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 1876376] [NEW] package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: package failed to install during 18.04 to 20.04 upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 1 21:41:12 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-05-14 (2179 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876376 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: package failed to install during 18.04 to 20.04 upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 1 21:41:12 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-05-14 (2179 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876376/+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 1840534] Re: Request package upgrade for iproute2 in Ubuntu Bionic
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: iproute2 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: iproute2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1840534 Title: Request package upgrade for iproute2 in Ubuntu Bionic Status in iproute2 package in Ubuntu: Fix Released Bug description: iproute2's version in Bionic is: 4.18.0-1ubuntu2~ubuntu18.04.1 But only 4.19 contains support for CAKE qdisc. https://lwn.net/Articles/769354/ Please update the package ASAP! Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1840534/+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 1876369] Re: garbled/frozen screen after waking from sleep mode
** Package changed: ubuntu => xorg (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/1876369 Title: garbled/frozen screen after waking from sleep mode Status in xorg package in Ubuntu: New Bug description: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power- off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.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 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876369/+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 1876372] [NEW] ubuntu-bug does not exit, does not launch browser
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 While trying to report a problem with a messed up X display after a new install, I logged in with ssh -X and ran ubuntu-bug with no arguments. It didn't bring up a web browser, and it didn't finish until I hit ctrl-C Specifying a package did work for me (ubuntu-bug apport) to produce this bug report. folder@folder-System:~$ ubuntu-bug AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: folder,,, (folder) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. -- I hit ctrl-C here --- ^CTraceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 711, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 458, in run_report_bug if self.run_symptoms(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 681, in run_symptoms self.run_report_bug(os.path.join(symptom_script_dir, symptom + '.py')) File "/usr/lib/python3/dist-packages/apport/ui.py", line 550, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-gtk", line 380, in ui_present_report_details Gtk.main() File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1632, in main return _Gtk_main(*args, **kwargs) File "/usr/lib/python3.8/contextlib.py", line 120, in __exit__ next(self.gen) File "/usr/lib/python3/dist-packages/gi/_ossighelper.py", line 251, in register_sigint_fallback signal.default_int_handler(signal.SIGINT, None) KeyboardInterrupt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 1 15:46:45 2020 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1876372 Title: ubuntu-bug does not exit, does not launch browser Status in apport package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 While trying to report a problem with a messed up X display after a new install, I logged in with ssh -X and ran ubuntu-bug with no arguments. It didn't bring up a web browser, and it didn't finish until I hit ctrl-C Specifying a package did work for me (ubuntu-bug apport) to produce this bug report. folder@folder-System:~$ ubuntu-bug AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: folder,,, (folder) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. -- I hit ctrl-C here --- ^CTraceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 711, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 458, in run_report_bug if self.run_symptoms(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 681, in run_symptoms self.run_report_bug(os.path.join(symptom_script_dir, symptom + '.py')) File "/usr/lib/python3/dist-packages/apport/ui.py", line 550, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-gtk", line 380, in ui_present_report_details Gtk.main() File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1632, in main return _Gtk_main(*args, **kwargs) File "/usr/lib/python3.8/contextlib.py", line 120, in __exit__ next(self.gen) File "/usr/lib/python3/dist-packages/gi/_ossighelper.py", line 251, in register_sigint_fallback signal.default_int_handler(signal.SIGINT, None) KeyboardInterrupt ProblemType: Bug DistroRelease
[Touch-packages] [Bug 1876348] Re: macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen.
** Package changed: ubuntu => xorg (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/1876348 Title: macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen. Status in xorg package in Ubuntu: New Bug description: System suspend does not work on Macbook air2009-2010. (MBair 2.1) System hangs indefinitely in a black screen. May or may not be related, power manager won't charge battery to 100%. 95% seems to be the upper limit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 1 19:54:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0870] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00ab] InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Apple Inc. MacBookAir2,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA21.88Z.0075.B03.0811141325 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D88C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8: dmi.product.family: MacBook dmi.product.name: MacBookAir2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876348/+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 1876348] [NEW] macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen.
You have been subscribed to a public bug: System suspend does not work on Macbook air2009-2010. (MBair 2.1) System hangs indefinitely in a black screen. May or may not be related, power manager won't charge battery to 100%. 95% seems to be the upper limit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 1 19:54:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0870] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00ab] InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Apple Inc. MacBookAir2,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA21.88Z.0075.B03.0811141325 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D88C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8: dmi.product.family: MacBook dmi.product.name: MacBookAir2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- macbook air 2009-2010. Pauzestand (suspend) does not work properly. System hangs indefinetly with a black screen. https://bugs.launchpad.net/bugs/1876348 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1876369] [NEW] garbled/frozen screen after waking from sleep mode
You have been subscribed to a public bug: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power-off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.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 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 focal ubuntu -- garbled/frozen screen after waking from sleep mode https://bugs.launchpad.net/bugs/1876369 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1876272] Re: GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok)
Thanks! ** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged -- 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/1876272 Title: GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok) Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Hi, I recently started using Dvarok full time, and some (all GTK) software in Ubuntu fails to identify the changed layout when shortcuts (Ctrl + C, Ctrl + X, Ctrl + V etc) are pressed. For example, Ctrl + X makes text bold in Geary, as X is positioned where B would be in a Qwerty. In all GTK software Ctrl + V offers me to input emojis, but doesn't paste anything. Other software where I notice the same behaviour is Nautilus, the Gnome terminal, Ubuntu Software, Gnome Maps, Gnome Weather, Gnome Calendar, and the default Calculator. All non-gtk software behaves normally (such as Rstudio, LibreOffice, Atom, and FireFox). I'm currently running a Flatpak version of Geary installed in 18.04, while the rest are from default repositories. The behaviour is the same. Ctrl + Shift + C enters "^C" in the terminal, while Ctrl + Shift + J copies. I have rebooted the computer many times since switching to Dvarok. EDIT: The issue is connected to Wayland - after switching to X all applications behave normally. Sorry for not knowing the appropriate place to lodge this bug, or if it's a duplicate. Thanks for your work! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 11:09:43 2020 InstallationDate: Installed on 2019-08-08 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-13 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1876272/+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 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
I have the same problem. However, I'm able to record audio (with internal mic) using audacity. Also, plugged in microphone/phones work ok. -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+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 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+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 1873384] Re: [Dell Inspiron 5577] Headphone has no sound out
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1873384 Title: [Dell Inspiron 5577] Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard
Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Confirmed Bug description: After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones Status in alsa-driver package in Ubuntu: New Bug description: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1875032] Re: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875032 Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: This problem only occurs when I plug my headphone and choose Headphone in option. If I choose Headset, though plugging either headphone or headset, it works perfectly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prm1856 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 20:05:01 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2018-09-28 (575 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prm1856 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 05/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 03NJH0 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd05/29/2019:svnDellInc.:pnVostro3470:pvr:rvnDellInc.:rn03NJH0:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3470 dmi.product.sku: 0869 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032/+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 1875714] Re: No sound from headphones
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Please test PPA here: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875714 Title: No sound from headphones Status in alsa-driver package in Ubuntu: New Bug description: Hi, I upgraded to focal and since then I have the following problems with my audio on my laptop: 1. If I start my laptop with my headphones pluged-in I initially have sound from my headphones, If I unplug my headphones speakers work normally. But when insert my headphone again the sound stops from the speakers but I have no sound from my headphones. To "fix" the problem I have to go to the kde systemsettings and in "audio" settings in the advanced tab change the profile to something else and then restore the option. If I start the laptop WITHOUT the headphones pluged-in then everything works as it should. I have deleted the ~./config/pulse folder but it changes nothing. 2. If the computer starts WITHOUT headphones and the computer goes into hibernation when it wakes I get a static noise from the speakers (although the headphones are plugined-in) I have to reboot the computer in order to fix this. Kind Regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 21:37:41 2020 InstallationDate: Installed on 2018-11-22 (523 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-04-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875714/+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 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify
Check also `systemctl cat ssh.service` and `systemctl cat secondssh.service` -- sshd also accepts parameters on the commandline, perhaps the port is being specified outside of the configuration files. Thanks -- 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/1876320 Title: Port parameter sshd_config is 22 AND whatever you specify Status in openssh package in Ubuntu: New Bug description: On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd deamons. One (on port 22) is for internal use, accepts passwords etc. The second (on port 7722) does not allow PAM use and no passwords, allows only one user(name) and uses an alternative autorized_keys file (that only root can edit). Any parameter FIRST encountered in sshd_config is the one that is accepted; others do not override (like in many other config files). There is one exception: 'Port', which is accumulative. To make life easier, I set the more restrictive parameters for port 7722 first and next include the system-default /etc/ssh/sshd_config. The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify 'Port' anywhere - the default is 22. But: it is obviously still accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722 AND 22. This is unwanted. Proposed solution: Remove the accumulative behavior for 'Port' and REQUIRE the 'Port' parameter like before (and maybe have second and later parameters override the earlier ones, like 'everyone else'). Regards, Adriaan PS Searching for solutions, I found that specifying 'ListenAddress 0.0.0.0:7722' stops sshd from listening to port 22. This, however, is not documented in 'man 5 sshd_config' and may be an unreliable side- effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320/+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 1875091] Re: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2"
Replacing mesa-opencl-icd with the version from Ubuntu 19.10 (mesa- opencl-icd_19.2.8-0ubuntu0~19.10.3_amd64.deb) is enough to make things work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875091 Title: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2" Status in mesa package in Ubuntu: New Bug description: Both luxmark and leelaz, the two OpenCL applications I have, fail at runtime with the same error, looking for "amdgpu_cs_query_reset_state2" in /usr/lib/x86_64-linux-gnu/gallium- pipe/pipe_radeonsi.so This is on a system with a relatively new AMD GPU, freshly upgraded from 18.04. Leela zero worked correctly in 18.04, and I've tried various compiler options, openCL config and such with no success. I don't know about luxmark but installed it to test. Since it reports the same error, I think it's a bug to report here. Platform Name Clover Device Name AMD Radeon (TM) RX Graphics (POLARIS11, DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1) Device Name AMD RAVEN (DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1) 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev c0) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi everybody, On my asus, the sound come back after a standby. Good luck Le ven. 1 mai 2020 à 17:30, Filippo Saglimbeni <1742...@bugs.launchpad.net> a écrit : > Hi everyone! > Asus Zenbook UX533FTC has the same problem with Ubuntu 20.04 with Windows > 10 in dual boot. > > 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 > > uname -r > 5.4.0-26-generic > > No sound at all. It's a good while I'm stuck on this... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1742852 > > Title: > [hostname, Realtek ALC294, Speaker, Internal] No sound at all after > windows update > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > After a windows update I lost all the sound on my ubuntu machine. It's > the second time that this happends. > My sound is unmuted and at a loud level and nothing is comming out of my > speakers. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 > Uname: Linux 4.13.0-26-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gbergeron 2408 F pulseaudio > gbergeron 3656 F alsamixer > CurrentDesktop: Unity > Date: Thu Jan 11 22:21:23 2018 > InstallationDate: Installed on 2017-11-29 (43 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio >/dev/snd/controlC0: gbergeron 2408 F pulseaudio > gbergeron 3656 F alsamixer > Symptom_Jack: Speaker, Internal > Symptom_Type: No sound at all > Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/23/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX430UAR.203 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX430UAR > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: UX > dmi.product.name: UX430UAR > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.
[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi everyone! Asus Zenbook UX533FTC has the same problem with Ubuntu 20.04 with Windows 10 in dual boot. 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 uname -r 5.4.0-26-generic No sound at all. It's a good while I'm stuck on this... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
https://github.com/libimobiledevice/libimobiledevice/issues/941 ** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #941 https://github.com/libimobiledevice/libimobiledevice/issues/941 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
I've upgraded to 20.04 and have checked out the installed versions. For now, I was able to get it working "just" by upgrading libimobiledevice to the latest git and building against gnutls (using openssl resulted in it needing to re-trust every time I plug in because the TLS information it is saving is wrong, somehow). The other libraries are new enough now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Ok, so this is progress. Building against gnutls fixes the trust pairing, but breaks file transfers. I rebuild the same source with openssl vs gnutls and that's exactly what I see. With openssl I have to re-pair every time I plug in but with gnutls, the file transfers don't work. The official ubuntu build uses gnutls so that's why we see the behaviour we do, and why the git version ubuntu uses should be new enough - it is with openssl. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1876272] Re: GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok)
Thanks, I just did. https://gitlab.gnome.org/GNOME/gtk/-/issues/2682 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2682 https://gitlab.gnome.org/GNOME/gtk/-/issues/2682 -- 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/1876272 Title: GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok) Status in gtk+3.0 package in Ubuntu: New Bug description: Hi, I recently started using Dvarok full time, and some (all GTK) software in Ubuntu fails to identify the changed layout when shortcuts (Ctrl + C, Ctrl + X, Ctrl + V etc) are pressed. For example, Ctrl + X makes text bold in Geary, as X is positioned where B would be in a Qwerty. In all GTK software Ctrl + V offers me to input emojis, but doesn't paste anything. Other software where I notice the same behaviour is Nautilus, the Gnome terminal, Ubuntu Software, Gnome Maps, Gnome Weather, Gnome Calendar, and the default Calculator. All non-gtk software behaves normally (such as Rstudio, LibreOffice, Atom, and FireFox). I'm currently running a Flatpak version of Geary installed in 18.04, while the rest are from default repositories. The behaviour is the same. Ctrl + Shift + C enters "^C" in the terminal, while Ctrl + Shift + J copies. I have rebooted the computer many times since switching to Dvarok. EDIT: The issue is connected to Wayland - after switching to X all applications behave normally. Sorry for not knowing the appropriate place to lodge this bug, or if it's a duplicate. Thanks for your work! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 11:09:43 2020 InstallationDate: Installed on 2019-08-08 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-13 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1876272/+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 1876219] Re: iris driver for old cpu
file bugs upstream at https://gitlab.freedesktop.org/mesa/mesa iris supports intel gpu's gen8 and up (meaning broadwell and newer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: New Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1856884] Re: When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1856884 Title: When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand. Status in pulseaudio package in Ubuntu: Confirmed Bug description: when i insert or take out my headphones , the system doesn't send signal on my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1929 F pulseaudio /dev/snd/controlC1: rob1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (326 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (411 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify
On a stock install, adding "Port 7722" to /etc/ssh/sshd_config and restarting sshd gives me this: # ss -nltp | grep sshd LISTEN0 128 0.0.0.0:77220.0.0.0:* users:(("sshd",pid=10651,fd=3)) LISTEN0 128 [::]:7722 [::]:* users:(("sshd",pid=10651,fd=4)) So 1 daemon, bounding to port 7722 on IPv4 and IPv6 wildcards. -- 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/1876320 Title: Port parameter sshd_config is 22 AND whatever you specify Status in openssh package in Ubuntu: New Bug description: On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd deamons. One (on port 22) is for internal use, accepts passwords etc. The second (on port 7722) does not allow PAM use and no passwords, allows only one user(name) and uses an alternative autorized_keys file (that only root can edit). Any parameter FIRST encountered in sshd_config is the one that is accepted; others do not override (like in many other config files). There is one exception: 'Port', which is accumulative. To make life easier, I set the more restrictive parameters for port 7722 first and next include the system-default /etc/ssh/sshd_config. The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify 'Port' anywhere - the default is 22. But: it is obviously still accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722 AND 22. This is unwanted. Proposed solution: Remove the accumulative behavior for 'Port' and REQUIRE the 'Port' parameter like before (and maybe have second and later parameters override the earlier ones, like 'everyone else'). Regards, Adriaan PS Searching for solutions, I found that specifying 'ListenAddress 0.0.0.0:7722' stops sshd from listening to port 22. This, however, is not documented in 'man 5 sshd_config' and may be an unreliable side- effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320/+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 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify
@Adriaan, are there really 2 sshd running? Or is it only one binding to the 2 ports and applying different parameter using Match conditions? Beware what on 20.04, there is support for additional config snippets dropped in /etc/ssh/sshd_config.d/*.conf. To check for 2 daemons: sudo ss -nltp | grep sshd -- 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/1876320 Title: Port parameter sshd_config is 22 AND whatever you specify Status in openssh package in Ubuntu: New Bug description: On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd deamons. One (on port 22) is for internal use, accepts passwords etc. The second (on port 7722) does not allow PAM use and no passwords, allows only one user(name) and uses an alternative autorized_keys file (that only root can edit). Any parameter FIRST encountered in sshd_config is the one that is accepted; others do not override (like in many other config files). There is one exception: 'Port', which is accumulative. To make life easier, I set the more restrictive parameters for port 7722 first and next include the system-default /etc/ssh/sshd_config. The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify 'Port' anywhere - the default is 22. But: it is obviously still accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722 AND 22. This is unwanted. Proposed solution: Remove the accumulative behavior for 'Port' and REQUIRE the 'Port' parameter like before (and maybe have second and later parameters override the earlier ones, like 'everyone else'). Regards, Adriaan PS Searching for solutions, I found that specifying 'ListenAddress 0.0.0.0:7722' stops sshd from listening to port 22. This, however, is not documented in 'man 5 sshd_config' and may be an unreliable side- effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320/+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 1876279] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1876279 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** 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/1876279 Title: Xorg freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am the beginner with Linux and Ubuntu.And some Android habit that I can't give up . So I just try to classify my application with click on the button of "Show Application ", and drag all the LibreOffice application in one folder like Android does, but I find out that it usually frozen when I trying to leave the folder ,you may try click the folder and out frequently, and it frozen, the result is come from my experiment, I'm not sure I am the only person who encounter this problem. The situation was the screen stopped at "Show Application", but "spotify" still playing the song at the background. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 18:29:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0567] MachineType: Acer TravelMate 8481 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=44a3c145-e212-4d4e-b563-ad4206dfe924 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA41_HS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnAcer:bvrV2.06:bd10/28/2011:svnAcer:pnTravelMate8481:pvrV2.06:rvnAcer:rnBA41_HS:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.06: dmi.product.name: TravelMate 8481 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876279/+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 1876189] Re: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
'Configuration file '/etc/sysfs.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** sysfs.conf (Y/I/N/O/D/Z) [default=N] ? d D sh: 1: pager: not found diff: standard output: Broken pipe' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1876189 Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 Status in debconf package in Ubuntu: New Bug description: I think this was due to forcing an update to 20.04 lts from 18.04 lts. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sysfsutils 2.1.0+repack-6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 29 16:18:06 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-15 (15 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: sysfsutils Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago) modified.conffile..etc.sysfs.conf: [modified] mtime.conffile..etc.sysfs.conf: 2020-04-17T18:17:04.410519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1876189/+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 1876272] Re: GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok)
Could you report it upstream on https://gitlab.gnome.org/GNOME/gtk/issues ? ** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- 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/1876272 Title: GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok) Status in gtk+3.0 package in Ubuntu: New Bug description: Hi, I recently started using Dvarok full time, and some (all GTK) software in Ubuntu fails to identify the changed layout when shortcuts (Ctrl + C, Ctrl + X, Ctrl + V etc) are pressed. For example, Ctrl + X makes text bold in Geary, as X is positioned where B would be in a Qwerty. In all GTK software Ctrl + V offers me to input emojis, but doesn't paste anything. Other software where I notice the same behaviour is Nautilus, the Gnome terminal, Ubuntu Software, Gnome Maps, Gnome Weather, Gnome Calendar, and the default Calculator. All non-gtk software behaves normally (such as Rstudio, LibreOffice, Atom, and FireFox). I'm currently running a Flatpak version of Geary installed in 18.04, while the rest are from default repositories. The behaviour is the same. Ctrl + Shift + C enters "^C" in the terminal, while Ctrl + Shift + J copies. I have rebooted the computer many times since switching to Dvarok. EDIT: The issue is connected to Wayland - after switching to X all applications behave normally. Sorry for not knowing the appropriate place to lodge this bug, or if it's a duplicate. Thanks for your work! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 11:09:43 2020 InstallationDate: Installed on 2019-08-08 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-13 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1876272/+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 1876272] [NEW] GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok)
You have been subscribed to a public bug: Hi, I recently started using Dvarok full time, and some (all GTK) software in Ubuntu fails to identify the changed layout when shortcuts (Ctrl + C, Ctrl + X, Ctrl + V etc) are pressed. For example, Ctrl + X makes text bold in Geary, as X is positioned where B would be in a Qwerty. In all GTK software Ctrl + V offers me to input emojis, but doesn't paste anything. Other software where I notice the same behaviour is Nautilus, the Gnome terminal, Ubuntu Software, Gnome Maps, Gnome Weather, Gnome Calendar, and the default Calculator. All non-gtk software behaves normally (such as Rstudio, LibreOffice, Atom, and FireFox). I'm currently running a Flatpak version of Geary installed in 18.04, while the rest are from default repositories. The behaviour is the same. Ctrl + Shift + C enters "^C" in the terminal, while Ctrl + Shift + J copies. I have rebooted the computer many times since switching to Dvarok. EDIT: The issue is connected to Wayland - after switching to X all applications behave normally. Sorry for not knowing the appropriate place to lodge this bug, or if it's a duplicate. Thanks for your work! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 11:09:43 2020 InstallationDate: Installed on 2019-08-08 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-13 (17 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug focal wayland-session -- GTK + Wayland: Keyboard shortcuts not adapting non-Qwerty keyboard layout (Dvarok) https://bugs.launchpad.net/bugs/1876272 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- 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 1876143] Re: Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia-driver-390
Hi! I just wanted to say that I had this problem and also I was unable to use an external monitor connected via HDMI even using nouveau. So I switched to version 340 driver and that caused some apt errors about nvidia-340-* and nvidia-driver-390-* (some dependency conflict with nvidia-340 files when installing 390) and made my system completely unbootable with some LVM mounting errors. But after restoring it back using "LC_MESSAGES=C dpkg-divert --list '*nvidia-340*' | sed -nre 's/^diversion of (.*) to .*/\1/p' | xargs -rd'\n' -n1 -- sudo dpkg- divert --remove" I realized my external monitor started to work with version 390. Also, WebKit is not crashing anymore! I don't know how to explain it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1876143 Title: Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia- driver-390 Status in gnome-online-accounts package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04 LTS today, and tried to add google and facebook account. Webkit crashes, and loading stops. When using open-source nvidia driver it works.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.28.2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 18:41:23 2020 InstallationDate: Installed on 2020-04-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1876143/+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 1876189] Re: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
** Package changed: sysfsutils (Ubuntu) => debconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1876189 Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 Status in debconf package in Ubuntu: New Bug description: I think this was due to forcing an update to 20.04 lts from 18.04 lts. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sysfsutils 2.1.0+repack-6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 29 16:18:06 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-15 (15 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: sysfsutils Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago) modified.conffile..etc.sysfs.conf: [modified] mtime.conffile..etc.sysfs.conf: 2020-04-17T18:17:04.410519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1876189/+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 1876145] Re: Unable to scroll list of sessions by mouse wheel or keyboard
*** This bug is a duplicate of bug 1068605 *** https://bugs.launchpad.net/bugs/1068605 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1279345, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1068605 List of session type does not fit on screen with many window managers installed -- 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/1876145 Title: Unable to scroll list of sessions by mouse wheel or keyboard Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed with many desktop sessions 2. Boot the machine 3. Try to specify graphical user session on the LightDM greeter screen by mouse or by keyboard Expected results: * the list of graphical sessions may be scrolled by mouse and/or by keyboard Actual results: * it is impossible to view all graphical sessions and scroll to one of them using keyboard and/or mouse (on the attached screenshot it is impossible to view sessions below Dwm). ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: lightdm 1.30.0-0ubuntu3.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Deepin Date: Thu Apr 30 19:48:12 2020 InstallationDate: Installed on 2020-04-22 (7 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) LightdmConfig: [Seat:*] autologin-guest=false allow-guest=false SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1876145/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
@rbalint sounds good to me, thanks! -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Confirmed Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 979 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 57662) Memory: 4.1M CGroup: /system.slice/systemd-networkd.service └─979 /lib/systemd/systemd-networkd Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for link '5' we don't know about, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received neighbor message with invalid family, ignoring. Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring. systemctl restart systemd-networkd resolved the issue and a systemctl status systemd-network producessystemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
[Touch-packages] [Bug 1876195] Re: /var is filed with errors logs (from network) until it is over 60 Gb sized
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1876195 Title: /var is filed with errors logs (from network) until it is over 60 Gb sized Status in linux package in Ubuntu: Incomplete Bug description: Hello, I installed Ubuntu 20.04 a few days ago, at release. Yesterday I got a warning about low remaining space on disk. Unable to access my files I restarted my computer. Ubuntu failed to boot and I got the code : [10.688299] ccp :0a:00.2: sev command 0x4 timed out, disabling PSP [10.688353] cpp :0a:00.2: SEV: failed to get status. Error: 0x0 I started Ubuntu with Advanced options and try repair my packages. It warned me I had not enough space to do that so I deleted part of my files in root mode, which allowed me to restart. I ran the disk analyser which show me I had a 60 gigabytes /var directory. ls -lSh /var/log command show : total 50G -rw-r- 1 syslogadm 50G avril 29 23:53 syslog -rw-r- 1 syslogadm 21M avril 29 23:38 kern.log -rw-r- 1 syslogadm 13M avril 26 00:00 kern.log.1 -rw-r- 1 syslogadm 4,5M avril 29 00:00 syslog.1 -rw-r- 1 syslogadm 1,3M avril 25 00:00 syslog.5.gz -rw-r--r-- 1 root root1,2M avril 29 19:18 dpkg.log -rw-r- 1 syslogadm 795K avril 28 00:00 syslog.2.gz -rw-rw-r-- 1 root utmp286K avril 24 00:20 lastlog -rw-r- 1 syslogadm 279K avril 26 00:00 syslog.4.gz -rw-r- 1 syslogadm 134K avril 27 00:00 syslog.3.gz -rw-r--r-- 1 root root102K avril 23 09:33 bootstrap.log -rw-r--r-- 1 root adm 92K avril 29 23:37 dmesg -rw-r--r-- 1 root adm 92K avril 29 23:20 dmesg.0 -rw-r- 1 syslogadm 80K avril 25 23:30 auth.log.1 -rw-r--r-- 1 root root 57K avril 29 20:15 Xorg.1.log.old -rw--- 1 root root 54K avril 29 23:37 boot.log -rw--- 1 root root 45K avril 25 00:00 boot.log.4 -rw-r- 1 syslogadm 44K avril 29 23:39 auth.log -rw-r--r-- 1 root root 39K avril 29 23:38 Xorg.1.log -rw-r--r-- 1 root root 38K avril 29 23:38 Xorg.0.log -rw-r--r-- 1 root root 38K avril 29 00:28 alternatives.log -rw-r--r-- 1 root root 32K avril 24 00:20 faillog -rw-rw-r-- 1 root utmp 22K avril 29 23:38 wtmp -rw--- 1 root root 21K avril 29 00:00 boot.log.1 -rw-r--r-- 1 root adm 21K avril 29 20:21 dmesg.2.gz -rw-r--r-- 1 root adm 21K avril 29 23:18 dmesg.1.gz -rw-r--r-- 1 root adm 21K avril 29 20:16 dmesg.4.gz -rw-r--r-- 1 root adm 21K avril 29 20:19 dmesg.3.gz -rw-r--r-- 1 root root 17K avril 29 23:20 Xorg.0.log.old -rw-r--r-- 1 root root 11K avril 24 02:46 fontconfig.log -rw--- 1 root root 11K avril 27 00:00 boot.log.2 -rw--- 1 root root 11K avril 26 00:00 boot.log.3 -rw-r- 1 root adm 6,1K avril 28 23:06 apport.log.1 drwxr-xr-x 2 root root4,0K avril 29 19:18 apt drwxr-xr-x 2 root root4,0K avril 29 00:00 cups drwxr-xr-x 2 root root4,0K avril 29 23:23 dist-upgrade drwx--x--x 2 root gdm 4,0K oct. 7 2019 gdm3 drwxr-xr-x 3 root root4,0K avril 23 09:36 hp drwxr-xr-x 2 root root4,0K avril 23 21:31 installer drwxr-sr-x+ 3 root systemd-journal 4,0K avril 23 21:39 journal drwxr-xr-x 2 root root4,0K sept. 5 2019 openvpn drwx-- 2 root root4,0K avril 23 09:32 private drwx-- 2 speech-dispatcher root4,0K janv. 19 19:26 speech-dispatcher drwxr-x--- 2 root adm 4,0K avril 24 13:46 unattended-upgrades -rw-rw-r-- 1 root tistus 1,2K avril 29 23:20 gpu-manager-switch.log -rw-r--r-- 1 root root1,2K avril 29 23:37 gpu-manager.log -rw-r- 1 root adm 363 avril 24 22:48 apport.log.2.gz -rw-r- 1 root adm0 avril 29 23:20 apport.log
[Touch-packages] [Bug 1876189] [NEW] package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
You have been subscribed to a public bug: I think this was due to forcing an update to 20.04 lts from 18.04 lts. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sysfsutils 2.1.0+repack-6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 29 16:18:06 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-15 (15 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: sysfsutils Title: package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago) modified.conffile..etc.sysfs.conf: [modified] mtime.conffile..etc.sysfs.conf: 2020-04-17T18:17:04.410519 ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- package sysfsutils 2.1.0+repack-6 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 https://bugs.launchpad.net/bugs/1876189 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. -- 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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Could you also verify if the bionic SRU create a regression? In which case we should mark it as verification-failed -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1876056] Re: No automatic switch to headset microphone on connect
Thank, if you are not using GNOME that explains you are not seeing the UI. I suggest you report a bug against KDE but I don't know what's the right component there. Also closing that one rather than reassigning because a cleaner state report is probably going to be easier to read and understand ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1876056 Title: No automatic switch to headset microphone on connect Status in pulseaudio package in Ubuntu: Invalid Bug description: On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector, the audio OUTPUT automatically switches from the speakers in the laptop to the headset. However, the audio INPUT does not switch from the microphone in the laptop to the microphone in the headset. Using for example pavucontrol, I can switch to the microphone manually on the tab 'input devices' - on that tab Port will be on 'Internal Microphone' and I can set it to 'Headset Microphone'. What's even more confusing is that when I unplug the headset, both input AND output switch back to internal automatically and the port on the 'Input Devices'. This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also see the same issue on kernel 5.3.0-48) and pulseaudio 1:13.0-1ubuntu1.1. If any more information is needed, let me know. inxi -F: System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 Desktop: KDE Plasma 5.16.5 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: Mobo: Dell model: 0VYV0G v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/25/2019 Battery: ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) CPU: Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP L2 cache: 12.0 MiB Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 9: 4291 10: 4198 11: 4149 12: 4188 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Sound Server: ALSA v: k5.4.28-050428-generic Network: Device-1: Intel driver: iwlwifi IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 953.87 GiB Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB (29.2%) Shell: bash inxi: 3.0.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: rtkit (Ubuntu) Importance: Undecided => Low ** Changed in: rtkit (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Incomplete Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I can confirm that the update to 20.04 fixed the audio and microphone for me! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1381050] Re: "Import Key File" fails when the path of the file has special characters
** Changed in: software-properties (Ubuntu Trusty) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1381050 Title: "Import Key File" fails when the path of the file has special characters Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Trusty: Confirmed Bug description: [Impact] Importing a key that is in a path that contains special characters (like "/home/$USER/Transferências") fails silently. [Test Case] 1. Download a PGP key for a Debian repository (for example, the VideoLAN team's key: download.videolan.org/pub/debian/videolan-apt.asc) 2. Move the key file to a folder that contains special characters, or rename the file to contain them (example: VídeoLAN.asc). 3. Open "Software & Updates" from the Dash, then select the Authentication tab. 4. Press the "Import Key File..." button and then choose the key file. Admin authentication should then be requested, so authenticate yourself. If the bug is fixed: the key should now appear in the list of keys. If not: the key was not added. [Regression Potential] If the fix is not correct, I suppose it could potentially break the "import key" feature even more, so it wouldn't work even in "normal" paths. [Original Report] The "Import Key File..." button in the "Authentication" tab fails silently when the path of the selected key file includes special characters. I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is named "/home/$USER/Transferências" here. Adding a key from that folder fails, but adding a key from "/home/$USER" (no special characters) succeeds. The problem is that, in softwareproperties/gtk/SoftwarePropertiesGtk.py in method SoftwarePropertiesGtk.add_key_clicked() at around line 952: if res == Gtk.ResponseType.ACCEPT: try: if not self.backend.AddKey(chooser.get_filename()): error(self.window_main, _("Error importing selected file"), _("The selected file may not be a GPG key file " "or it might be corrupt.")) except dbus.DBusException as e: if e._dbus_error_name == 'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy': logging.error("Authentication canceled, changes have not been saved") "self.backend.AddKey(chooser.get_filename())" throws a "org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with special characters. This is probably a side effect of switching from Python 2 to 3 (and 'bytes' now being used in network communications where 'str' was previously used). Another issue is that the error isn't reported to the user, and it should be. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 14 13:22:21 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-13 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1876277] Re: Background image gets corrupted after login
** Package changed: xorg (Ubuntu) => gnome-2048 (Ubuntu) ** Description changed: Problem: Small squares with random pixel colors appear on desktop background image. - Additional info (forgive me if some of these are included in the bug details that was automatically uploaded): + Additional info (forgive me if some of these are included in the bug details that was automatically uploaded): 1- My laptop has two graphic cards: Intel and NVIDIA and it's using Intel as the default card (It's written in the About page of the Settings) 2- I also have Windows on my laptop and it doesn't happen there. 3- Changing the background solves the issue but only until the next restart. Also, changing it back to the image that was corrupted returns the corrupted pixels exactly the way they were. They somehow get attached to that specific image. 4- I'm using Ubuntu 20.04. 5- Sometimes those squares appear in the login screen too. 6- I have attached a screenshot of the desktop (1.jpg in the zip file I've attached) 7- Another observation I've had is that right after I enter my password in the login page, the screen somehow "flashes" once and some lines appear on the screen (2.jpg in the zip file) What I've tried: 1- I tried changing the NVIDIA driver from xorg to NVIDIA's own driver (version 440) but no luck. 2- Tried "dconf reset -f /org/gnome/" and it didn't help. Workarounds I've found: - Restarting Gnome using Alt+F2 and entering r will solve the problem but only until the next restart. + 1- Restarting Gnome using Alt+F2 and entering r will solve the problem but only until the next restart. + 2- I changed the DE to Ubuntu on Wayland and the issue is gone. It seems like gnome has some kind of incompatibility with something. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 14:36:55 2020 DistUpgraded: 2020-05-01 02:56:41,056 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:820d] -Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 960M] [103c:820d] + Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:820d] + Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 960M] [103c:820d] InstallationDate: Installed on 2019-07-15 (290 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 8087:0a2a Intel Corp. - Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD - Bus 001 Device 002: ID 046d:c058 Logitech, Inc. M115 Mouse - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0a2a Intel Corp. + Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD + Bus 001 Device 002: ID 046d:c058 Logitech, Inc. M115 Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9da90290-adcc-4ed3-9f63-fae1bb7364cd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820D dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820D:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: X1G64PA#AB4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xse
[Touch-packages] [Bug 1876320] [NEW] Port parameter sshd_config is 22 AND whatever you specify
Public bug reported: On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd deamons. One (on port 22) is for internal use, accepts passwords etc. The second (on port 7722) does not allow PAM use and no passwords, allows only one user(name) and uses an alternative autorized_keys file (that only root can edit). Any parameter FIRST encountered in sshd_config is the one that is accepted; others do not override (like in many other config files). There is one exception: 'Port', which is accumulative. To make life easier, I set the more restrictive parameters for port 7722 first and next include the system-default /etc/ssh/sshd_config. The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify 'Port' anywhere - the default is 22. But: it is obviously still accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722 AND 22. This is unwanted. Proposed solution: Remove the accumulative behavior for 'Port' and REQUIRE the 'Port' parameter like before (and maybe have second and later parameters override the earlier ones, like 'everyone else'). Regards, Adriaan PS Searching for solutions, I found that specifying 'ListenAddress 0.0.0.0:7722' stops sshd from listening to port 22. This, however, is not documented in 'man 5 sshd_config' and may be an unreliable side- effect. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1876320 Title: Port parameter sshd_config is 22 AND whatever you specify Status in openssh package in Ubuntu: New Bug description: On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd deamons. One (on port 22) is for internal use, accepts passwords etc. The second (on port 7722) does not allow PAM use and no passwords, allows only one user(name) and uses an alternative autorized_keys file (that only root can edit). Any parameter FIRST encountered in sshd_config is the one that is accepted; others do not override (like in many other config files). There is one exception: 'Port', which is accumulative. To make life easier, I set the more restrictive parameters for port 7722 first and next include the system-default /etc/ssh/sshd_config. The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify 'Port' anywhere - the default is 22. But: it is obviously still accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722 AND 22. This is unwanted. Proposed solution: Remove the accumulative behavior for 'Port' and REQUIRE the 'Port' parameter like before (and maybe have second and later parameters override the earlier ones, like 'everyone else'). Regards, Adriaan PS Searching for solutions, I found that specifying 'ListenAddress 0.0.0.0:7722' stops sshd from listening to port 22. This, however, is not documented in 'man 5 sshd_config' and may be an unreliable side- effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi there. Asus UX563FD has the same problem on Ubuntu 20.4 with Windows dual boot. cat /proc/asound/pcm 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 uname -r 5.4.0-28-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi there. Asus UX563FD has the same problem on Ubuntu 20.4 with Windows dual boot. cat /proc/asound/pcm 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 uname -r 5.4.0-28-generic I mean problem with no sound. How can I fix it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Same here, cannot switch profile to HSP/HFP for Soundcore Life P2 on an ThinkPad T430s: Device E8:07:BF:9B:23:D2 (public) Name: Soundcore Life P2 Alias: Soundcore Life P2 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Vendor specific (eb03-d102-11e1-9b23-00025b00a5a5) Some fix would be very much appreciated, I am available to help if I can. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1876279] [NEW] Xorg freeze
Public bug reported: I am the beginner with Linux and Ubuntu.And some Android habit that I can't give up . So I just try to classify my application with click on the button of "Show Application ", and drag all the LibreOffice application in one folder like Android does, but I find out that it usually frozen when I trying to leave the folder ,you may try click the folder and out frequently, and it frozen, the result is come from my experiment, I'm not sure I am the only person who encounter this problem. The situation was the screen stopped at "Show Application", but "spotify" still playing the song at the background. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 18:29:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0567] MachineType: Acer TravelMate 8481 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=44a3c145-e212-4d4e-b563-ad4206dfe924 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA41_HS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnAcer:bvrV2.06:bd10/28/2011:svnAcer:pnTravelMate8481:pvrV2.06:rvnAcer:rnBA41_HS:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.06: dmi.product.name: TravelMate 8481 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876279 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I am the beginner with Linux and Ubuntu.And some Android habit that I can't give up . So I just try to classify my application with click on the button of "Show Application ", and drag all the LibreOffice application in one folder like Android does, but I find out that it usually frozen when I trying to leave the folder ,you may try click the folder and out frequently, and it frozen, the result is come from my experiment, I'm not sure I am the only person who encounter this problem. The situation was the screen stopped at "Show Application", but "spotify" still playing the song at the background. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 18:29:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0567] MachineType: Acer TravelMate 8481 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=44a3c145-e212-4d4e-b563-ad4206dfe924 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA41_HS
[Touch-packages] [Bug 1876277] [NEW] Background image gets corrupted after login
Public bug reported: Problem: Small squares with random pixel colors appear on desktop background image. Additional info (forgive me if some of these are included in the bug details that was automatically uploaded): 1- My laptop has two graphic cards: Intel and NVIDIA and it's using Intel as the default card (It's written in the About page of the Settings) 2- I also have Windows on my laptop and it doesn't happen there. 3- Changing the background solves the issue but only until the next restart. Also, changing it back to the image that was corrupted returns the corrupted pixels exactly the way they were. They somehow get attached to that specific image. 4- I'm using Ubuntu 20.04. 5- Sometimes those squares appear in the login screen too. 6- I have attached a screenshot of the desktop (1.jpg in the zip file I've attached) 7- Another observation I've had is that right after I enter my password in the login page, the screen somehow "flashes" once and some lines appear on the screen (2.jpg in the zip file) What I've tried: 1- I tried changing the NVIDIA driver from xorg to NVIDIA's own driver (version 440) but no luck. 2- Tried "dconf reset -f /org/gnome/" and it didn't help. Workarounds I've found: Restarting Gnome using Alt+F2 and entering r will solve the problem but only until the next restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 14:36:55 2020 DistUpgraded: 2020-05-01 02:56:41,056 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:820d] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 960M] [103c:820d] InstallationDate: Installed on 2019-07-15 (290 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD Bus 001 Device 002: ID 046d:c058 Logitech, Inc. M115 Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9da90290-adcc-4ed3-9f63-fae1bb7364cd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820D dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820D:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: X1G64PA#AB4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: background gnome screen-corruption ** Attachment added: "screenshots.zip" https://bugs.launchpad.net/bugs/1876277/+attachment/5364334/+files/screenshots.zip ** Summary changed: - Background corrupted after login + Background image gets corrupted after login -- 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/1876277 Title: Background image gets corrupted after login Status in xorg package in Ubuntu: New Bug description: Problem: Small squares with random pixel colors appear on desktop background image. Additional info (forgive me if some of these are included in the bug details that was automatically uploaded): 1- My laptop has two graphic cards: Intel and NVIDIA and it's using Intel as the default card (It's written in the About page of the Settings) 2- I also have W
[Touch-packages] [Bug 1864313] Re: "Software and Updates" UI hang.
** Package changed: update-manager (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864313 Title: "Software and Updates" UI hang. Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 0.98.5 3) I clicked the Software and Updates icon, the Software and Updates window appears. If I start clicking on different tabs, the UI hangs. I think the hang is because the process is downloading data and my internet connection(64k) is slow. Could you fork the download process, so that the UI remains responsive? 4) Software and Updates window hanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1864313/+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 1864313] [NEW] "Software and Updates" UI hang.
You have been subscribed to a public bug: 1) Ubuntu 19.10 2) 0.98.5 3) I clicked the Software and Updates icon, the Software and Updates window appears. If I start clicking on different tabs, the UI hangs. I think the hang is because the process is downloading data and my internet connection(64k) is slow. Could you fork the download process, so that the UI remains responsive? 4) Software and Updates window hanged. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- "Software and Updates" UI hang. https://bugs.launchpad.net/bugs/1864313 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- 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 1876267] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1876267/+attachment/5364324/+files/ProcCpuinfoMinimal.txt -- 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/1876267 Title: Audio settings strange behaviour with ASUS STXII sound card Status in gnome-control-center package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-23 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-28-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/gnome-control-center/+bug/1876267/+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 1876267] Re: Audio settings strange behaviour with ASUS STXII sound card
apport information ** Description changed: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. + The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf + In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) - Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. - + Lfe slider should work. BR, Mathias ** Description changed: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. - Lfe slider should work. + Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias ** Tags added: apport-collected ** Description changed: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1
[Touch-packages] [Bug 1876143] Re: Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia-driver-390
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1876143 Title: Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia- driver-390 Status in gnome-online-accounts package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04 LTS today, and tried to add google and facebook account. Webkit crashes, and loading stops. When using open-source nvidia driver it works.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.28.2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 18:41:23 2020 InstallationDate: Installed on 2020-04-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1876143/+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 1876267] Re: Audio settings strange behaviour with ASUS STXII sound card
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1876267 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal ** Package changed: mutter (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1876267 Title: Audio settings strange behaviour with ASUS STXII sound card Status in gnome-control-center package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1876267] [NEW] Audio settings strange behaviour with ASUS STXII sound card
You have been subscribed to a public bug: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. BR, Mathias ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal -- Audio settings strange behaviour with ASUS STXII sound card https://bugs.launchpad.net/bugs/1876267 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- 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 1875017] Re: primary display size is wrong when 2nd display is rotated
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 Setting the orientation of my second monitor in `nvidia-settings` works correctly (panning and tracking are not enabled). Here's the output of `xrandr` after rotating my second monitor in `nvidia-settings`: Screen 0: minimum 8 x 8, current 5040 x 2160, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0030.0029.9723.98 1920x1080 60.0059.9450.0029.9723.98 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x768 59.87 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected 1200x1920+3840+0 left (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 59.88 1920x1080 60.0059.9450.0023.98 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) USB-C-0 disconnected (normal left inverted right x axis y axis) -- 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/1875017 Title: primary display size is wrong when 2nd display is rotated Status in xorg package in Ubuntu: New Bug description: I have 2 displays, primary on the left, 2nd on the right primary dell 30" LCD 2560 x 1600 secondary dell 20" LCD (rotated 1600 x 1200 Fractional scaling is NOT enabled In display settings, if I don't rotate the screen all is well when the 2nd display is rotated, the primary display "extends into the 2nd display, by about 1/3 Moving the mouse to the far right, causes the screen to scroll <--> so as to diaplay the reset of the 2nd screen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 22:53:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b] InstallationDate: Installed on 2020-04-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision T1700 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=c1eecc57-1357-4347-a0a6-cf3c563a52fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-d
[Touch-packages] [Bug 1875017] Re: primary display size is wrong when 2nd display is rotated
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 I agree with Chris: This current bug (#1875017) is not a duplicate of bug #1874567 :) Since updating from 19.10 to 20.20, I'm getting the same issue as Chris: I have two monitors, both connected to an Nvidia RTX-2080Ti: The primary monitor is landscape; the secondary monitor is rotated portrait right. When I set my second monitor to "Orientation = Portrait Right" in Settings, the rotation settings take effect, and the second monitor displays in the correct orientation. However, the error is that panning and tracking are now enabled (this is not the expected behaviour!) Here's a little video demonstrating the problem: https://photos.app.goo.gl/iGX7bKa3GQpF8ada6 Below, I'll show two outputs of `xrandr`: The first output is after the second monitor is rotated (note the 'panning' and 'tracking'). The second output is when the second monitor is set to landscape (and doesn't show panning or tracking). ## XRANDR AFTER SETTING ROTATION OF SECOND SCREEN TO PORTRAIT RIGHT Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+499+0 (normal left inverted right x axis y axis) 621mm x 341mm panning 4560x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 3840x2160 60.00*+ 59.9450.0030.0029.9723.98 1920x1080 60.0059.9450.0029.9723.98 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x768 59.87 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected 1200x1920+4339+0 left (normal left inverted right x axis y axis) 518mm x 324mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1200 59.95*+ 59.88 1920x1080 60.0059.9450.0023.98 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) USB-C-0 disconnected (normal left inverted right x axis y axis) ## XRANDR WHEN BOTH SCREENS ARE SET TO PORTRAIT ROTATION Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0030.0029.9723.98 1920x1080 60.0059.9450.0029.9723.98 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x800 59.81 1280x768 59.87 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 59.88 1920x1080 60.0059.9450.0023.98 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) USB-C-0 disconnected (normal left inverted right x axis y axis) -- 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/1875017 Title: primary display size is wrong when 2nd display is rotated Status in xorg package in Ubuntu: New Bug description: I have 2 displays, primary on the left, 2nd on the right primary dell 30" LCD 2560 x 1600 secondary dell 20" LCD (rotated 1600 x 1200 Fractional scaling is NOT enabled In display settings, if I don't rotate the screen all is well when the 2nd display is rotated, the primary display "extends into the 2nd