[Bug 2063254] Re: firewire_ohci stops under moderate load
Update: this is strangely related to nouveau On a machine with a "NVIDIA MCP89 [GeForce 320M]" the nvidia drivers have been removed from 22.04. nouveau when run normally now causes a hang [see other reports if curious] The described "firewire_ohci quits when using firefox" happens when kernel launched with kernel flag nomodeset When launched, instead, with nouveau.noaccel=1 ...normal usage does not affect firewire_ohci, as expected and desired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063254 Title: firewire_ohci stops under moderate load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
** Attachment added: "screen-2024-04-24-17-49-34.png" https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+attachment/5770120/+files/screen-2024-04-24-17-49-34.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Thank you for the timely reply. I assumed the support site was a report, my apologies, as I assumed it was monitored. I found a very similar report, which I presume is "proper", here: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/1987036 and indeed this is a few days older than the support site reference. I figured the description was sufficient, but will attach a brand-new screenshot. In English as requested. I installed backports and observed exactly the same behavior. Logs showed repeats of the crash until the rate-limiting shutdown of restarts for lxqt-powermanager: Apr 24 17:48:54 Konnekt kernel: lxqt-powermanag[20433]: segfault at e8e ip 7e8466908059 sp 7ffeed791208 error 4 in libQt5Core.so.5.15.3[7e846688e000+30f000] likely on CPU 0 (core 0, socket 0) Apr 24 17:48:54 Konnekt kernel: Code: 31 d2 f7 f1 49 8b 40 08 83 c2 01 48 63 f2 48 8d 04 f0 29 d1 74 d8 89 c9 48 8d 0c c8 eb 0c 0f 1f 00 48 83 c0 08 48 39 c8 74 c4 <48> 8b 10 49 39 d0 74 ef 49 89 d0 4c 89 c0 c3 0f 1f 84 00 00 00 00 This was with the backports version: $ lxqt-powermanagement -v lxqt-powermanagement 1.4.0 liblxqt 1.4.0 Qt5.15.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] [NEW] attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Public bug reported: I have exactly the same problem as OP here (and the others who chime in): https://askubuntu.com/questions/1422776/energy-manager-error-when-reducing-screen-brightness-during-inactivity Reported 1 year 8 months ago, still seems broken LxQT Power Manager: In the settings section for "inactivity", I check the option "enable backlight change", in order to reduce the screen brightness after 1 minute of inactivity. If I press the "Check Backlight" button, nothing happens. Upon completion of 1 minute of inactivity, instead of the screen brightness being reduced, I see the power/battery icon disappear, then reappear a few times, then the system displays an alert of multiple manager crash errors, resulting in its autorun being disabled. Adjusting screen brightness via "lxqt-config-brightness" from "lxqt- config" works fine ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-powermanagement 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Apr 24 10:03:12 2024 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: lxqt-powermanagement UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-powermanagement (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Summary changed: - attempting to use idle brightness in lxqt-powermanagement leads to crash + attempting to use idle brightness in lxqt-powermanagement leads to crashin 22.04.4 LTS ** Summary changed: - attempting to use idle brightness in lxqt-powermanagement leads to crashin 22.04.4 LTS + attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063254] [NEW] firewire_ohci stops under moderate load
Public bug reported: This began in 6.5.0-27 afaict, and is very noticeable in 6.5.0-28 Using snd_dice to playback audio, doing anything else, even just scrolling in firefox or launching this bug report, causes the firewire driver to quit: Apr 23 12:48:53 Konnekt kernel: firewire_ohci :01:00.0: DMA context IT0 has stopped, error code: evt_timeout ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 23 13:08:53 2024 Dependencies: linux-modules-6.5.0-28-generic 6.5.0-28.29~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: linux-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.5 (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/2063254 Title: firewire_ohci stops under moderate load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
I have found a fix. First I tried adding "nouveau.modeset=0" to bootflags, which got me to boot but no greeter. sddm appeared to be happily running but it failed to start the display server restarting it did not help "startx" worked, which gave me hope It appeared the session "seat" had been determined by systemd to have "CanGraphical" false Then I found this: https://github.com/mikhailnov/systemd/commit/c00bf275fdfbad3a9db8934b5e266b6abbdb8443 There's a heuristic hack which sets CanGraphical when the kernel starts w/o graphics, but only if this is done via "nomodeset" rather than the driver-specific ".modeset" flags So I just added "nomodeset" to boot flags, and now not only does 6.5.0-28 boot and land at a working greeter again, but all the weird sddm graphics bugs i'd been encountering since 6.5 are gone. Hope this helps someone else... And maybe this kernel issue will get fixed, some day -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788044 Title: task kworker blocked for more than 120 seconds nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
This is the closest, most recent report I could find with something which also appears kernel related Kernel 6.5.0-27 -- works fine Kernel 6.5.0-28 -- graphics hard-hangs - sddm never displays, vtty can't be activated shh works, sddm and x11 processes can not be killed, reboot hangs, hard power cycle required I see reports like this literally for years, yet seemingly no resolution. Now I'm bit, in a way suspiciously kernel version related Common internet "use nvidia drivers" wisdom is unworkable as old nvidia hardware is not supported on 22.04 04:00.0 VGA compatible controller: NVIDIA Corporation MCP89 [GeForce 320M] (rev a2) Again, for me, this is with 22.04, kernel 6.5.0-28 All the various combinations of nouveau flags to kernel boot which have helped reduce garbage or sddm troubles don't help. Here's a relevant boot log: Apr 20 21:06:29 Konnekt sddm-greeter[922]: Adding view for "LVDS-1" QRect(0,0 1280x800) Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 216004 put 216088 ib_get 0007 ib_put 0007 state 800081a4 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21608c put 217b7c ib_get 0009 ib_put 000a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 218ff0 put 21932c ib_get 000d ib_put 0012 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a48 put 219a64 ib_get 001f ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a64 put 219a7c ib_get 0021 ib_put 0024 state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a7c put 219a8c ib_get 0023 ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a8c put 219ccc ib_get 0025 ib_put 002a state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219de8 put 219df8 ib_get 002f ib_put 0030 state 4004 (err: INVALID_MTHD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: CACHE_ERROR - ch 3 [sddm-greeter[922]] subc 0 mthd data 2000 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219ef0 put 21a2f0 ib_get 0033 ib_put 0038 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 0020b10960 put 0020b10ac8 ib_get 0042 ib_put 0044 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21aff8 put 21bdf4 ib_get 004b ib_put 004c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21c248 put 21c620 ib_get 004d ib_put 004e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417a40 put 417a4c ib_get 0056 ib_put 0058 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417b54 put 417b5c ib_get 005c ib_put 005e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3370 put 4d33f4 ib_get 0062 ib_put 0064 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4db3c0 put 4db450 ib_get 0068 ib_put 006a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21d000 put 21d150 ib_get 006b ib_put 006c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417c50 put 417c5c ib_get 006e ib_put 0070 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3630 put 4d3684 ib_get 007a
[Bug 1898492] [NEW] mosquitto broker websockets no longer work
Public bug reported: Ubuntu 20.04.1 LTS mosquitto 1.6.9-1 I have a MQTT-brokered weather station, which sends realtime updates to a webpage using paho to do MQTT over websockets Everything worked fine until upgrade from bionic to focal The mosquitto broker continued to work fine, but the websocket component stopped functioning The relevant config section for mosquitto is like this: listener 4 ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH certfile /etc/nginx/ssl/acme/site.crt cafile /etc/nginx/ssl/acme/site.fullchain keyfile /etc/nginx/ssl/acme/site.key protocol websockets --- The first issue, netstat confirmed that mosquitto was NOT listening on IPv4, but only on IPv6. IPv6 is not routed to the internet in my installation, so that was an undesirable change in functionality. Adding this stanza: socket_domain ipv4 ...at least got netstat to report IPv4 listening on the websocket port But the websocket server was not reachable from the Internet. It just didn't work, on either Chrome or Firefox, on ubuntu or Windows, though strangely it worked with Mobile Safari on iOS. I made some discoveries... focal uses mosquitto 1.6.9, on top of libwebsockets 3.2.1 [libwebsockets15] bionic used mosquitto 1.4.15, on top of libwebsockets 2.0.3 [libwebsockets8] I pulled down mosquitto 1.6.9 source and the source for both libwebsockets versions from packages.ubuntu.com mosquitto 1.6.9 built against libwebsockets 3.2.1 misbehaved exactly as stock Ubuntu focal builds, which was reassuring mosquitto 1.6.9 built against libwebsockets 2.0.3 functioned properly, as 1.4.15 did on bionic Everything else was left identical. you may note in this report that /usr/sbin/mosquitto is altered - I have replaced it with my hand-built frankenversion, to get my server back in business Cheers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mosquitto 1.6.9-1 [modified: usr/sbin/mosquitto] ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 4 17:07:46 2020 InstallationDate: Installed on 2018-03-07 (942 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mosquitto UpgradeStatus: Upgraded to focal on 2020-10-04 (0 days ago) ** Affects: mosquitto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898492 Title: mosquitto broker websockets no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosquitto/+bug/1898492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
