What could cause "Failed to measure available space"

Detzi · 2020-02-18 20:44:04

Hey Folks,

i yesterday did setup my first arch Linux machine and am enjoining it so far.
Now i wanted to add git "GUI" support and both programs i tried so far crash when i try to clone a repo to my home directory /home/detzi/repo reporting:

giggle: Gtk-WARNING **: 21:19:37.503: Failed to measure available space: The specified location is not supported
gitg: Gtk-WARNING **: 21:35:40.430: Failed to measure available space: The specified location is not supported
Segmentation fault (core dumped)

my best bet is that i missed installing something but google wont tell me what that could be and rather points me to unrelated issues on different programs without solution.
My logs don't seem to have anything giggle or gitg related so i don't know how to start/solve this.

ls /var/log
audit btmp cups gdm lastlog pacman.log samba timeshift
boot.log clamav faillog journal old private tallylog wtmp

Can someone please point me to the right direction here?
Thanks in advance

cirrus · 2020-02-19 01:07:04

Hi Detzi
Welcome to the forums,

ls /var/log

shows us nothing of any significance, its the contents of log files that could help us help you.
I would advise all newcomers have a read of this https://wiki.archlinux.org/index.php/Co … ow_to_post following that advice will also help us to help you.
Regards

loqs · 2020-02-19 01:34:58

Also see coredump, particularly the section on examining a core dump.

Detzi · 2020-02-19 15:12:33

Thank you bot for your answers!
@cirrus:
i wanted to show you the content of my log directory to make clear that there is no log that seems relevant to me but if there is one that someone with more knowledge than me considered valuable, can be easily spotted. If i have violated the code of conduct please tell me what i did wrong so i can ask a more complete question next time. What i posted was my best effort to describe my problem as clear and complete as i could.

@loqs:
thanks for the hint with the core dump i should have spotted that myself..." coredumpctl list" returns:

[mr87@x1carbon ~]$ coredumpctl list
TIME                            PID   UID   GID SIG COREFILE  EXE
Mon 2020-02-17 19:24:50 CET    1879     0     0  11 error     /usr/lib/fprintd
Tue 2020-02-18 21:10:45 CET    2317  1000   985  11 present   /usr/bin/gitg
Tue 2020-02-18 21:11:24 CET    2389  1000   985  11 present   /usr/bin/gitg
Tue 2020-02-18 21:12:49 CET    2475  1000   985  11 present   /usr/bin/gitg
Tue 2020-02-18 21:16:25 CET    2603  1000   985  11 present   /usr/bin/gitg
Tue 2020-02-18 21:37:01 CET    3039  1000   985  11 present   /usr/bin/gitg
Wed 2020-02-19 15:43:09 CET    1214  1000   985  11 present   /usr/bin/gitg
Wed 2020-02-19 15:44:54 CET    1355  1000   985  11 present   /usr/bin/gitg

And when i understand the wiki correctly this should be the Dump you have pointed me to But i can't spot anything interesting in there.

