[Touch-packages] [Bug 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04
I have an Intel Nuc, Product Name: D34010WYK, i3-4010U, its hooked up a Samsung TV via hdmi. The sound defaults to HDMI/DisplayPort - Built-in Audio, Digital Stereo (HDMI) Output but that doesn't work. If I flip it to Digital Surround it works but since the TV only has a left/right speaker I would think stereo should work and doesn't. I confirmed the issue is the same if I boot off the desktop ISO and "Try Ubuntu", since I upgraded my system I thought maybe something wasn't right because of that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1970050 Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: After upgrading today from 20.04 LTS to 22.04 HDMI Audio does not work at all. Audio from speakers from a headphone jack works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 21:13:23 2022 InstallationDate: Installed on 2020-04-24 (729 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97M-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.
I was watching a video over the network from my x1 system when it went offline. My system had been up over a day at the time, Later it came back online and I found this pattern in the logs. Nov 24 22:08:38 x1 kernel: [ 4491.984774] rfkill: input handler enabled Nov 24 22:45:15 x1 kernel: [ 6689.350749] r8169 :04:00.0 eth0: link down Nov 24 22:45:18 x1 kernel: [ 6692.350653] r8169 :04:00.0 eth0: link up ... Nov 24 23:28:51 x1 kernel: [ 9305.191129] perf: interrupt took too long (2514 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Nov 24 23:44:36 x1 kernel: [10250.105921] r8169 :04:00.0 eth0: link down Nov 24 23:44:39 x1 kernel: [10253.137255] r8169 :04:00.0 eth0: link up Nov 24 23:44:41 x1 kernel: [10254.820174] r8169 :04:00.0 eth0: link down Nov 24 23:44:53 x1 kernel: [10267.308766] r8169 :04:00.0 eth0: link down Nov 24 23:44:57 x1 kernel: [10270.416767] r8169 :04:00.0 eth0: link up Nov 24 23:45:05 x1 kernel: [10278.366294] r8169 :04:00.0 eth0: link down Nov 24 23:45:08 x1 kernel: [10281.415489] r8169 :04:00.0 eth0: link up Nov 24 23:45:56 x1 kernel: [10329.333933] r8169 :04:00.0 eth0: link down Nov 24 23:46:04 x1 kernel: [10337.815700] r8169 :04:00.0 eth0: link down Nov 24 23:46:11 x1 kernel: [10344.998667] r8169 :04:00.0 eth0: link up Nov 24 23:46:13 x1 kernel: [10346.873959] r8169 :04:00.0 eth0: link down Nov 24 23:46:16 x1 kernel: [10350.226690] r8169 :04:00.0 eth0: link up Nov 24 23:46:18 x1 kernel: [10352.318011] r8169 :04:00.0 eth0: link down Nov 24 23:46:21 x1 kernel: [10355.245040] r8169 :04:00.0 eth0: link up Nov 26 21:14:23 x1 kernel: [129787.573891] rfkill: input handler enabled Nov 26 21:23:30 x1 kernel: [130334.427437] r8169 :03:00.0 eth0: link down Nov 26 21:23:33 x1 kernel: [130337.443076] r8169 :03:00.0 eth0: link up Nov 26 21:23:57 x1 kernel: [130361.790251] r8169 :03:00.0 eth0: link down Nov 26 21:24:00 x1 kernel: [130364.790674] r8169 :03:00.0 eth0: link up Nov 26 21:41:58 x1 kernel: [131442.193462] r8169 :03:00.0 eth0: link down Nov 26 21:42:01 x1 kernel: [131445.332817] r8169 :03:00.0 eth0: link up Nov 26 21:42:14 x1 kernel: [131458.567170] rfkill: input handler disabled Nov 26 21:42:16 x1 kernel: [131460.513607] r8169 :03:00.0 eth0: link down Nov 26 21:42:19 x1 kernel: [131464.056605] r8169 :03:00.0 eth0: link up Nov 26 21:42:23 x1 kernel: [131467.593377] r8169 :03:00.0 eth0: link down Nov 26 21:42:30 x1 kernel: [131474.613404] r8169 :03:00.0 eth0: link up Nov 26 21:42:41 x1 kernel: [131485.133432] r8169 :03:00.0 eth0: link down Nov 26 21:42:49 x1 kernel: [131493.199224] rfkill: input handler enabled Nov 26 21:42:52 x1 kernel: [131496.274226] r8169 :03:00.0 eth0: link up Nov 26 21:42:53 x1 kernel: [131497.548189] r8169 :03:00.0 eth0: link down Nov 26 21:42:56 x1 kernel: [131500.994252] r8169 :03:00.0 eth0: link up Nov 26 21:42:57 x1 kernel: [131501.750754] r8169 :03:00.0 eth0: link down Nov 26 21:43:04 x1 kernel: [131508.486113] r8169 :03:00.0 eth0: link up root@x1:/var/log# uname -a Linux x1 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@x1:/var/log# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1787824 Title: "rfkill: input handler disabled" boot time 11 seconds. Status in util-linux package in Ubuntu: Incomplete Bug description: My computer is slowly opening, I looked at the output of dmesg and at 11th I get this post. What i need to do? thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rfkill 2.31.1-0.4ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 19:44:21 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libsmartcols1 2.31.1-0.4ubuntu3.1 InstallationDate: Installed on 2018-08-18 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1787824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371250] Re: LightDM fails to switch to greeter on logout if allow-user-switching=false
Hello, I'm using multiseat under ubuntu lts 16.04 I found a description of what is happening here: https://lists.launchpad.net/ubuntu-multiseat/msg00505.html In short, seat-1 lock/switch user doesn't work and generates tons of error logs [+763003.64s] DEBUG: Launching process 27821: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp [+763003.69s] DEBUG: Launching process 27822: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp [+763003.74s] DEBUG: Launching process 27823: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp [+763003.79s] DEBUG: Launching process 27824: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp [+763003.84s] DEBUG: Launching process 27825: /usr/bin/X :1 -s seat-1 :2 -config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 -nolisten tcp I configured allow-user-switching=false so that my logs won't fill up. [Seat:seat-1] xserver-command=/usr/bin/X :1 -s seat-1 xserver-config=/etc/X11/xorg.conf.nvidia # This kept constant respawn of X from filling up logs, but only allows one login - greeter fails to start allow-user-switching=false Now what happens, just as reported in this bug is that I can start lightdm, and someone can login once to seat-1, but once they log out there is no greeter respawned. I think this bug should be updated to include Xenial as well. Anyways I'm sure multiseat is a rare thing but I wanted someone to know it matters to me. I'm so close to having it work! Is there anything else I can try to work around? I see the question above: "Should we adopt the following solution for this bug?" I vote yes to that. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1371250 Title: LightDM fails to switch to greeter on logout if allow-user- switching=false Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in Light Display Manager 1.12 series: Won't Fix Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Won't Fix Bug description: In my multiseat system, if I logout on a non-seat0 seat (which has allow-user-switching=false by default), lightdm fails to start a greeter on that seat: DEBUG: Seat: Display server stopped DEBUG: Seat: Active display server stopped, starting greeter DEBUG: Seat: Stopping; failed to start a greeter DEBUG: Seat: Stopping DEBUG: Seat: Stopped I guess the problem is related to seat_switch_to_greeter() calls in session_stopped or display_server_stopped callbacks in seat.c. Switch to greeter should be always allowed on logout. NOTE: This was observed in LightDM 1.10.2 on Ubuntu 14.04, but I guess it also happens on trunk series. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553466] Re: org.gnome.SessionManager was not provided by any .service files
lxterminal on lubuntu on a raspberrypi2 segfaults due to this bug (or at least that's what it looks like to me) root@x3:~# uname -a Linux x3 4.4.0-1010-raspi2 #13-Ubuntu SMP Fri May 13 16:04:46 UTC 2016 armv7l armv7l armv7l GNU/Linux ERROR: apport (pid 8102) Fri Jun 3 21:31:43 2016: debug: session gdbus call: ERROR: apport (pid 8102) Fri Jun 3 21:31:44 2016: this executable already crashed 2 times, ignoring ERROR: apport (pid 8106) Fri Jun 3 21:31:46 2016: called for pid 8092, signal 11, core limit 0 ERROR: apport (pid 8106) Fri Jun 3 21:31:46 2016: executable: /usr/bin/strace (command line "strace lxterminal") ERROR: apport (pid 8106) Fri Jun 3 21:31:46 2016: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1553466 Title: org.gnome.SessionManager was not provided by any .service files Status in dbus package in Ubuntu: Confirmed Bug description: This is logged into journalctl: org.gnome.ScreenSaver[1755]: ** (gnome-screensaver:1868): WARNING **: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dbus 1.10.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 5 08:37:25 2016 ExecutablePath: /usr/bin/dbus-daemon ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) upstart.dbus.log: Activating service name='org.gnome.Terminal' Successfully activated service 'org.gnome.Terminal' Activating service name='org.gnome.Terminal' Successfully activated service 'org.gnome.Terminal' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1553466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
