[Bug 2062982] [NEW] [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect
Public bug reported: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062982 Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2062982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714667] Re: please add old hungarian letters
Please don't use capital/small letters in center aligned form. It's good for city-tables, but not for documents and user intefaces. Align letters to bottom line! If the font developers can wait, we will offer two kind of "Old Hungarian" font. First is the https://github.com/rovasiras/kende We would like second implementation, with another typography. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714667 Title: please add old hungarian letters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/1714667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970743] Re: Gedit not changing themes when run as root in Ubuntu 22.04
Error is (gedit:41903): dconf-WARNING **: 13:59:25.721: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Can be fixed with dbus-x11 install sudo apt install dbus-x11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970743 Title: Gedit not changing themes when run as root in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1970743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965610] Re: Extra layouts don't work on Hungarian UI
** Attachment added: "Setting with terminal" https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965610/+attachment/5570660/+files/extra_layouts.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965610 Title: Extra layouts don't work on Hungarian UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965610] [NEW] Extra layouts don't work on Hungarian UI
Public bug reported: When I set into a terminal the following command: "sudo gsettings set org.gnome.desktop.input-sources show-all-sources true" it fails. We required for "Old Hungarian" layout, short description:"oldhun" -> "Székely-magyar rovásírás" and "Old Hungarian (for ligatures)" layout, short description: "oldhun(lig)" id:"oldhunlig" ->"Székely-magyar rovásírás (ligatúrákhoz)" ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965610 Title: Extra layouts don't work on Hungarian UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965609] Re: Not all Hunngarian keyboard layouts' name translated to Hungarian layout
** Attachment added: "List of keyboard layout 2nd part" https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965609/+attachment/5570659/+files/Hungarian_layouts2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965609 Title: Not all Hunngarian keyboard layouts' name translated to Hungarian layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965609] [NEW] Not all Hunngarian keyboard layouts' name translated to Hungarian layout
Public bug reported: Wen I wanted to choose a Hungarian layout, I saw, that not all Hungarian layouts' name translated into Hungarian language. ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Layouts 1st section" https://bugs.launchpad.net/bugs/1965609/+attachment/5570658/+files/Hungarian_layouts1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965609 Title: Not all Hunngarian keyboard layouts' name translated to Hungarian layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1965609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961434] [NEW] package linux-image-5.4.0-100-generic 5.4.0-100.113 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: On installation from removable media, after partitioning, suppose not enough free space on /boot partition (was 100 MB), now set to 150 MB. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-100-generic 5.4.0-100.113 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sando 1427 F pulseaudio CasperMD5CheckResult: skip Date: Fri Feb 18 09:21:38 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-17 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IwConfig: enp3s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 003: ID 248a:8367 Maxxter Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. PLAISIOCOMPUTERS ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-100-generic root=UUID=d54c4bb4-5d59-4a1a-91b8-15fa177ba083 ro efi=runtime PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-100-generic 5.4.0-100.113 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A48PGP02 dmi.board.name: H67M-S/H67M-V/H67 dmi.board.vendor: Foxconn dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA48PGP02:bd02/24/2011:svnTobefilledbyO.E.M.:pnPLAISIOCOMPUTERS:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH67M-S/H67M-V/H67:rvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: PLAISIOCOMPUTERS 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. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961434 Title: package linux-image-5.4.0-100-generic 5.4.0-100.113 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1961434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
Upgrading to BIOS 1.13.3 on Latitude 3520 seems to have solved the issue. Thanks for the help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
The difference between your and my setup is that I do not use a docking station. Maybe worth a try if this also happens without it. Upstream bug has been reported here: https://github.com/systemd/systemd/issues/21751 Also, I have a BIOS update that just came out so will install it right now and let you know if that helped. ** Bug watch added: github.com/systemd/systemd/issues #21751 https://github.com/systemd/systemd/issues/21751 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
I experience the same issue on a Dell Latitude 3520. It is Manjaro and systemd version is 249 but the issue/solution is exactly the same. Did you find any permanent solution to the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954564] Re: "linux-modules-extra" module missing in pc-kernel snap for 20/track
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954564 Title: "linux-modules-extra" module missing in pc-kernel snap for 20/track To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954564] Re: "linux-modules-extra" module missing in pc-kernel snap for 20/track
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954564 Title: "linux-modules-extra" module missing in pc-kernel snap for 20/track To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954564] [NEW] "linux-modules-extra" module missing in pc-kernel snap for 20/track
Public bug reported: See details here: https://forum.snapcraft.io/t/enable-kernel-module-for-rtw-8821/27812/6 tl;dr is that the linux-modules-extra module is missing, which is causing WiFi not to work on many amd64 based boards. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954564 Title: "linux-modules-extra" module missing in pc-kernel snap for 20/track To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947697] Re: no longer works after upgrade to 21.10 (raspberry pi 4)
@Sam Lane Thank you so much! Now it works great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947697 Title: no longer works after upgrade to 21.10 (raspberry pi 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1947697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947697] Re: no longer works after upgrade to 21.10 (raspberry pi 4)
The zram module is needed. With installed "linux-modules-extra-raspi" it's working fine. ** Changed in: zram-config (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947697 Title: no longer works after upgrade to 21.10 (raspberry pi 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1947697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
I think 8th november. (Link: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/comments/46 ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948910] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1948910/+attachment/5536763/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948910 Title: Old Hungarian letters appears as tofu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/1948910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948910] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1948910/+attachment/5536764/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948910 Title: Old Hungarian letters appears as tofu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/1948910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948910] Re: Old Hungarian letters appears as tofu.
apport information ** Tags added: apport-collected focal ** Description changed: Old Hungarian letters appears as tofus. One of the Old Hungarian font checked. Old Hungarian "language" is not implemented: ISO code is ohu-Hung-HU. Old Hungarian script is a Right to left script. Unicode range downloadable from https://unicode.org/charts/PDF/U10C80.pdf U+10C80-U+10CB2 range is capital letters' range. U+10CC0-U+10CF2 range is small letters' range. U+10CFA-U+10CFF range is the Old Hungarian numbers' range. You can test with Old Hungarian keyboard layout of xkeyboard-config project, (Is it in the extras, must be check as not frequently used layouts) or Old Hungarian keyboard layout from https://keyman.com/ project page, which is a multiplatform implementation of the Old Hungarian keyboard layout. You need to add to the scribus an implemented Old Hungarian font into fonts repo, if it is possible. One of the Old Hungarian public font implementation is downloadable from github.com project page from kende-font/kende-font repository, or its FontForge's source from github.com from kende-font/kende-source repository. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-06-03 (511 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: nvidia_modeset nvidia + Package: scribus 1.5.5+dfsg-6build1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 + Tags: focal + Uname: Linux 5.11.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1948910/+attachment/5536762/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948910 Title: Old Hungarian letters appears as tofu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/1948910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
5.13.0.1009.15 unfortunately does not improve the problem. (fresh installed ubuntu 21.10 desktop and rpi4 4gb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948910] [NEW] Old Hungarian letters appears as tofu.
Public bug reported: Old Hungarian letters appears as tofus. One of the Old Hungarian font checked. Old Hungarian "language" is not implemented: ISO code is ohu-Hung-HU. Old Hungarian script is a Right to left script. Unicode range downloadable from https://unicode.org/charts/PDF/U10C80.pdf U+10C80-U+10CB2 range is capital letters' range. U+10CC0-U+10CF2 range is small letters' range. U+10CFA-U+10CFF range is the Old Hungarian numbers' range. You can test with Old Hungarian keyboard layout of xkeyboard-config project, (Is it in the extras, must be check as not frequently used layouts) or Old Hungarian keyboard layout from https://keyman.com/ project page, which is a multiplatform implementation of the Old Hungarian keyboard layout. You need to add to the scribus an implemented Old Hungarian font into fonts repo, if it is possible. One of the Old Hungarian public font implementation is downloadable from github.com project page from kende-font/kende-font repository, or its FontForge's source from github.com from kende-font/kende-source repository. ** Affects: scribus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948910 Title: Old Hungarian letters appears as tofu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/1948910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947697] Re: no longer works after upgrade to 21.10 (raspberry pi 4)
I have downgraded to the last ubuntu 21.04 kernel (5.11.0-1021-raspi) and zram-config is now working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947697 Title: no longer works after upgrade to 21.10 (raspberry pi 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1947697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947697] Re: no longer works after upgrade to 21.10 (raspberry pi 4)
Hello, thank you very much for your answer. Unfortunately, the new version also does not enable zram. At the moment there are several kernel problems (rpi on 21.10). Maybe I should wait until the 8th of november. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947697 Title: no longer works after upgrade to 21.10 (raspberry pi 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1947697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947697] [NEW] no longer works after upgrade to 21.10 (raspberry pi 4)
Public bug reported: Package: zram-config (0.6) DistroRelease: Ubuntu 21.10 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 --- I already had zram-config installed on ubuntu 21.04. After upgrading to ubuntu 21.10 the systemd service only gives the message "FAILURE". I have already tried to reinstall zram-config but no change. (I would also like to provide more infos/logs, but I am not sure what is correct.) ** Affects: zram-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947697 Title: no longer works after upgrade to 21.10 (raspberry pi 4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1947697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Re: Thunderbolt docking station drops USB
Just to keep this alive, I'm running 5.13.1 and so far it seems to be working. I only used it for ~8 hours and so far I have not seen any Transfer event errors, nor any USB reset (I see a lot of other new errors, it even failed to boot with 5.13.1 at first, but those are irrelevant regarding this issue). I don't know if its going to be stable on the long term or not, as even with the 5.8 kernel it sometimes managed to work for 3+ days non stop without any issues (but most of the time crashed after 5-30 minutes). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
Well, there are patches for this module, it's even linked to this issue: 0.10.15. That version does not introduce any additional dependencies. Is there a reason why this package has to be on the latest release and why version 0.10.15 can't be used? Sadly I can't use older releases, as ~2 year old hardware (and some 5+) is too new to be supported by older releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893753] Re: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17
Hm, interesting fix. Will this mean that all buggy modules will get removed too in the future? Is there any chance for Anton Tolchanov's change to be merged (or re-created to verify its trustworthy then compared)? Removal of this package caused me a day of headache. Upgrading it to a newer but not the newest version is better in my opinion than completely removing it. Also, it was not totally broken, for some use cases it worked fine (my simple use case worked flawlessly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893753 Title: libnginx-mod-http-lua 0.10.11 not compatible with NGINX 1.18/1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1893753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Re: Thunderbolt docking station drops USB
I tested with https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.12/amd64/ for a few (5-6) hours (sorry I don't use desktop linux much at all now days), dmesg is still full of errors like these: [ 2852.594018] xhci_hcd :3c:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [ 2852.594051] xhci_hcd :3c:00.0: Looking for event-dma 0001ed2ad1d0 trb-start 0001ed2ad1e0 trb-end 0001ed2ad1e0 seg-start 0001ed2ad000 seg-end 0001ed2adff0 [ 2854.671891] usb 5-2.4.1: reset full-speed USB device number 8 using xhci_hcd So far it did not drop the usb controller, so that's good. 5-2.4.1 is a wireless receiver for my mouse, if I plug it in directly to the machine it does not throw this error, but in the dock this message occurs every few minutes. It was plugged into the same physical port when I used the previous kernel and this error message did not occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Re: Thunderbolt docking station drops USB
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485290/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485289/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485288/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485287/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485286/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485285/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485284/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485283/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485282/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485281/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485280/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485279/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485278/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485276/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485277/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485275/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485274/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485272/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485273/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485271/+files/Card0.Codecs.codec.2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485270/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] Re: Thunderbolt docking station drops USB
apport information ** Tags added: apport-collected ** Description changed: My Lenovo Thunderbolt Dock Gen2 randomly drops the USB controller, resulting in no USB at all. It sometimes happens after a few seconds of being plugged in to the notebook, but sometimes it works for hours. The display connected to the dock stays active and working. I tried to blacklist the driver (r8152) for the usb3-ethernet controller, as suggested in a few forums, but it does not solve the issue. dmesg is full of the following messages: [ 1001.028336] xhci_hcd :08:00.0: WARN Event TRB for slot 11 ep 1 with no TDs queued? [ 1001.029304] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [ 1001.029324] xhci_hcd :08:00.0: Looking for event-dma 00087785b460 trb-start 00087785b540 trb-end 00087785b540 seg-start 00087785b000 seg-end 00087785bff0 I'm running ubuntu 20.10, but it also happened under 20.04. Everything is up to date as of writing this bugreport. The dock is running the latest firmware, but the issue was present with earlier version of the firmware too. I also tried both thunderbolt ports on the notebook (MSI Prestige 15), the issue happens on both. The dock works flawlessly under windows 10. + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-48-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: viktor 1021 F pulseaudio + /dev/snd/controlC0: viktor 1021 F pulseaudio + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-06-05 (306 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-48-generic N/A + linux-backports-modules-5.8.0-48-generic N/A + linux-firmware1.190.3 + Tags: groovy + Uname: Linux 5.8.0-48-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/18/2019 + dmi.bios.release: 1.8 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: E16S3IMS.108 + dmi.board.asset.tag: Default string + dmi.board.name: MS-16S3 + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: REV:1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: + dmi.product.family: Prestige + dmi.product.name: Prestige 15 A10SC + dmi.product.sku: 16S3.1 + dmi.product.version: REV:1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485268/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1921643/+attachment/5485269/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921643] [NEW] Thunderbolt docking station drops USB
Public bug reported: My Lenovo Thunderbolt Dock Gen2 randomly drops the USB controller, resulting in no USB at all. It sometimes happens after a few seconds of being plugged in to the notebook, but sometimes it works for hours. The display connected to the dock stays active and working. I tried to blacklist the driver (r8152) for the usb3-ethernet controller, as suggested in a few forums, but it does not solve the issue. dmesg is full of the following messages: [ 1001.028336] xhci_hcd :08:00.0: WARN Event TRB for slot 11 ep 1 with no TDs queued? [ 1001.029304] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [ 1001.029324] xhci_hcd :08:00.0: Looking for event-dma 00087785b460 trb-start 00087785b540 trb-end 00087785b540 seg-start 00087785b000 seg-end 00087785bff0 I'm running ubuntu 20.10, but it also happened under 20.04. Everything is up to date as of writing this bugreport. The dock is running the latest firmware, but the issue was present with earlier version of the firmware too. I also tried both thunderbolt ports on the notebook (MSI Prestige 15), the issue happens on both. The dock works flawlessly under windows 10. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921643 Title: Thunderbolt docking station drops USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1921643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878020] Re: thunderbolt combined with ethernet does not work
*** This bug is a duplicate of bug 1749961 *** https://bugs.launchpad.net/bugs/1749961 This also happens with a Lenovo Thunderbolt Dock Gen 2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878020 Title: thunderbolt combined with ethernet does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909695] [NEW] Software application hasn't been installed
Public bug reported: I installed Ubuntu LTS with mini.iso. After choosing ubuntu-desktop in task selection gnome-software was not installed. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909695 Title: Software application hasn't been installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1909695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
@Juerg - Do you have a timeline for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
no, wait, that is a different error message. When I run unprivileged, I get Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered. Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease At least one invalid signature was encountered. Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease At least one invalid signature was encountered. Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease At least one invalid signature was encountered. Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
I have verified that the date is indeed the problem. When I run an ubuntu container privileged, the container has the correct date and apt update succeeds. But when I run the container privileged and set the date to 1971, then I get that same error message from apt update. Therefore, this bug is a duplicate of bug #1896443 pi@raspberrypi:~ $ docker run --privileged -it ubuntu bash root@ad897025c4b7:/# date "+%Y-%m-%d %H:%M:%S" -s "1971-01-01 00:00:00" 1971-01-01 00:00:00 root@ad897025c4b7:/# apt update Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [111 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [98.3 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [107 kB] Reading package lists... Done E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal/InRelease is not valid yet (invalid for another 18010d 17h 33min 0s). Updates for this repository will not be applied. E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal-updates/InRelease is not valid yet (invalid for another 18222d 10h 50min 54s). Updates for this repository will not be applied. E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal-backports/InRelease is not valid yet (invalid for another 18222d 10h 51min 16s). Updates for this repository will not be applied. E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal-security/InRelease is not valid yet (invalid for another 18222d 10h 50min 42s). Updates for this repository will not be applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
So now I manually downloaded libseccomp2_2.5.0-3_armhf.deb, copied it into the container and tried to install it from there. This didn't work either: Step 7/27 : RUN dpkg --force-all -P libseccomp2 ---> Running in bf8c3eba1b94 dpkg: libseccomp2:armhf: dependency problems, but removing anyway as you requested: apt depends on libseccomp2 (>= 2.4.2). (Reading database ... 4115 files and directories currently installed.) Removing libseccomp2:armhf (2.4.3-1ubuntu3.20.04.3) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Removing intermediate container bf8c3eba1b94 ---> 46d72c3e2384 Step 8/27 : RUN dpkg -i /libseccomp2_2.5.0-3_armhf.deb ---> Running in 2636514aa37f tar: ./control: Cannot utime: Operation not permitted tar: ./md5sums: Cannot utime: Operation not permitted tar: ./shlibs: Cannot utime: Operation not permitted tar: ./symbols: Cannot utime: Operation not permitted tar: ./triggers: Cannot utime: Operation not permitted tar: .: Cannot utime: Operation not permitted tar: Exiting with failure status due to previous errors dpkg-deb: error: tar subprocess returned error exit status 2 dpkg: error processing archive /libseccomp2_2.5.0-3_armhf.deb (--install): dpkg-deb --control subprocess returned error exit status 2 Errors were encountered while processing: /libseccomp2_2.5.0-3_armhf.deb The command '/bin/sh -c dpkg -i /libseccomp2_2.5.0-3_armhf.deb' returned a non-zero code: 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
I have also tried this on ubuntu:20.10, ubuntu:20.04 and ubuntu:18.04 and it produces the same error there, too. I think it is an issue with the system clock reporting Jan 1st 1970. The system clock on the host system is correct though. I could only find two ways to change the system clock in the ubuntu docker image: "date -s" requires --privileged (which isn't available in docker build) hwclock, which doesn't work on raspberry pi: root@8f7355a71bca:/# hwclock --verbose hwclock from util-linux 2.34 System Time: 0.-1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. other means like ntp don't work because they aren't preinstalled and cannot be installed because apt-get doesn't work (which is the topic of this bugreport) I was also not able to update libseccomp2, because wget and curl aren't preinstalled and cannot be installed either, because apt-get doesn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895142] Re: Toshiba Satellite A300 restarts after waking from suspend mode
I tested this bug with the Linux kernel version 4.15.0-112-generic (i686) that I thought was OK. It is not. My computer has problems with resuming from the suspend mode and the behaviour is not always the same. As I used the 112 version for longer time before and nothing happened, it seems to me that now it is some hardware error as my Toshiba is quite old. I apologize for disturbing. Please, close this bug as not relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895142 Title: Toshiba Satellite A300 restarts after waking from suspend mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895142] [NEW] Toshiba Satellite A300 restarts after waking from suspend mode
Public bug reported:
I suspend the laptop either by closing the lid or by GUI clicking on Suspend
option (Pohotovostný režim in Slovak).
I resume from suspend either by opening the lid or by pressing the power button.
In either case the PC resumes for about a second then power goes off (I hear
the hard disk going off) and the system restarts. Then it is OK.
I think that the problem started after updating the kernel to version Linux
4.15.0-115-generic (i686). Now I use the version 4.15.0-117-generic (i686).
I have never faced this problem before and I run Lubuntu on this PC for more
than year.
I cannot provide information required by Ubuntu Wiki in section
DebuggingKernelSuspend as I have not installed the nondaily mainline kernel.
Issuing the command "sudo cat /sys/kernel/debug/suspend_stats" I obtained the
following output:
viktor@Toshiba:~$ sudo cat /sys/kernel/debug/suspend_stats
[sudo] heslo pre používateľa viktor:
success: 0
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
last_failed_dev:
last_failed_errno:0
0
last_failed_step:
viktor@Toshiba:~$
That's all so far.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-117-generic.
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0c: viktor 966 F...m pulseaudio
/dev/snd/pcmC0D0p: viktor 966 F...m pulseaudio
/dev/snd/controlC0: viktor 966 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd470 irq 25'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1179ff1e,0013
HDA:11c11040,11790001,00100200'
Controls : 28
Simple ctrls : 12
CurrentDesktop: LXDE
Date: Thu Sep 10 14:19:52 2020
MachineType: TOSHIBA Satellite A300
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=UUID=3c3d339c-33ce-486d-b55e-4fe4154e7815 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.60:bd10/14/2008:svnTOSHIBA:pnSatelliteA300:pvrPSAG8E-01L00JSK:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: Satellite A300
dmi.product.version: PSAG8E-01L00JSK
dmi.sys.vendor: TOSHIBA
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: apport-bug bionic i386
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895142
Title:
Toshiba Satellite A300 restarts after waking from suspend mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895142/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891356] [NEW] ?
Public bug reported: ? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 12 19:05:41 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=ru_RU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891356 Title: ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Having the same or at least similar issue on a DELL XPS13 (9360) D600 Dock. The thunderbolt connection suddenly drops for a few seconds and the automatically reconnects again. Screens go blank for that time and all peripherals also gets disconnected. This happens randomly but at least twice an hour. All firmware is up-to-date. OS: Ubuntu 20.04 LTS (5.4.0-40-generic) Hardware: DELL XPS 13 (9360); Intel Core i7-7500U CPU, 8GB RAM Dock: DELL D600 (with two 1080p monitors connected over DisplayPort) Here the dmesg: [ 4088.809311] show_signal_msg: 3032 callbacks suppressed [ 4088.809314] ActiveCommandQu[6618]: segfault at 7f244c19f000 ip 00998e9e sp 7f244e7fa438 error 4 in DisplayLinkManager[40+937000] [ 4088.809321] Code: 3d db fb c4 c1 3d 72 d0 08 c4 e3 fd 00 d7 d8 c5 bd db fb c5 6d f9 d8 c5 ed fd d0 c5 ed fd d0 c5 ed fd c9 c5 fd 6f 17 4c 01 cf 7d 6f 17 c5 f5 71 d1 02 c5 ed db c3 c5 ed 72 d2 08 c5 7d 6f 24 [ 4093.927731] evdi: [D] evdi_driver_postclose:133 (dev=2) Process tries to close us, postclose [ 4093.927733] evdi: [I] Task 1148 (DesktopManagerE) of process 1139 (DisplayLinkMana) [ 4093.927736] evdi: [D] evdi_painter_disconnect:817 (dev=2) Disconnected from 9024a4f0 [ 4093.927739] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4093.927788] evdi: [D] evdi_driver_postclose:133 (dev=1) Process tries to close us, postclose [ 4093.927789] evdi: [I] Task 1148 (DesktopManagerE) of process 1139 (DisplayLinkMana) [ 4093.927791] evdi: [D] evdi_painter_disconnect:817 (dev=1) Disconnected from a19585cf [ 4093.927792] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.278010] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.278026] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.278039] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.278048] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.278058] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.278064] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.278072] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.278078] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.278514] evdi: [D] evdi_painter_dpms_notify:654 (dev=-1) Notifying dpms mode: 3 [ 4094.278515] evdi: [W] evdi_painter_send_event:307 Painter is not connected! [ 4094.597176] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.597190] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.597202] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.597210] evdi: [D] evdi_detect:94 (dev=-1) poll connector state: disconnected [ 4094.597220] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.597227] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.597237] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.597245] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected [ 4094.761411] evdi: [D] evdi_painter_dpms_notify:654 (dev=-1) Notifying dpms mode: 3 [ 4094.761413] evdi: [W] evdi_painter_send_event:307 Painter is not connected! [ 4095.603371] evdi: [D] evdi_painter_dpms_notify:654 (dev=0) Notifying dpms mode: 3 [ 4095.603373] evdi: [W] evdi_painter_send_event:307 Painter is not connected! [ 4095.603384] evdi: [D] evdi_painter_dpms_notify:654 (dev=0) Notifying dpms mode: 3 [ 4095.603385] evdi: [W] evdi_painter_send_event:307 Painter is not connected! [ 4095.603397] evdi: [D] evdi_painter_dpms_notify:654 (dev=-1) Notifying dpms mode: 3 [ 4095.603398] evdi: [W] evdi_painter_send_event:307 Painter is not connected! [ 4095.603478] evdi: [D] evdi_painter_dpms_notify:654 (dev=-1) Notifying dpms mode: 3 [ 4095.603479] evdi: [W] evdi_painter_send_event:307 Painter is not connected! [ 4099.415992] evdi: [D] evdi_painter_connect:738 (dev=-1) Process is trying to connect [ 4099.415994] evdi: [I] Task 6702 (DesktopManagerE) of process 6696 (DisplayLinkMana) [ 4099.415997] evdi: [D] evdi_painter_connect:788 (dev=1) Connected with e47f4312 [ 4099.416000] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [ 4099.423785] evdi: [D] evdi_painter_connect:738 (dev=-1) Process is trying to connect [ 4099.423787] evdi: [I] Task 6702 (DesktopManagerE) of process 6696 (DisplayLinkMana) [ 4099.423790] evdi: [D] evdi_painter_connect:788 (dev=2) Connected with 040a913a [ 4099.423792] evdi: [D] evdi_detect:90 (dev=2) poll connector state: connected [ 4099.430545] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [ 4099.430547] evdi: [D] evdi_painter_get_edid_copy:228 (dev=1) EDID valid [ 4099.430701] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [ 4099.430702] evdi: [D]
[Bug 1885419] [NEW] QEMU crash using virtio-scsi with iothread
Public bug reported: After a recent upgrade I can't start a Windows 10 VM anymore, QEMU crashes with the error message: error: Failed to start domain win10 error: internal error: qemu unexpectedly closed the monitor: qemu-system-x86_64: /build/qemu-v_zvmu/qemu-2.11+dfsg/util/aio-posix.c:592: aio_poll: Assertion `in_aio_context_home_thread(ctx)' failed. I was able to resurrect the VM by removing the iothread-related elements from the domain definition: ... 1 ... ... The domain XML is attached. I'm using virtio-scsi and not virtio-blk because I use trimming to keep my QCOW image small(er). Would be great if I could continue to use this with iothreads enabled. $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 $ apt-cache policy qemu-kvm qemu-kvm: Installiert: 1:2.11+dfsg-1ubuntu7.27 Installationskandidat: 1:2.11+dfsg-1ubuntu7.27 Versionstabelle: *** 1:2.11+dfsg-1ubuntu7.27 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.26 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qemu-kvm 1:2.11+dfsg-1ubuntu7.27 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 13:05:17 2020 InstallationDate: Installed on 2019-10-03 (268 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-108-generic root=UUID=d40a86d5-61ae-486e-8ddf-9581c538d64e ro quiet splash vt.handoff=1 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: Z68 Pro3 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.:bvrP1.60:bd07/13/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Pro3: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.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Domain XML causing failure." https://bugs.launchpad.net/bugs/1885419/+attachment/5387838/+files/win10.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885419 Title: QEMU crash using virtio-scsi with iothread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1885419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883489] Re: Logrotate failed to start in LUbuntu 20.04
This problem is related to MYSQL. The privileges of 'debian-sys-maint' user are too scanty. The workaround is found at http://hobbymods.ru/article/linux/osibka-error-running-shared-postrotate-script-for-varlogmysqllog-varlogmysqlmysq with some changes due to the modern syntax: 1. Get the password for user 'debian-sys-maint': sudo grep -m 1 password /etc/mysql/debian.cnf | cut -d" " -f3 The password should be displayed. Copy it 2. Configure MySQL: sudo mysql --user=root mysql 2.1. In MYSQL environment set the propper password ALTER USER 'debian-sys-maint'@'localhost' IDENTIFIED BY 'Paste the copied password'; flush privileges; 2.2. Reconfigure the user privileges: GRANT RELOAD, SHUTDOWN, PROCESS, SHOW DATABASES, SUPER, LOCK TABLES ON *.* TO 'debian-sys-maint'@'localhost'; flush privileges; exit 3. Test the operation. Should be OK (no output) sudo logrotate -f /etc/logrotate.conf I did not check, is the password proper by default (now it is impossible). If yes, only steps 2.2 and 3 are necessary. It can be tested only before step 2.1. If the settings for 'debian-sys-maint' are secure, they should be set by default at the installation of (L/K/X)Ubunutu 20.04. If the settings are vulnerable, another solution should be found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883489 Title: Logrotate failed to start in LUbuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883489] Re: Logrotate failed to start in LUbuntu 20.04
After some weeks, logrotate failed with different error caused by MYSQL: ● logrotate.service - Rotate log files Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-06-24 08:29:59 EEST; 44s ago TriggeredBy: ● logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) Process: *** ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE) Main PID: *** (code=exited, status=1/FAILURE) Jun 24 08:29:56 systemd[*]: Starting Rotate log files... Jun 24 08:29:59 logrotate[***]: error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/*log ' Jun 24 08:29:59 systemd[*]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Jun 24 08:29:59 systemd[*]: logrotate.service: Failed with result 'exit-code'. Jun 24 08:29:59 systemd[*]: Failed to start Rotate log files. (Hostname and PIDs are replaced by *) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883489 Title: Logrotate failed to start in LUbuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1883489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884082] [NEW] package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Popped up just like dat. Had boot problems just befo dat du 2 2 less space. Keep up da gud work. Peace! Ps: sry fo ma dumb langauge. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cellardoor 1500 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 17 12:16:57 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: LENOVO 4243W4K ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2115cb1b-ab29-42d1-8560-2ded1bfc06c3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET65WW (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243W4K dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn4243W4K:pvrThinkPadT520:rvnLENOVO:rn4243W4K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243W4K dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884082 Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883489] [NEW] Logrotate failed to start in LUbuntu 20.04
Public bug reported: After fresh installation of LUbuntu 20.04, when I switched off Plymouth, failure of logrotate appeared on the screen during boot. (PIDs are replaced by ***) :~$ systemctl status logrotate ● logrotate.service - Rotate log files Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-06-15 07:56:59 EEST; 32s ago TriggeredBy: ● logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) Process: *** ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE) Main PID: *** (code=exited, status=1/FAILURE) Jun 15 07:56:55 systemd[***]: Starting Rotate log files... Jun 15 07:56:59 logrotate[***]: error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/*log ' Jun 15 07:56:59 systemd[***]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Jun 15 07:56:59 systemd[***]: logrotate.service: Failed with result 'exit-code'. Jun 15 07:56:59 systemd[***]: Failed to start Rotate log files. I compared /etc/logrotate.d/samba with the information at https://salsa.debian.org/samba-team/samba/commit/bed29aba47558252eacfe9453d23cc1ab29770aa Two different lines have been found: In /etc/logrotate.d/samba: line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] || /usr/bin/smbcontrol smbd reload-config line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config at https://... line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config There is a same difference: in LUbuntu 20.04 .pid files are searched in /run/samba/, but at https://... they are searched in /var/run/samba/. After boot, both are present and have the same PIDs. :~$ cat /var/run/samba/nmbd.pid abcd :~$ cat /run/samba/nmbd.pid abcd :~$ cat /var/run/samba/smbd.pid efgh :~$ cat /run/samba/smbd.pid efgh (digits are replaced by letters for security reasons) Changing the folders according to https://... and reboot solve the problem: :~$ systemctl status logrotate ● logrotate.service - Rotate log files Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) After that, I tried to revert the changes and reboot. The bug cannot be reproduced anymore. Additional information: :~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 :~$ apt-cache policy logrotate logrotate: Installed: 3.14.0-4ubuntu3 Candidate: 3.14.0-4ubuntu3 Version Table: *** 3.14.0-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Finally, the solution for me is: sudo /etc/logrotate.d/samba Replace the following line (for me, line 6) [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] || /usr/bin/smbcontrol smbd reload-config by [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config and the following line (for me, line 18) [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config by [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config Save and reboot. But there are two question. Is it necessary to check both .pid files (both are present after boot), if yes, what operator should be used, || or && ? Is it necessary to correct line 32: "elif [ -f /run/samba/samba.pid ]; then"? I did not correct it. Because of a short time after installation, it is not tested, are the log files rotated or not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: logrotate 3.14.0-4ubuntu3 Uname: Linux 5.6.0-18.1-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Jun 15 08:43:08 2020 InstallationDate: Installed on 2020-05-30 (15 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal logrotate ** Patch added: "The corrected file in /etc/logrotate.d" https://bugs.launchpad.net/bugs/1883489/+attachment/5383897/+files/samba -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883489 Title: Logrotate failed to start in LUbuntu 20.04 To manage notifications about this bug go to:
[Bug 1883489] Re: Logrotate failed to start in LUbuntu 20.04
** Attachment added: "Original file "samba" in /etc/logrotate.d" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1883489/+attachment/5383901/+files/samba -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883489 Title: Logrotate failed to start in LUbuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1883489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850439] Re: No sound on ASUS UX534FT
I've tested those commands. Before run it, I installed alsa-tools: sudo apt install alsa-tools then I run these commands: sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 Awesome, the sound is working good now on UX533FTC and Ubuntu 20.04 LTS! It does not work after rebooting. So, I created bash script and run it on startup. 1) Create a bash script: nano fix_sound.sh #!/bin/bash hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 2) Change the permission of the script you saved sudo chmod 774 fix_sound.sh 3) Add it to startup sudo crontab -e 4) Then add this to your crontab: @reboot /path/to/fix_sound.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881543] [NEW] Wrong translation of the word "Volume" in Ukrainian
Public bug reported:
Dear All!
In the Options or Parameters ("Параметри") dialog there is an item
"Volume". In this context, it means "Volume on a drive". It should be
translated as "Розділ" in Ukrainian. But in the Ukrainian localization
it has been translated as "Гучність", which means "Volume of sound" or
"Loudness"
Please correct the translation in this context as "Розділ".
With beast regards.
Viktor.
** Affects: pcmanfm-qt (Ubuntu)
Importance: Undecided
Status: New
** Tags: translation volume
** Attachment added: "Options.png"
https://bugs.launchpad.net/bugs/1881543/+attachment/5379232/+files/Options.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881543
Title:
Wrong translation of the word "Volume" in Ukrainian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1881543/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873669] [NEW] Activities menu in not opened when "super" button is clicked (keyboard language should be different from EN)
Public bug reported: Steps 1) Switch language(keyboard) to Ukrainian or Russian 2) Click "super" button Expected Result Activities menu is opened Actual Result Nothing happens System Ubuntu 20.04 LTS (fresh installed beta) Gnome 3.36.1 Notes With English keyboard everything works as expected On Ubuntu 18.04 worked just fine ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873669 Title: Activities menu in not opened when "super" button is clicked (keyboard language should be different from EN) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850439] Re: No sound on ASUS UX534FT
I have the same problem. I tried to use different kernel and latest one 5.6.4, but there is no sound. Is there any chance to provide me a workaround for this? Asus ZenBook 15 UX534FTC-AA074T Ubuntu 18.04.4 LTS kernel 5.3.0-46-generic. hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.9G5mT1GK4nF SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x02c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1a61 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable) Memory Range: 0xc410-0xc41f (rw,non-prefetchable) IRQ: 148 (876 events) Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: sof_pci_dev is active Driver Activation Cmd: "modprobe sof_pci_dev" Config Status: cfg=new, avail=yes, need=no, active=unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same for me. inxi -SCGxxxz System:Host: viktorz Kernel: 5.3.0-46-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: Gnome 3.28.4 (Gtk 3.22.30-1ubuntu4) info: gnome-shell dm: gdm3 Distro: Ubuntu 18.04.4 LTS CPU: Quad core Intel Core i5-9400H (-MT-MCP-) arch: Skylake rev.13 cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 1 clock speeds: min/max: 800/4300 MHz 1: 900 MHz 2: 900 MHz 3: 900 MHz 4: 900 MHz 5: 900 MHz 6: 900 MHz 7: 900 MHz 8: 900 MHz Graphics: Card: Intel Device 3e9b bus-ID: 00:02.0 chip-ID: 8086:3e9b Display Server: x11 (X.Org 1.20.5 ) driver: i915 Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes syslog: Apr 10 14:56:25 viktorz kernel: [18006.588904] i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871694] [NEW] No Locale files
Public bug reported: There are no translation files in the new version. The old version has translation files. In version for Ubuntu 18.04 no locale files. In Ubuntu 16.06 locale files exists. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871694 Title: No Locale files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1871694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835546] Re: [20.04 FEAT] Base KVM setup for secure guests - qemu part
The QEMU review is still ongoing. As a stop-gap measure it would be great to have PPA with a preliminary build of QEMU (master level + patches). Attached is a full diff on top of 4.2. Since the attached patch obsoletes some of the debian/patches content, the following series file should suffice: pv-full.diff qboot-stop-using-inttypes.patch qboot-no-jump-tables.diff # ubuntu patches ubuntu/expose-vmx_qemu64cpu.patch ubuntu/enable-svm-by-default.patch ubuntu/define-ubuntu-machine-types.patch ubuntu/pre-bionic-256k-ipxe-efi-roms.patch ubuntu/lp-1857033-i386-Add-new-CPU-model-Cooperlake.patch It will be necessary to tweak the machine type and the CPU model patch. Further, I had to apply this change to debian/rules: --- orig/debian/rules 2020-02-12 09:21:56.0 -0500 +++ pv/debian/rules 2020-03-09 06:54:19.0 -0400 @@ -103,6 +101,9 @@ b/configure-stamp: configure dh_testdir + # Fix up permission + chmod +x scripts/kernel-doc + # system build rm -rf b/qemu; mkdir -p b/qemu cd b/qemu && \ ** Attachment added: "Full diff, needs to go to debian/patches" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1835546/+attachment/5335786/+files/pv-full.diff.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835546 Title: [20.04 FEAT] Base KVM setup for secure guests - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
Thank you Gunnar Hjalmarsson! I tested this package on bionic, and it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840699] [NEW] Caps-lock doesn't work correctly in Old Hungarian layout
Public bug reported: Xkeyboard-config's version 2.27 resolves this problem ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: xkb-data -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1840699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655260] Висш Съдебен Съвет: Бойко Атанасов - граждански кандидат за главен прокурор на България
Hallo, ich habe gerade die Petition „Висш Съдебен Съвет: Бойко Атанасов - граждански кандидат за главен прокурор на България" unterschrieben und wollte dich fragen, ob du auch mitmachst. Unser Ziel ist es, 2.500 Unterschriften zu sammeln und dafür brauchen wir Unterstützung. Hier kannst du mehr über die Petition erfahren: http://chng.it/G9RB8vcMN6 Vielen Dank! Viktor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655260 Title: Kernel freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820604] Re: curtin fails to find itself in subiquity snap, when running on serial-subiquity@.service
I am having a same issue as reported by Jake and Jim. Trying to install
on Lanner hardware using USB stick with "ubuntu-18.04.2-live-server-
amd64.iso" image. I used serial console output by enabling
console=ttyS0,115200n8 in Grub config. The installer fails once install
attempts to format a hard drive. I get the following error:
Full installer output ───┐
│Traceback (most recent call last):│
│ File "/snap/subiquity/664/usr/lib/python3.6/runpy.py", line 193, in │
│_run_module_as_main │
│"__main__", mod_spec) │
│ File "/snap/subiquity/664/usr/lib/python3.6/runpy.py", line 85, in _run_code│
│exec(code, run_globals) │
│ File "/snap/subiquity/664/lib/python3.6/site-packages/curtin/__main__.py", │
│line 4, in│
│sys.exit(main()) │
│ File│
│"/snap/subiquity/664/lib/python3.6/site-packages/curtin/commands/main.py",│
│line 177, in main │
│raise OSError("Unable to find helpers or 'curtin' exe to add to path")│
│OSError: Unable to find helpers or 'curtin' exe to add to path│
│
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820604
Title:
curtin fails to find itself in subiquity snap, when running on serial-
subiquity@.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1820604/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
I have now tested the updated Linux kernel from bionic proposed. The new kernel seems to solve the problem and the fix appears OK for : linux-image-generic 4.15.0.55.57 amd64 Generic Linux kernel image Linux 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Hence, I change the tag to verification-done-bionic ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
As I understood it, the fix was unfortunately some days to late for the he previous Kernel SRU cycle. I then expected the fix to be applied for the current SRU cycle, that is, 03-Jun through 30-Jun. I still assume that is the case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
I did expect a change in status to "Fix Committed", indicating that the fix had been applied? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
Thanks a lot. That's great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
This crash is currently critical when using traffic control (tc) in one of the Ubuntu LTS releases, bionic and xenial linux-hwe. I referred to a simple script in the debian bug tracking system that triggers the kernel crash. In my case a normal shutdown/reboot triggers the crash, when the kernel tries to perform cleanup for tc. This leaves the system hanging in a crashed state. In the debian bug reporting system this bug had severity critical and it was fixed March 12th 2019. Is there anything that can be done in order to get this fixed for Ubuntu LTS (bionic and xenial linux-hwe) during the SRU cycle 13-May through 02-June ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
I could have been more explicit. The thread linked to in the initial bug description also contains a simplified script by Ben Hutchings that triggers the kernel crash (included below for the reference): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10 The script triggers the kernel crash in the latest available Ubuntu kernel, that is 4.15.0.48, which affects bionic and xenial linux-hwe. --- BEGIN --- #!/bin/sh -ex modprobe ifb while true; do tc qdisc add dev ifb0 root handle 2:0 prio bands 5 tc qdisc add dev ifb0 parent 2:5 sfq tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on tc qdisc del dev ifb0 root || true done --- END --- ** Bug watch added: Debian Bug tracker #921542 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
Log files should not be required, as this issue is already confirmed and also fixed in the Linux kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
I should have added that there were a couple of other commits related to this issue (memory leaks in cls_tcindex) that were also merged in. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825942] [NEW] kernel crash : net_sched race condition in tcindex_destroy()
Public bug reported: I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739578] Re: Missing support for WPA2 Enterprise
@Timo will this be backported to Core16? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739578 Title: Missing support for WPA2 Enterprise To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1739578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814921] Re: Soundcard isn't recognized after update
Which version? I can try to test. However, as I wrote previously the issue disappears from time to time even on the current kernel. At the moment I have a sound card correctly detected. On Wed, Mar 6, 2019 at 1:41 PM Kai-Heng Feng wrote: > Does previous kernel version work? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1814921 > > Title: > Soundcard isn't recognized after update > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > After last update soundcard stopped working. > $ sudo aplay -l > aplay: device_list:268: no soundcards found... > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-141-generic 4.4.0-141.167 > ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 > Uname: Linux 4.4.0-141-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Wed Feb 6 15:49:19 2019 > EcryptfsInUse: Yes > HibernationDevice: RESUME=UUID=3f6d36fa-7c5e-4a8e-843f-d38f6177dbf0 > InstallationDate: Installed on 2017-02-18 (717 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: System manufacturer System Product Name > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed > root=UUID=0e8ab561-3465-4757-8331-5ee5a859f119 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.4.0-141-generic N/A >linux-backports-modules-4.4.0-141-generic N/A >linux-firmware 1.157.21 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/27/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 3016 > dmi.board.asset.tag: Default string > dmi.board.name: Z170I PRO GAMING > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr3016:bd12/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170IPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > --- > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.04 > EcryptfsInUse: Yes > InstallationDate: Installed on 2017-02-18 (717 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > PackageArchitecture: all > ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 > Tags: xenial > Uname: Linux 4.4.0-141-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 12/27/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 3016 > dmi.board.asset.tag: Default string > dmi.board.name: Z170I PRO GAMING > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr3016:bd12/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170IPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
I found this fix: https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814921] Re: Soundcard isn't recognized after update
The same error persists when booted from Ubuntu 18.04 USB live stick. However, after power cycle prompted at Live Ubuntu shutdown, the sound card had been correctly detected in my main Ubuntu 16.04. ** Attachment added: "dmesg_sound_works.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+attachment/5236697/+files/dmesg_sound_works.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814921] Re: Soundcard isn't recognized after update
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814921] Re: Soundcard isn't recognized after update
I'm almost sure dmesg: [7.949843] snd_hda_intel :00:1f.3: no codecs found! is related to the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814921] Re: Soundcard isn't recognized after update
Unfortunately, it worked only before Suspend. After that again Dummy output only in Sound settings. Reboot doesn't help. It's a strange problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814921] Re: Soundcard isn't recognized after update
Updating the BIOS fixed the issue for me. Please consider whether the bug requires further investigation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814921] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1814921/+attachment/5236402/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814921 Title: Soundcard isn't recognized after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
