i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Sat, 22 Jun 2013 14:37:20 +0000SysRq R E I S U B is not working.https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/I installed i3 a few months ago under ubuntu 12.10 with gnome shell. I used the ubuntu package, i3 "registered" automatically with ldm, so on the rare occasion of a restart, I log in by choosing i3 in ldm. Everything really works fine except for one thing: SysRq R E I S U B won't work, when my machine gets unresponsive. Thanks in advance for any answer. [Edit 2013-06-21 07:40] Well. Maybe I got carried away when I wrote "Thanks in advance for _any_ answer". One cannot simply(TM) type "sudo reboot" once the machine is unresponsive, let alone switch to a workspace with an open terminal. As is explained quite nicely in the quoted wikipdia article, holding SysRq and typing the aforementioned sequence of keys is kind of a last resort to regain control over your machine when the beast won't do anything anymore. [Edit 2013-06-22 16:42] Maybe it's not i3's fault. Maybe the kernel got into a condition, from which nothing could be done anyway. I'll try to explain the details: I was listening to some music with XBMC on HDMI1, while at the same time changing some Firefox preferences on LVDS1. I put the preference dialog into floating mode and started changing. Once I tried to save the new settings, the floating window became unresponsive _and_ a very small portion of the track I was listening to started to loop. So a was sitting there with a pseudo-techno loop and an unresponsive screen. I tried SysRq R E I S U B -- but I had to hard-reset my machine. That's about it.Thu, 20 Jun 2013 07:21:31 +0000https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/Comment by joepd for I installed i3 a few months ago under ubuntu 12.10 with gnome shell. I used the ubuntu package, i3 "registered" automatically with ldm, so on the rare occasion of a restart, I log in by choosing i3 in ldm. Everything really works fine except for one thing: SysRq R E I S U B won't work, when my machine gets unresponsive. Thanks in advance for any answer. [Edit 2013-06-21 07:40] Well. Maybe I got carried away when I wrote "Thanks in advance for any answer". One cannot simply(TM) type "sudo reboot" once the machine is unresponsive, let alone switch to a workspace with an open terminal. As is explained quite nicely in the quoted wikipdia article, holding SysRq and typing the aforementioned sequence of keys is kind of a last resort to regain control over your machine when the beast won't do anything anymore. [Edit 2013-06-22 16:42] Maybe it's not i3's fault. Maybe the kernel got into a condition, from which nothing could be done anyway. I'll try to explain the details: I was listening to some music with XBMC on HDMI1, while at the same time changing some Firefox preferences on LVDS1. I put the preference dialog into floating mode and started changing. Once I tried to save the new settings, the floating window became unresponsive and a very small portion of the track I was listening to started to loop. So a was sitting there with a pseudo-techno loop and an unresponsive screen. I tried SysRq R E I S U B -- but I had to hard-reset my machine. That's about it. https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2064#comment-2064@bruno: Thanks for the link! @j-son-quarc: does the key work with another window manager? Sat, 22 Jun 2013 09:34:32 +0000https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2064#comment-2064Comment by J-Son-Quarc for I installed i3 a few months ago under ubuntu 12.10 with gnome shell. I used the ubuntu package, i3 "registered" automatically with ldm, so on the rare occasion of a restart, I log in by choosing i3 in ldm. Everything really works fine except for one thing: SysRq R E I S U B won't work, when my machine gets unresponsive. Thanks in advance for any answer. [Edit 2013-06-21 07:40] Well. Maybe I got carried away when I wrote "Thanks in advance for any answer". One cannot simply(TM) type "sudo reboot" once the machine is unresponsive, let alone switch to a workspace with an open terminal. As is explained quite nicely in the quoted wikipdia article, holding SysRq and typing the aforementioned sequence of keys is kind of a last resort to regain control over your machine when the beast won't do anything anymore. [Edit 2013-06-22 16:42] Maybe it's not i3's fault. Maybe the kernel got into a condition, from which nothing could be done anyway. I'll try to explain the details: I was listening to some music with XBMC on HDMI1, while at the same time changing some Firefox preferences on LVDS1. I put the preference dialog into floating mode and started changing. Once I tried to save the new settings, the floating window became unresponsive and a very small portion of the track I was listening to started to loop. So a was sitting there with a pseudo-techno loop and an unresponsive screen. I tried SysRq R E I S U B -- but I had to hard-reset my machine. That's about it. https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2065#comment-2065@joepd: AFAIK it works for Linux in general. And I can use it under i3 when the machine is responsive -- but that's not when you want to use it. Maybe it's not i3's fault at all.Sat, 22 Jun 2013 14:37:20 +0000https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2065#comment-2065Comment by joepd for I installed i3 a few months ago under ubuntu 12.10 with gnome shell. I used the ubuntu package, i3 "registered" automatically with ldm, so on the rare occasion of a restart, I log in by choosing i3 in ldm. Everything really works fine except for one thing: SysRq R E I S U B won't work, when my machine gets unresponsive. Thanks in advance for any answer. [Edit 2013-06-21 07:40] Well. Maybe I got carried away when I wrote "Thanks in advance for any answer". One cannot simply(TM) type "sudo reboot" once the machine is unresponsive, let alone switch to a workspace with an open terminal. As is explained quite nicely in the quoted wikipdia article, holding SysRq and typing the aforementioned sequence of keys is kind of a last resort to regain control over your machine when the beast won't do anything anymore. [Edit 2013-06-22 16:42] Maybe it's not i3's fault. Maybe the kernel got into a condition, from which nothing could be done anyway. I'll try to explain the details: I was listening to some music with XBMC on HDMI1, while at the same time changing some Firefox preferences on LVDS1. I put the preference dialog into floating mode and started changing. Once I tried to save the new settings, the floating window became unresponsive and a very small portion of the track I was listening to started to loop. So a was sitting there with a pseudo-techno loop and an unresponsive screen. I tried SysRq R E I S U B -- but I had to hard-reset my machine. That's about it. https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2059#comment-2059Call me ignorant and too lazy to search but as this FAQ wants to have questions ans answers showing up at search engines, care to explain why you would like to type R E I S U B ? Thu, 20 Jun 2013 22:24:43 +0000https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2059#comment-2059Comment by bruno.braga for I installed i3 a few months ago under ubuntu 12.10 with gnome shell. I used the ubuntu package, i3 "registered" automatically with ldm, so on the rare occasion of a restart, I log in by choosing i3 in ldm. Everything really works fine except for one thing: SysRq R E I S U B won't work, when my machine gets unresponsive. Thanks in advance for any answer. [Edit 2013-06-21 07:40] Well. Maybe I got carried away when I wrote "Thanks in advance for any answer". One cannot simply(TM) type "sudo reboot" once the machine is unresponsive, let alone switch to a workspace with an open terminal. As is explained quite nicely in the quoted wikipdia article, holding SysRq and typing the aforementioned sequence of keys is kind of a last resort to regain control over your machine when the beast won't do anything anymore. [Edit 2013-06-22 16:42] Maybe it's not i3's fault. Maybe the kernel got into a condition, from which nothing could be done anyway. I'll try to explain the details: I was listening to some music with XBMC on HDMI1, while at the same time changing some Firefox preferences on LVDS1. I put the preference dialog into floating mode and started changing. Once I tried to save the new settings, the floating window became unresponsive and a very small portion of the track I was listening to started to loop. So a was sitting there with a pseudo-techno loop and an unresponsive screen. I tried SysRq R E I S U B -- but I had to hard-reset my machine. That's about it. https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2061#comment-2061http://en.wikipedia.org/wiki/Magic_SysRq_keyThu, 20 Jun 2013 22:33:40 +0000https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?comment=2061#comment-2061Answer by bruno.braga for I installed i3 a few months ago under ubuntu 12.10 with gnome shell. I used the ubuntu package, i3 "registered" automatically with ldm, so on the rare occasion of a restart, I log in by choosing i3 in ldm. Everything really works fine except for one thing: SysRq R E I S U B won't work, when my machine gets unresponsive. Thanks in advance for any answer. [Edit 2013-06-21 07:40] Well. Maybe I got carried away when I wrote "Thanks in advance for any answer". One cannot simply(TM) type "sudo reboot" once the machine is unresponsive, let alone switch to a workspace with an open terminal. As is explained quite nicely in the quoted wikipdia article, holding SysRq and typing the aforementioned sequence of keys is kind of a last resort to regain control over your machine when the beast won't do anything anymore. [Edit 2013-06-22 16:42] Maybe it's not i3's fault. Maybe the kernel got into a condition, from which nothing could be done anyway. I'll try to explain the details: I was listening to some music with XBMC on HDMI1, while at the same time changing some Firefox preferences on LVDS1. I put the preference dialog into floating mode and started changing. Once I tried to save the new settings, the floating window became unresponsive and a very small portion of the track I was listening to started to loop. So a was sitting there with a pseudo-techno loop and an unresponsive screen. I tried SysRq R E I S U B -- but I had to hard-reset my machine. That's about it. https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?answer=2060#post-id-2060Why doesn't work? What happens? Have you tried: sudo reboot I never worried about SysRq because: - I run on a Apple hardware (they don't have this key); - Laptop nowadays you never need to shutdown, just suspend by lid action; - and lastly, I rarely have a window without a terminal on it, so typing reboot is not much of a pain to me, when I need it. Thu, 20 Jun 2013 22:33:15 +0000https://faq.i3wm.org/question/2055/sysrq-r-e-i-s-u-b-is-not-working/?answer=2060#post-id-2060