<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gnome on Michael’s Domain</title><link>https://jeltsch.org/en/tags/gnome/</link><description>Recent content in Gnome on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/gnome/index.xml" rel="self" type="application/rss+xml"/><item><title>Application is not responding</title><link>https://jeltsch.org/en/alive-timeout/</link><pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/alive-timeout/</guid><description>&lt;p&gt;In Gnome, you get a warning if an application takes too long to complete a task. This can be really annoying if you know that the application is just trying to do its job with the available resources. Gdebi, Zotero and SnapGene are some of the apps that frequently cause this timeout warning on my (rather slow) laptop. To let Gnome know to stop sending this disturbing notification (or at least make them much less frequent), you can increase the timeout like this:&lt;/p&gt;</description></item><item><title>Gnome &amp; KDE sessions autostart items</title><link>https://jeltsch.org/en/gnome_kde_sessions_autostart_items/</link><pubDate>Fri, 25 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/gnome_kde_sessions_autostart_items/</guid><description>&lt;p&gt;Always when I logged into a Gnome session, automatically several application started up without me wanting them to start up (two terminal sessions and a nautilus windows). To get rid of them (at least I think so, I will see at the next login), you have to go to Main Menu - Preferences - More preferences - Sessions. Under the &amp;ldquo;Current Session&amp;rdquo; tab, one can remove the programs that are automatically started upon login and also specify in which order the programs are started that are started automatically.In KDE, item in the /home/user/.kde/Autostart directory get executed upon session start. Just place a .desktop file into that directory to have it auto-executed.&lt;/p&gt;</description></item><item><title>Location of launchers, panels, etc. in Gnome</title><link>https://jeltsch.org/en/location_of_launchers_panels_etc_in_gnome/</link><pubDate>Fri, 25 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/location_of_launchers_panels_etc_in_gnome/</guid><description>&lt;p&gt;The files that specify the different folders and buttons of the Gnome user interface are somehow really badly distributed all over the place. Here are just a few of the more common locations:Icons in the panel: ~/.gnome2/panel2.d/default/launchers/Contents of Start Here: ~/.gnome2/vfolders/start-here/user&amp;rsquo;s Home, Trash and Start Here: ~/.gnome-desktop/&lt;/p&gt;</description></item><item><title>Desktop Integration of the Staden Package in KDE on Suse Linux 9</title><link>https://jeltsch.org/en/desktop_integration_of_the_staden_package_in_kde_on_suse_linux_9/</link><pubDate>Sat, 19 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/desktop_integration_of_the_staden_package_in_kde_on_suse_linux_9/</guid><description>&lt;p&gt;I have installed the Staden package on my laptop. In order to convince other people from my lab to use it, it must be very easy to use. Ideally, they should just need to select some sequences, click and the preprocessing and assembly should be done automatically. In order to achieve that I did the following:&lt;/p&gt;</description></item></channel></rss>