[Bug 1896482] Re: acpi event detection crashes
It seems like nobody is paying attention to this since the fix (which does not work) was released. Maybe we need to post new bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896482] Re: acpi event detection crashes
damn, wrong again, the patched kernel has just displayed the bug. no fixed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896482] Re: acpi event detection crashes
sorry, I retract that. The problem is that ubuntu updated my kernel without my knowledge, replacing the correctly patched kernel with the broken one (that both have the same numbers!) It would be nice if the patch got incorporated into the distro to save me and others from this headache! I have since noticed that no only is hibernation screwed up by this bug, but also detection of the power supply and the brightness buttons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896482] Re: acpi event detection crashes
Unfortunately it looks like the bug did not disappear. I have it starting around 45 minutes after booting in the kernel we thought was good, 5.4.0-52-generic_5.4.0-52.57. Unless I somehow screwed up and reinstalled a broken one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922577] [NEW] secondary selection with middle mouse button not working
Public bug reported: On my new computer, secondary selection with the middle mouse button is not working. The cursor does not move when I attempt to drag it while the middle button is pressed. It may be a motif bug rather than an nedit bug, since the problem does not occur when I ssh into the problem computer from a working system and run nedit remotely, whereas the same problem occurs if I ssh into the working system and remotely run nedit from the problem computer. But nedit is the only application where I am seeing any problem with the middle mouse button. $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 $ apt-cache policy nedit nedit: Installed: 1:5.7-2 Candidate: 1:5.7-2 Version table: *** 1:5.7-2 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: nedit (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/1922577 Title: secondary selection with middle mouse button not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nedit/+bug/1922577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898389] Re: browser frequently crashing with trap int3
I've switched to firefox, that solved 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/1898389 Title: browser frequently crashing with trap int3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898389] [NEW] browser frequently crashing with trap int3
Public bug reported: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages *** 85.0.4183.83-0ubuntu0.16.04.2 100 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 18.0.1025.151~r130497-0ubuntu1 500 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages dmesg: [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 sp:7ffdfc31ca70 error:0 [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 sp:7ffd8fc04770 error:0 [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 sp:7ffdfc31b2c0 error:0 [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be sp:7ffdfc31bd40 error:0 [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 sp:7ffdfc31cab0 error:0 [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 sp:7ffdfc31b300 error:0 [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 sp:7ffdfc31c640 error:0 [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be sp:7ffdfc31a6a0 error:0 [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 sp:7fe1dcaf95e0 error:0 [519367.329864] traps: chromium-browse[24588] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.357674] traps: chromium-browse[24558] trap invalid opcode ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 sp:7ffdfc316260 error:0 [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 sp:7ffdfc31abd0 error:0 [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be sp:7ffdfc31bbb0 error:0 [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 sp:7ffdfc31d020 error:0 [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 sp:7ffdfc3165c0 error:0 [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 sp:7ffdfc3164c0 error:0 [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 sp:7ffdfc31c5b0 error:0 [519429.841404] traps: chromium-browse[24906] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000 ** Affects: chromium-browser (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/1898389 Title: browser frequently crashing with trap int3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
That's right, I masked them by hand following some advice on the internet for how to make systemd stop suspending, since it was not responding to settings in login.conf even after restating logind service. Regardless of my motivation, it seems buggy that changing these settings should lead to such undesirable behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896395] Re: lid closure behavior unpredictable
sorry, you can withdraw this bug as I discovered it is a kernel bug, not systemd. (I wanted to withdraw it earlier but did not know how to get back to this report.) thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896395 Title: lid closure behavior unpredictable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896482] [NEW] acpi event detection crashes
Public bug reported: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666] acpi_ev_address_space_dispatch+0x2f7/0x39f Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 Sep 20 11:35:33 laxmi kernel: [232492.303670] acpi_ex_access_region+0x454/0x4ed Sep 20 11:35:33 laxmi kernel: [232492.303672] acpi_ex_field_datum_io+0x18a/0x42d Sep 20 11:35:33 laxmi kernel: [232492.303673] acpi_ex_extract_from_field+0x172/0x320 Sep 20 11:35:33 laxmi kernel: [232492.303675] acpi_ex_read_data_from_field+0x30f/0x361 Sep 20 11:35:33 laxmi kernel: [232492.303677] acpi_ex_resolve_node_to_value+0x3a7/0x4dd Sep 20 11:35:33 laxmi kernel: [232492.303679] acpi_ex_resolve_to_value+0x3c3/0x472 Sep 20 11:35:33 laxmi kernel: [232492.303681]
[Bug 1896395] Re: lid closure behavior unpredictable
Using systemctl status systemd-logind, I see that lid events are no longer being detected. This behavior persists even after restarting the service. This is *not* what is requested in logind.conf, where HandleLidSwitch=suspend and HandleLidSwitchDocked=suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896395 Title: lid closure behavior unpredictable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896395] [NEW] lid closure behavior unpredictable
Public bug reported: in 20.04.01 LTS (release 20.04), suspend on lid closure works for a while, then one day stops working, with no error message in syslog. The event is not even registered. The problem seems to start when the system has been inactive for long enough so that the screen is blanked. systemd: Installed: 245.4-4ubuntu3.2 Candidate: 245.4-4ubuntu3.2 Version table: *** 245.4-4ubuntu3.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages seems similar to bug #1840784, even though no error message is generated. ** Affects: systemd (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/1896395 Title: lid closure behavior unpredictable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
by unmasking sleep.target suspend.target hibernate.target hybrid- sleep.target, and allowing for suspend on lid closure in login.conf, I was able to make the problem go away, but why should I be forced to this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896137] [NEW] syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
Public bug reported: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: When I close the lid on my laptop, syslog goes crazy with the message - a: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 + systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. ** Package changed: perf-tools-unstable (Ubuntu) => systemd (Ubuntu) ** Description changed: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but - systemd is trying to kill me with these messages. + systemd is trying to kill me with these messages. I am running Ubuntu + 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895217] Re: gnome control center mouse settings don't work in other window manager
Hi Daniel, yes I was going to resort to that if necessary. Thanks! One comment though, I found that the setting was not even saved before I switched to Fvwm. I had to redo the mouse speed each time I logged into an Ubuntu session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895217 Title: gnome control center mouse settings don't work in other window manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895217] [NEW] gnome control center mouse settings don't work in other window manager
Public bug reported: I would like to use gnome control center from Fvwm window manager. But the mouse speed does not respond at all to what I set unless I am running it from the default ubuntu window manager. I tried running gnome control center using different XDG environment variables as suggested by some posts, but this had no effect. ** Affects: gnome-control-center (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/1895217 Title: gnome control center mouse settings don't work in other window manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
