I'm using Fedora 35 on my laptop. When I open anaconda-navigator I got this message:
"WARNING linux_scaling.get_scaling_factor_using_dbus:42
Can't detect system scaling factor settings for primary monitor."
and yes, the window for anaconda can't be resized. I disabled "enable high-DPI scaling" setting in Navigator's Preferences menu, as this has worked for other users. Not for me. Also tried to change in ~/.anaconda/navigator/anaconda-navigator.ini :
<enable_high_dpi_scaling = True> to <enable_high_dpi_scaling = False>, or <enable_high_dpi_scaling = None>
but this also hasn't worked. As I said, I'm using Fedora 35 on gnome 41 and I'm trying to run anaconda3 on 64 bit. Any ideas?
I have a very weird issue. I purchased the Logitech MX Keys Macintosh version. After settings up Pop OS by choosing the French Macinstosh version (which) is the correct one, the Logitech version swaps my # and < key strokes. When I connect a native Macintosh keyboard it works. Anyone any tip how I can fix this?
I had the same issue but not sure about the cause, pressing fn +p for 3 seconds seems to switch it back correctly.
Also, via the Logitech software:
disable the 'Always keep in mac-layout'.
Sorry about my English skill. Currently, I am using Gnome 3 On the Fedora 19. (Sometime I switch to Cinnamon desktop :)). When I using Gnome 3, the window top bar is not uniform on all windows, but on Cinnamon, that is working well. If you know about that, pls tell me why and how to fix it!!! Thanks to much...
http://i.stack.imgur.com/gt2i5.png
http://i.stack.imgur.com/RZK4c.png
I had the same problem when install almost every theme on Fedora 19, Nautilus fails to respect gnome's theme settings. After some research, my best guess about why it happens is because most themes only support nautilus 3.6 but however in fedora 19 we have nautilus 3.8. And there is no way to downgrade.
(I also tried your theme from http://satya164.deviantart.com/art/Numix-GTK3-theme-360223962 and with no luck, it doesn't work for me either. I'll update if I find a way)
Environment:
vim7.3
secureCRT 5.1
CentOS 5
Screenshot: http://www.pureonebio.com/tmux.png
http://blog.hawkhost.com/2010/07/02/tmux-%E2%80%93-the-terminal-multiplexer-part-2/#modifying-tab-color
http://blog.oldworld.fr/index.php?post/2010/03/21/256-colors-terminal-with-tmux-and-urxvt
The colour change may be due to the color support issues of the computer you use. Some support 256 where some do not. What is so special about colors when the usage is important? Anyway, have a good time.
This is obviously a stupid question.
I am coding in Eclipse both on Mac and Linux, but I mixed up and used the Mac shortcut to window tabbing (Ctrl-Cmd-F6), but I was using the Linux on uni and screen went black. I've done this before, but this time I can't get back to my desktop. Ctrl-Alt F1-F6 gives me different terminals, F7 gives me a black screen and F8 a blinking underscore in the top left corner. Shouldn't my session have been somewhere in F1-F6 and is it lost?
Ctrl-Alt-F7 should work perhaps your X has crashed?
I just did what you did and F7 got it back for me, saying that before I remember X crashing and I had the same black screen
I had the same issue. I tried with hitting ctl+ alt + F1 together. And it worked
X is probably still running on F7, your display driver (or something else) is just misbehaving. You might be able to trick it into coming back on by going to F7 and blindly opening a terminal and playing with xset ($ xset dpms force on). Or you can ctrl-alt-backspace to kill X and GDM should restart it.
Try seeing if you can repeat the problem and then file a bug report (or let the lab admin know if it isn't your computer). It probably has something to do with your distro's kernel configuration/patching. I've had this happen before on Ubuntu but not any other distros (I've used many), which is why I am assuming it might be distro-specific issue. Probably the unintended consequences of some kernel patching.
The ctrl+alt+Fx (x=1..6) key combinations often allow you to have up to 6 concurrent terminal sessions on the console.
Usually one is setup to use X windows, and differs from distribution to distribution. Typically its on Ctrl+Alt+F7.
http://linux.about.com/od/linux101/l/blnewbie5_1.htm
Some distributions of Linux allow you to kill the X Windows session with Ctrl+Alt+Backspace at which point the operating system will attempt to restart it.
alt + F1
works for ubuntu 18.04.
In the future, you can go into a terminal and type:
init 3
To bring the system into text mode, and:
init 5
To return the system to X mode. The nice thing about doing it that way is that everything should be shut down and restarted cleanly.
For My case. I tried with hitting
ctl+ alt + F2
together. And it worked in Fedora
Try Ctrl-Alt-F9, and Ctrl-Alt-F10. :-)
Looks like X crashed. To check, you could log in on one of the terminals (on Ctrl+F1 etc.) and check that the "X" process is still running.
I've had the same happen to me recently, and found the SIGSEGV and backtrace later in /var/log/Xorg.0.log. Curse your graphics driver vendor (usually) and then reboot.
We're running gnome on Red Hat 5.
ps axu in one of the other terminals showed some of the processes still running. Probably something with the display drivers then. Did ctrl-alt-backspace and restarted it. Thanks for the help.
F8 solves the problem in Linux Mint 17.3 Rosa