[mr87@x1carbon ~]$ coredumpctl info 1355
           PID: 1355 (gitg)
           UID: 1000 (mr87)
           GID: 985 (users)
        Signal: 11 (SEGV)
     Timestamp: Wed 2020-02-19 15:44:54 CET (16min ago)
  Command Line: gitg
    Executable: /usr/bin/gitg
 Control Group: /user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
          Unit: user@1000.service
     User Unit: gnome-terminal-server.service
         Slice: user-1000.slice
     Owner UID: 1000 (mr87)
       Boot ID: e930900b7d2045f09150dbb42d7d55a0
    Machine ID: 04b7b73f53e34280a988564ab6c12b97
      Hostname: x1carbon
       Storage: /var/lib/systemd/coredump/core.gitg.1000.e930900b7d2045f09150dbb42d7d55a0.1355.1582123494000>
       Message: Process 1355 (gitg) of user 1000 dumped core.
                
                Stack trace of thread 1421:
                #0  0x00007fb20cd15e74 n/a (libgit2.so.28 + 0xb8e74)
                #1  0x00007fb20bfae182 http_parser_execute (libhttp_parser.so.2.9 + 0x4182)
                #2  0x00007fb20cd17391 n/a (libgit2.so.28 + 0xba391)
                #3  0x00007fb20cd19771 n/a (libgit2.so.28 + 0xbc771)
                #4  0x00007fb20cd1bb59 n/a (libgit2.so.28 + 0xbeb59)
                #5  0x00007fb20cd19f92 n/a (libgit2.so.28 + 0xbcf92)
                #6  0x00007fb20ccf6347 git_remote_fetch (libgit2.so.28 + 0x99347)
                #7  0x00007fb20cc88175 git_clone (libgit2.so.28 + 0x2b175)
                #8  0x00007fb20dacf3ff n/a (libgit2-glib-1.0.so.0 + 0x243ff)
                #9  0x00007fb20dcc0791 g_initable_new_valist (libgio-2.0.so.0 + 0xf3791)
                #10 0x00007fb20dcc084a g_initable_new (libgio-2.0.so.0 + 0xf384a)
                #11 0x00007fb20dac829a ggit_repository_clone (libgit2-glib-1.0.so.0 + 0x1d29a)
                #12 0x000055bce3dff28d n/a (gitg + 0x3428d)
                #13 0x00007fb20e863b45 n/a (libgitg-1.0.so.0 + 0x71b45)
                #14 0x00007fb20e697bb1 n/a (libglib-2.0.so.0 + 0x48bb1)
                #15 0x00007fb20d41d46f start_thread (libpthread.so.0 + 0x946f)
                #16 0x00007fb20e9b13d3 __clone (libc.so.6 + 0xff3d3)
                
                Stack trace of thread 1355:
                #0  0x00007fb20e9a6abf __poll (libc.so.6 + 0xf4abf)
                #1  0x00007fb20e6bb120 n/a (libglib-2.0.so.0 + 0x6c120)
                #2  0x00007fb20e6bb1f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                #3  0x00007fb20dc69dbe g_application_run (libgio-2.0.so.0 + 0x9cdbe)
                #4  0x000055bce3df1b35 gitg_main_main (gitg + 0x26b35)
                #5  0x00007fb20e8d9023 __libc_start_main (libc.so.6 + 0x27023)
                #6  0x000055bce3de708e _start (gitg + 0x1c08e)
                
                Stack trace of thread 1357:
                #0  0x00007fb20e9a6abf __poll (libc.so.6 + 0xf4abf)
                #1  0x00007fb20e6bb120 n/a (libglib-2.0.so.0 + 0x6c120)
                #2  0x00007fb20e6bc0c3 g_main_loop_run (libglib-2.0.so.0 + 0x6d0c3)
                #3  0x00007fb20dc26bc8 n/a (libgio-2.0.so.0 + 0x59bc8)
                #4  0x00007fb20e697bb1 n/a (libglib-2.0.so.0 + 0x48bb1)
                #5  0x00007fb20d41d46f start_thread (libpthread.so.0 + 0x946f)
                #6  0x00007fb20e9b13d3 __clone (libc.so.6 + 0xff3d3)
                
                Stack trace of thread 1358:
                #0  0x00007fb20e9a6abf __poll (libc.so.6 + 0xf4abf)
                #1  0x00007fb20e6bb120 n/a (libglib-2.0.so.0 + 0x6c120)
                #2  0x00007fb20e6bb1f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                #3  0x00007fb208454e5e n/a (libdconfsettings.so + 0x4e5e)
                #4  0x00007fb20e697bb1 n/a (libglib-2.0.so.0 + 0x48bb1)
                #5  0x00007fb20d41d46f start_thread (libpthread.so.0 + 0x946f)
                #6  0x00007fb20e9b13d3 __clone (libc.so.6 + 0xff3d3)
                
                Stack trace of thread 1356:
                #0  0x00007fb20e9a6abf __poll (libc.so.6 + 0xf4abf)
                #1  0x00007fb20e6bb120 n/a (libglib-2.0.so.0 + 0x6c120)
                #2  0x00007fb20e6bb1f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
                #3  0x00007fb20e6bb242 n/a (libglib-2.0.so.0 + 0x6c242)
                #4  0x00007fb20e697bb1 n/a (libglib-2.0.so.0 + 0x48bb1)
                #5  0x00007fb20d41d46f start_thread (libpthread.so.0 + 0x946f)
                #6  0x00007fb20e9b13d3 __clone (libc.so.6 + 0xff3d3)
                
                Stack trace of thread 1424:
                #0  0x00007fb20e9abf8d syscall (libc.so.6 + 0xf9f8d)
                #1  0x00007fb20e66c11b g_cond_wait_until (libglib-2.0.so.0 + 0x1d11b)
                #2  0x00007fb20e6e9f63 n/a (libglib-2.0.so.0 + 0x9af63)
                #3  0x00007fb20e6ea154 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x9b154)
                #4  0x00007fb20e69102a n/a (libglib-2.0.so.0 + 0x4202a)
                #5  0x00007fb20e697bb1 n/a (libglib-2.0.so.0 + 0x48bb1)
                #6  0x00007fb20d41d46f start_thread (libpthread.so.0 + 0x946f)
                #7  0x00007fb20e9b13d3 __clone (libc.so.6 + 0xff3d3)

when i use "git clone" from the cmd line it works just fine "rabbitvcs" and "github desktop" do also work.

Last edited by Detzi (2020-02-19 15:34:11)

seth · 2020-02-20 14:45:45

That's a gtk warning (i believe from the dialog positioning code) - are you running an xwayland client in a wayland session?

It's unlikely the cause for the gitg coredump.

Detzi · 2020-02-20 16:26:59

Hey @Seth
i am quite sure that i am not running wayland.
When i installed arch i ran:

pacman -S xorg-server xorg-xinit --noconfirm

and use the default drivers for intel integrated into the "xorg-server" package. "echo $XDG_SESSION_TYPE" returns:

[mr87@x1carbon ~]$ echo $XDG_SESSION_TYPE
x11

and "env | grep -i wayland" returns nothing. When i understand the wiki correctly i use "xwayland" only when i have installed wayland?

Now that you mention it...i until now thought that this was a warning referring to my disk space but on second thought that sounds like gtk cant measure display space to arrrange its size accordingly.
That does make it very strange thou, why would it quit cloning the repo and then crash.

With that in mind i started "gitg" and as soon as i open the "clone" dialog i get the

(gitg:3142): Gtk-WARNING **: 17:23:29.437: Failed to measure available space: The specified location is not supported

on the terminal. But the program has not crashed, so you are right the "warning" is unrelated to the crash and the coredump.

loqs · 2020-02-20 17:41:03

Once libgit2 1:0.99.0-2 has moved out of staging you could test if the update has fixed the issue. If not a backtrace with debug symbols may help.

peT · 2020-03-12 17:36:28

I opened an issue upstream for this: https://gitlab.gnome.org/GNOME/gtk/issues/2509

Arch Linux

#1 2020-02-18 20:44:04

What could cause "Failed to measure available space"

#2 2020-02-19 01:07:04

Re: What could cause "Failed to measure available space"

#3 2020-02-19 01:34:58

Re: What could cause "Failed to measure available space"

#4 2020-02-19 15:12:33

Re: What could cause "Failed to measure available space"

#5 2020-02-20 14:45:45

Re: What could cause "Failed to measure available space"

#6 2020-02-20 16:26:59

Re: What could cause "Failed to measure available space"

#7 2020-02-20 17:41:03

Re: What could cause "Failed to measure available space"

#8 2020-03-12 17:36:28

Re: What could cause "Failed to measure available space"

Board footer