Difference between revisions of "Talk:GNOME"

From ArchWiki
Jump to: navigation, search
(Candidates for removal (discussion))
(Getting traces of gnome-shell crashes: re, close)
 
(216 intermediate revisions by 28 users not shown)
Line 1: Line 1:
== Installation ==
+
== GNOME applications blocking window manager keyboard shortcuts? Drawing over everything? ==
Being that {{ic| pacman -S gnome}} produces a numbered list, wouldn't be prudent to specify packages that are ''critical'' for a workable desktop? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:00, 28 January 2013 (UTC)
 
  
== Candidates for removal (discussion) ==
+
Seen on Fluxbox, using evince, totem, baobab.(as of 3.14.1-2, 3.14.1-1, 3.14.1-1, well, earlier) Makes these programs near-useless.[[User:Jasper1984|Jasper1984]] ([[User talk:Jasper1984|talk]]) 15:31, 8 December 2014 (UTC)
  
* [[GNOME#Some_.27System_Settings.27_not_preserved]] - Poor language and doubles what's explained (more thoroughly) in [[Systemd]]. Should be rewritten and reference to [[Systemd]]
+
:I believe this is not just about GNOME, but all [[GTK+]] and [[Qt]] applications [https://bugzilla.gnome.org/show_bug.cgi?id=344059] [https://bugs.kde.org/show_bug.cgi?id=70063]. Haven't read through the reports, but it appears to be some flaw in [[Xorg]]. Not much we can do about this, so unless you want to discuss a workaround this can be closed. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:50, 8 December 2014 (UTC)
  
* [[GNOME#Extensions_do_not_work_after_GNOME_3_update]] - Advises people to skip version checks when extensions no longer load due to version incompatibility. I'm not sure this is something we should be telling users to do.
+
:Can you confirm this with another toolkit than GTK3 ? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:35, 10 January 2015 (UTC)
 
 
* [[GNOME#Login_screen]] - GDM is not part of clean GNOME, should we add this to [[GDM]] in stead?
 
:: +1. I think this part is created before [[GDM]] exist. Merge request added. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:33, 14 September 2012 (UTC)
 
 
 
:: I would also like to gather and give a private section to extensions. Currently that information is spread around the article, I think it deserves its own section within this article.
 
 
 
:: +1 Added clarity to merge tag. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:18, 28 January 2013 (UTC)
 
 
 
*[[GNOME#Shutdown_via_the_status_menu]] - As of Gnome (3.6.2), this is no longer the case.  Gnome has switched back to using Power Off in the menu.
 
 
 
: I see that the "Troubleshooting" section is bloated and requires cleanup.  I support removal of material so as long that: It is proven to be irrelevant from this point forward, or condensed into notes/tips that are assimilated into the main article with external links for reference if need be.  [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 21:18, 28 January 2013 (UTC)
 
  
 
== GNOME and fontconfig settings ==
 
== GNOME and fontconfig settings ==
Line 74: Line 62:
 
  </match>
 
  </match>
  
 +
(to be finished, please comment or fix) {{Unsigned|23:58, 8 January 2012‎|Erm67}}
 +
 +
:I think that info must be in [[Font configuration]], linked from there if needed -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 10:57, 3 June 2014 (UTC)
 +
 +
::Well, it is very GNOME specific and complex at the same time. I would vote for putting it into [[GNOME tips]] and crosslink it from [[GNOME#Fonts]] as well as from [[Font configuration]]. But first: Above contribution of Erm67 is a couple of years back. Does someone know whether the instructions still work like that? --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 09:04, 10 November 2014 (UTC)
 +
::Update to note: [[GNOME tips]] was cleaned up removing GNOME content after I suggested above. It does not make sense to put these instructions there anymore. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 12:41, 15 January 2015 (UTC)
 +
 +
== Natural scrolling ==
 +
 +
I can't get reverse natural scrolling on my trackpath to work (scroll with fingers in same direction as if it was a mouse wheel). I am happy to propose some text for the wiki if someone can tell me how to do it ... --[[User:Bronze|Bronze]] ([[User talk:Bronze|talk]]) 04:33, 26 February 2017 (UTC)
 +
 +
:Is there not a natural scrolling setting under Settings -> Mouse & Touchpad that you can toggle? -- [[User:Chazza|Chazza]] ([[User talk:Chazza|talk]]) 09:57, 26 February 2017 (UTC)
 +
:: i saw this with computers which have a keyboard with integrated touchpads like the logitech k400, and no mouse connected. not sure what makes gnome than display nothing ... --[[User:Soloturn|Soloturn]] ([[User talk:Soloturn|talk]]) 05:11, 1 April 2017 (UTC)
 +
 +
== <s>Getting traces of gnome-shell crashes</s> ==
  
(to be finished, please comment or fix)
+
Gnome-shell uses javascript, which makes it hard to debug.
  
== deleted manual hotkeys modification ==
+
To enable debugging of extensions, it is necessary to
  
Manual edit of accel.scm into nautilus config doesn't fit with this page. And this can't be a generic method, cause not every application has an accels.scm file, even if it has that, it's location in ~/.config is not mandatory.
+
1) rebuild gjs with CXXFLAGS='-g -O0'
[[User:4javier|4javier]] 08:09, 25 April 2011 (EDT)
 
  
:It fits with this page just as much as the remaining part on changing hotkeys does because both serve the same purpose. So I disagree with that it should be downright deleted, particularly as for me (thus possibly others) the ''can-change-accels'' way did not work. I added it again (a bit more carefully phrased) to the "Troubleshooting" section. -- [[User:Misc|Misc]] 15:40, 25 April 2011 (EDT)
+
<pre>packages/gjs/trunk$ svn diff PKGBUILD
 +
Index: PKGBUILD
 +
===================================================================
 +
--- PKGBUILD (révision 300688)
 +
+++ PKGBUILD (copie de travail)
 +
@@ -26,7 +26,8 @@
 +
 +
build() {
 +
  cd $pkgname
 +
-  ./configure --prefix=/usr --disable-static --libexecdir=/usr/lib
 +
+  export CXXFLAGS='-g -O0'
 +
+  ./configure --prefix=/usr --disable-static --libexecdir=/usr/lib --enable-debug-symbols=-gdwarf-2
 +
  sed -i -e 's/ -shared / -Wl,-O1,--as-needed\0/g' libtool
 +
  make
 +
}</pre>
  
::I still think that applications' specific method of changing accels should be mentioned in the application page itself. Into this page I'd leave just a reminder (i.e. "If this method doesn't work see application's wiki page for app specific file"). But I don't delete it anymore until somebody else tell us his opinion. [[User:4javier|4javier]] 20:35, 25 April 2011 (EDT)
+
2) rebuild js38 with debug enabled:
  
:::Perhaps update [[Nautilus]] and reference it? Perhaps simply add that article to the related articles? --[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 23:33, 6 September 2012 (UTC)
+
<pre>packages/js38/trunk$ svn diff PKGBUILD
 +
Index: PKGBUILD
 +
===================================================================
 +
--- PKGBUILD (révision 300681)
 +
+++ PKGBUILD (copie de travail)
 +
@@ -10,7 +10,7 @@
 +
license=(MPL)
 +
depends=(nspr gcc-libs readline zlib icu libffi)
 +
makedepends=(python2 libffi zip)
 +
-options=(!staticlibs)
 +
+options=(!staticlibs debug)
 +
source=(https://ftp.mozilla.org/pub/firefox/releases/${pkgver}esr/source/firefox-${pkgver}esr.source.tar.bz2
 +
        mozjs38-fix-tracelogger.patch
 +
        mozjs38-shell-version.patch</pre>
  
== Xmonad section ==
+
Once the gjs and js38-debug packages are installed and gnome-shell restarted (Alt+F2 + r), whenever gnome-shell crashes the debug symbols will be available.
  
I think xmonad section should be generalized for every other wm: openbox, fluxbox, ratpoison etc. Is there some gnome3 user who can test the method with other wm than xmonad? --[[User:4javier|4javier]] 05:40, 16 May 2011 (EDT)
+
After the crash:
 +
<pre>$ coredumpctl -1
 +
TIME                            PID  UID  GID SIG COREFILE  EXE
 +
Mon 2017-07-17 15:34:49 CEST  27368  1000  1000  11 present  /usr/bin/gnome-shell
 +
$ coredumpctl gdb 27368
 +
(gdb) bt
 +
#0  0x00007fbc7b997945 in js::GCMethods<JSObject*>::needsPostBarrier(JSObject*) (v=0x7fbc0a9548c0) at /usr/include/mozjs-38/js/RootingAPI.h:663
 +
#1  0x00007fbc7b997945 in JS::Heap<JSObject*>::set(JSObject*) (newPtr=0x0, this=0x254c260) at /usr/include/mozjs-38/js/RootingAPI.h:296
 +
#2  0x00007fbc7b997945 in JS::Heap<JSObject*>::operator=(JSObject* const&) (p=<optimized out>, this=0x254c260) at /usr/include/mozjs-38/js/RootingAPI.h:266
 +
#3  0x00007fbc7b997945 in GjsMaybeOwned<JSObject*>::reset() (this=0x254c250) at ./gjs/jsapi-util-root.h:267
 +
#4  0x00007fbc7b997945 in closure_clear_idle(void*) (data=0x254c220) at gi/closure.cpp:133
 +
#5  0x00007fbc79abd8c5 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
 +
#6  0x00007fbc79abdc88 in  () at /usr/lib/libglib-2.0.so.0
 +
#7  0x00007fbc79abdfa2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
 +
#8  0x00007fbc7b27508c in meta_run () at /usr/lib/libmutter-0.so.0
 +
#9  0x0000000000401ff7 in main ()</pre>
  
== Add link to official extensions site ==
+
I think this might be useful to be added to a dedicated section or to another page so that users can easily contribute traces to the gnome team.
 +
[[User:Fthiery|Fthiery]] ([[User talk:Fthiery|talk]]) 13:59, 17 July 2017 (UTC)
  
I think to add a link to [https://extensions.gnome.org/ extensions.gnome.org], also in order to easy manage the extensions in the browser from the [https://extensions.gnome.org/local/ /local] page. --[[User:Gimmy|Gimmy]] 05:22, 23 January 2012 (EST)
+
:+1. I suggest adding it to [[GNOME/Troubleshooting#Shell_freezes]]. It would be nice, if a respective expansion could also provide a corresponding gnome project link. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 12:12, 20 July 2017 (UTC)
:Link added, this probably deserves a section of its own now that extensions play such a vital role in GNOME. A future rewrite / restructure of this article may be needed. --[[User:Stefanwilkens|stefanwilkens]] ([[User talk:Stefanwilkens|talk]]) 23:52, 6 September 2012 (UTC)
 
  
== Remove systemd configuration from 'Some 'System Settings' no preserved' section ==
+
I added it to https://wiki.archlinux.org/index.php/GNOME/Troubleshooting#Shell_segfaults because i find it quite different to freezing [[User:Fthiery|Fthiery]] ([[User talk:Fthiery|talk]]) 15:26, 20 July 2017 (UTC)
  
I think that part of the 'Some 'System Settings' no preserved' section regarding switching to systemd should be removed and replaced with a link to systemd wiki. Systemd wiki explains migration more thoroughly and shows how to configure and administrate it.
+
::Yes, I agree. Cheers. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 14:56, 21 July 2017 (UTC)

Latest revision as of 14:56, 21 July 2017

GNOME applications blocking window manager keyboard shortcuts? Drawing over everything?

Seen on Fluxbox, using evince, totem, baobab.(as of 3.14.1-2, 3.14.1-1, 3.14.1-1, well, earlier) Makes these programs near-useless.Jasper1984 (talk) 15:31, 8 December 2014 (UTC)

I believe this is not just about GNOME, but all GTK+ and Qt applications [1] [2]. Haven't read through the reports, but it appears to be some flaw in Xorg. Not much we can do about this, so unless you want to discuss a workaround this can be closed. -- Alad (talk) 19:50, 8 December 2014 (UTC)
Can you confirm this with another toolkit than GTK3 ? -- Alad (talk) 17:35, 10 January 2015 (UTC)

GNOME and fontconfig settings

Since there isn't a section dedicated to fonts in GNOME 3 I was thinking about writing one, but I put it here first:

GNOME doesn't use the dpi settings set by xorg server to scale fonts, instead it uses a fixed dpi of 96 that cannot be changed unlike previous versions:

/* As we cannot rely on the X server giving us good DPI information, and
 * that we don't want multi-monitor screens to have different DPIs (thus
 * different text sizes), we'll hard-code the value of the DPI
 *
 * See also:
 * https://bugzilla.novell.com/show_bug.cgi?id=217790•
 * https://bugzilla.gnome.org/show_bug.cgi?id=643704
 */

The gnome-settings-daemon plugin xsettings relies on this hardcoded value for some calculations and there is currently no way of changing it beside customizing the code in abs. The dimension of text can be tweaked changing the text-scaling-factor (1.0 by default), using gnome-tweak-tool or editing the following key in dconf-editor:

org.gnome.desktop.interface.text-scaling-factor

The xsettings plugins will also merge some Xft values in the X resources db overwriting values set in .Xresources od .Xdefaults files. The defaults are:

Xft.antialias:	1
Xft.dpi:	96
Xft.hinting:	1
Xft.hintstyle:	hintmedium
Xft.lcdfilter:	lcddefault
Xft.rgba:	none

Some of those values can be changed using dconf-editor (org.gnome.settings-daemon.plugins.xsettings) or gnome-tweak-tool. It is possible to change this values using xrdb -merge ~/.Xresources after gnome is started but gnome will still use its values internally so it is not a good idea.

It is a good idea to configure your fonts.conf in a way consistent with the gnome settings otherwise, at least on my laptop, fonts will looks weird in some gnome apps.

The dpi setting of the Xserver can be changed to 96 following this guide, this way it will be the same for all applications, the drawback is that fonts might look too small or too big in other application if the real DPI of your monitor differs too much from 96.

For and LCD monitor it is a good idea to activate the lcd filter setting the following keys in dconf-editor:

org.gnome.settings-daemon.plugins.xsettings.antialiasing rgba
org.gnome.settings-daemon.plugins.xsettings.rgba-order rgb, bgr, vrgb or vbgr (as your monitor requires)

Since the lcdfilter is not designed to work together with autohinting it is a good idea to disable it also in fonts.conf. It is also a good idea to use the same hinting value as in your font.conf, the default in gnome is medium:

org.gnome.settings-daemon.plugins.xsettings.hinting medium

This values in fonts.conf will match the gnome settings:

<match target="font">
 <edit mode="assign" name="rgba"><const>rgb</const></edit>
 <edit mode="assign" name="autohint"><bool>false</bool></edit>
 <edit mode="assign" name="hinting"><bool>true</bool></edit>
 <edit mode="assign" name="hintstyle"><const>hintmedium</const></edit>
 <edit mode="assign" name="antialias"><bool>true</bool></edit>
 <edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit>
</match>

(to be finished, please comment or fix) —This unsigned comment is by Erm67 (talk) 23:58, 8 January 2012‎. Please sign your posts with ~~~~!

I think that info must be in Font configuration, linked from there if needed -- Kycok (talk) 10:57, 3 June 2014 (UTC)
Well, it is very GNOME specific and complex at the same time. I would vote for putting it into GNOME tips and crosslink it from GNOME#Fonts as well as from Font configuration. But first: Above contribution of Erm67 is a couple of years back. Does someone know whether the instructions still work like that? --Indigo (talk) 09:04, 10 November 2014 (UTC)
Update to note: GNOME tips was cleaned up removing GNOME content after I suggested above. It does not make sense to put these instructions there anymore. --Indigo (talk) 12:41, 15 January 2015 (UTC)

Natural scrolling

I can't get reverse natural scrolling on my trackpath to work (scroll with fingers in same direction as if it was a mouse wheel). I am happy to propose some text for the wiki if someone can tell me how to do it ... --Bronze (talk) 04:33, 26 February 2017 (UTC)

Is there not a natural scrolling setting under Settings -> Mouse & Touchpad that you can toggle? -- Chazza (talk) 09:57, 26 February 2017 (UTC)
i saw this with computers which have a keyboard with integrated touchpads like the logitech k400, and no mouse connected. not sure what makes gnome than display nothing ... --Soloturn (talk) 05:11, 1 April 2017 (UTC)

Getting traces of gnome-shell crashes

Gnome-shell uses javascript, which makes it hard to debug.

To enable debugging of extensions, it is necessary to

1) rebuild gjs with CXXFLAGS='-g -O0'

packages/gjs/trunk$ svn diff PKGBUILD 
Index: PKGBUILD
===================================================================
--- PKGBUILD	(révision 300688)
+++ PKGBUILD	(copie de travail)
@@ -26,7 +26,8 @@
 
 build() {
   cd $pkgname
-  ./configure --prefix=/usr --disable-static --libexecdir=/usr/lib
+  export CXXFLAGS='-g -O0'
+  ./configure --prefix=/usr --disable-static --libexecdir=/usr/lib --enable-debug-symbols=-gdwarf-2
   sed -i -e 's/ -shared / -Wl,-O1,--as-needed\0/g' libtool
   make
 }

2) rebuild js38 with debug enabled:

packages/js38/trunk$ svn diff PKGBUILD 
Index: PKGBUILD
===================================================================
--- PKGBUILD	(révision 300681)
+++ PKGBUILD	(copie de travail)
@@ -10,7 +10,7 @@
 license=(MPL)
 depends=(nspr gcc-libs readline zlib icu libffi)
 makedepends=(python2 libffi zip)
-options=(!staticlibs)
+options=(!staticlibs debug)
 source=(https://ftp.mozilla.org/pub/firefox/releases/${pkgver}esr/source/firefox-${pkgver}esr.source.tar.bz2
         mozjs38-fix-tracelogger.patch
         mozjs38-shell-version.patch

Once the gjs and js38-debug packages are installed and gnome-shell restarted (Alt+F2 + r), whenever gnome-shell crashes the debug symbols will be available.

After the crash:

$ coredumpctl -1
TIME                            PID   UID   GID SIG COREFILE  EXE
Mon 2017-07-17 15:34:49 CEST  27368  1000  1000  11 present   /usr/bin/gnome-shell
$ coredumpctl gdb 27368
(gdb) bt
#0  0x00007fbc7b997945 in js::GCMethods<JSObject*>::needsPostBarrier(JSObject*) (v=0x7fbc0a9548c0) at /usr/include/mozjs-38/js/RootingAPI.h:663
#1  0x00007fbc7b997945 in JS::Heap<JSObject*>::set(JSObject*) (newPtr=0x0, this=0x254c260) at /usr/include/mozjs-38/js/RootingAPI.h:296
#2  0x00007fbc7b997945 in JS::Heap<JSObject*>::operator=(JSObject* const&) (p=<optimized out>, this=0x254c260) at /usr/include/mozjs-38/js/RootingAPI.h:266
#3  0x00007fbc7b997945 in GjsMaybeOwned<JSObject*>::reset() (this=0x254c250) at ./gjs/jsapi-util-root.h:267
#4  0x00007fbc7b997945 in closure_clear_idle(void*) (data=0x254c220) at gi/closure.cpp:133
#5  0x00007fbc79abd8c5 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#6  0x00007fbc79abdc88 in  () at /usr/lib/libglib-2.0.so.0
#7  0x00007fbc79abdfa2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#8  0x00007fbc7b27508c in meta_run () at /usr/lib/libmutter-0.so.0
#9  0x0000000000401ff7 in main ()

I think this might be useful to be added to a dedicated section or to another page so that users can easily contribute traces to the gnome team. Fthiery (talk) 13:59, 17 July 2017 (UTC)

+1. I suggest adding it to GNOME/Troubleshooting#Shell_freezes. It would be nice, if a respective expansion could also provide a corresponding gnome project link. --Indigo (talk) 12:12, 20 July 2017 (UTC)

I added it to https://wiki.archlinux.org/index.php/GNOME/Troubleshooting#Shell_segfaults because i find it quite different to freezing Fthiery (talk) 15:26, 20 July 2017 (UTC)

Yes, I agree. Cheers. --Indigo (talk) 14:56, 21 July 2017 (UTC)