![]() That covers all of the possibilities for customizing the look and feel of openbox. Note that this does not create a dock (or panel, or whatever), that still has to be done by another application, but if/when such an application is running, this specifies how openbox will interact with it. Dock: Where to place and how to handle a dock.This can be useful if you don't have panels or docks, and the background is the only way to get to a window manager menu. Margins: If you want to reserve a few pixels around the edge of the screen so you can always reach the desktop background.Desktops: Specify the number and name of virtual desktops, and behavior on switching.Mouse: How to handle window focus transfer with mouse movement, and what action to take when the title bar is double-clicked.Move & Resize: Behavior such as whether to (try to) maintain the window contents while moving, and whether to dynamically display size information while resizing.Windows: Specify placement and focus of new windows, and how multiple displays are handled.Shutter can be a convenient way to minimize a window without actually losing it off the display and having to use Alt-Tab to recover it. If you like the 'shutter roll-up' function, add 'S' to the mix. If you prefer the Ubuntu approach of having all the buttons at the left side, specify IMCL. Each possible item is represented by one letter, so the default is 'NLIMC', which places the window icon at the left end, and the iconify, maximize and close buttons at the right end. The idea here is that the Title is always centered in the title bar, and it automatically expands to push whatever is placed on either side of it to the ends of the title bar. Appearance: Specify the content and order of window title bar controls.To do this - just edit /etc/grub.d/10_linux file. Solution is remove from grub $vt_handoff string. Model name: Intel(R) Pentium(R) CPU N3540 2.16GHzįlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat Initialized Arguments for Method : (1 arguments defined for method invocation)Īrg0: 00000000fe968048 Integer 00000000000000D3ĪCPI Error: Aborting method \_SB.HKEY.DEVT due to previous error (AE_NOT_FOUND) (20210331/psparse-529) No Local Variables are initialized for Method I was also seeing the following ACPI error: ACPI BIOS Error (bug): Could not resolve symbol, AE_NOT_FOUND (20210331/psargs-330) ![]() The traces are: WARNING: CPU: 0 PID: 18016 at /var/lib/dkms/nvidia/510.47.03/build/nvidia/nv.c:3935 nv_restore_user_channels+0xce/0xe0 It is easy to know if you've hit the same bug or not, just look for the following stack traces on your dmesg.īecause you are likely shutting down the computer and restarting, you have to look for them in the dmesg of the previous boot as per : journalctl -b-1 Note that even non graphic stuff like NVIDIA's CUDA/OpenCL package was still breaking things, notably I couldn't suspend after removing the graphics but keeping them, related: PURGE EVERYTHING FROM NVIDIA: uninstall all nvidia packages ( dpkg -l | grep -i nvidia, sudo apt uninstall), and purge their configs as well ( sudo apt purge. Apparently this is broken on some setups and kernels. ![]() The 470 driver migrated to systemd method while previous versions relied on Kernel Driver Callback. ![]() In case you nuke it, the contents of nvidia.bak are: #!/bin/sh Sudo mv /lib/systemd/system-sleep/nvidia ~/nvidia.bak (tested for several days now, seems to be working) the bug report links to from heroic user humblebee which has workaround: sudo systemctl stop rvice Otherwise, the problem would only happen sometimes, and more commonly after suspending for a few hours. To reproduce the problem easily, I had to disconnect the power cable from my laptop and be on battery only. This started happening to me as soon as I moved to Ubuntu 21.10 on my Lenovo ThinkPad P51 NVIDIA Quadro M1200, and based on kernel traces, it is this exact bug: My duplicated investigation: Ubuntu 21.10 NVIDIA 470/510 nv_restore_user_channels bug
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |