Segfault on file open dialog. #4275

enp2s0 · 2018-03-26T00:05:16Z

When clicking the open file button, lmms crashes with a segfault.

This is the first run of a fresh build of lmms.

Build Instructions

git clone --recursive https://github.com/LMMS/lmms.git
cd lmms
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=./ -DWANT_QT5=ON
make -j6
./lmms   # <-- This segfaults!

Output

[nbrecht@nbrecht-desktop build]$ ./lmms
VST sync support disabled in your configuration
Segmentation fault (core dumped)

Backtrace

nbrecht@nbrecht-desktop build]$ gdb ./lmms
GNU gdb (GDB) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./lmms...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/nbrecht/Exec/lmms/build/lmms 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe8df0700 (LWP 12476)]
[New Thread 0x7fffddfd3700 (LWP 12477)]
[New Thread 0x7fffdd7d2700 (LWP 12478)]
[New Thread 0x7fffd5cf9700 (LWP 12479)]
[New Thread 0x7fffd5168700 (LWP 12480)]
[New Thread 0x7fffd4967700 (LWP 12481)]
[New Thread 0x7fffce1ff700 (LWP 12482)]
VST sync support disabled in your configuration
[New Thread 0x7fff9ee94700 (LWP 12483)]
[Thread 0x7fff9ee94700 (LWP 12483) exited]
[New Thread 0x7fff9ee94700 (LWP 12484)]
[New Thread 0x7fff9e693700 (LWP 12485)]
[New Thread 0x7fff9de92700 (LWP 12486)]
[New Thread 0x7fff9cfd0700 (LWP 12488)]
[New Thread 0x7fff83fff700 (LWP 12489)]
[New Thread 0x7fff83027700 (LWP 12490)]
[New Thread 0x7fff8261c700 (LWP 12491)]

Thread 1 "lmms" received signal SIGSEGV, Segmentation fault.
0x00007fffe3291f07 in gtk_list_box_get_selected_row () from /usr/lib/libgtk-3.so.0
(gdb) bt
#0  0x00007fffe3291f07 in gtk_list_box_get_selected_row () at /usr/lib/libgtk-3.so.0
#1  0x00007fffe32e805b in  () at /usr/lib/libgtk-3.so.0
#2  0x00007fffdfa0a1c8 in ffi_call_unix64 () at /usr/lib/libffi.so.6
#3  0x00007fffdfa09c2a in ffi_call () at /usr/lib/libffi.so.6
#4  0x00007fffe28ec453 in g_cclosure_marshal_generic () at /usr/lib/libgobject-2.0.so.0
#5  0x00007fffe28ebc2d in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#6  0x00007fffe28ffbb0 in  () at /usr/lib/libgobject-2.0.so.0
#7  0x00007fffe2908746 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#8  0x00007fffe290965c in g_signal_emit_by_name () at /usr/lib/libgobject-2.0.so.0
#9  0x00007fffe26cf240 in  () at /usr/lib/libcloudproviders.so.0
#10 0x00007fffe26cfca2 in  () at /usr/lib/libcloudproviders.so.0
#11 0x00007fffe0ef118c in  () at /usr/lib/libgio-2.0.so.0
#12 0x00007fffe0ef1e57 in  () at /usr/lib/libgio-2.0.so.0
#13 0x00007fffe0f23913 in  () at /usr/lib/libgio-2.0.so.0
#14 0x00007fffe0ef118c in  () at /usr/lib/libgio-2.0.so.0
#15 0x00007fffe0ef11c9 in  () at /usr/lib/libgio-2.0.so.0
#16 0x00007ffff0f0e2c6 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#17 0x00007ffff0f0e6a1 in  () at /usr/lib/libglib-2.0.so.0
#18 0x00007ffff0f0e72e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#19 0x00007ffff42b7241 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#20 0x00007fffec0b0482 in  () at /usr/lib/libQt5XcbQpa.so.5
#21 0x00007ffff425932b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#22 0x00007ffff76a969b in QDialog::exec() () at /usr/lib/libQt5Widgets.so.5
#23 0x0000555555733356 in MainWindow::openProject() ()
#24 0x00007ffff428b616 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#25 0x00007ffff75a7b03 in QAbstractButton::clicked(bool) () at /usr/lib/libQt5Widgets.so.5
#26 0x00007ffff75a7d1c in  () at /usr/lib/libQt5Widgets.so.5
#27 0x00007ffff75a915c in  () at /usr/lib/libQt5Widgets.so.5
#28 0x00007ffff75a935e in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5
#29 0x00007ffff768f6ab in QToolButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5
#30 0x00007ffff74f2188 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#31 0x00007ffff768f745 in QToolButton::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#32 0x00007ffff74b1fec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#33 0x00007ffff74b9f41 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#34 0x00007ffff425acf0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#35 0x00007ffff74b8eca in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /usr/lib/libQt5Widgets.so.5
#36 0x00007ffff750d949 in  () at /usr/lib/libQt5Widgets.so.5
#37 0x00007ffff7510060 in  () at /usr/lib/libQt5Widgets.so.5
#38 0x00007ffff74b1fec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#39 0x00007ffff74b99c6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#40 0x00007ffff425acf0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#41 0x00007ffff47ce434 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5
#42 0x00007ffff47cff86 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5
#43 0x00007ffff47a729c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#44 0x00007fffec0b048d in  () at /usr/lib/libQt5XcbQpa.so.5
#45 0x00007ffff425932b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#46 0x00007ffff4262728 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#47 0x000055555562c741 in main ()

OS

[nbrecht@nbrecht-desktop build]$ uname -a
Linux nbrecht-desktop 4.15.12-1-ARCH #1 SMP PREEMPT Wed Mar 21 15:14:56 UTC 2018 x86_64 GNU/Linux

If any other info is needed I will provide it.

The text was updated successfully, but these errors were encountered:

enp2s0 · 2018-03-26T02:51:08Z

The recent files drop-down works fine, however, both File -> Open and the Open Project button segfault.

enp2s0 · 2018-03-26T03:03:27Z

I have just noticed that File -> Export crashes as well. Command line export works fine.

enp2s0 · 2018-03-26T04:26:36Z

This seems to be an issue affecting all file dialogs; could be a issue with Qt though and not lmms.

tresf · 2018-03-26T04:45:24Z

Shot in the dark.... https://bbs.archlinux.org/viewtopic.php?id=121360.

From what I'm reading there are some buggy gtk themes which may be the culprit as well as some root Qt5 bugs. The crash is very clearly gtk rooted which suggests Gnome, XFCE, etc is rendering some of the artwork when Qt loads these common dialog boxes but that's still speculative.

I also assume this same symptom occurs with the AppImage (https://lmms.io/download/#linux)? We build with a backport of the latest Qt5 (e.g. 5.9 or higher) so if a particular bug has been resolved along the way the AppImage would benefit from this.

Here's one that sounds very similar in description (unresolved). Since it's against GTK2, it's not relevant to your setup (as your backtrace says you're on GTK3):
https://bugreports.qt.io/browse/QTBUG-48263?jql=project%20%3D%20QTBUG%20AND%20text%20~%20gtk

Something a bit unique about our theme is that we theme most of our own common dialog boxes, so if you hit a theming bug it may be specific to Qt apps that override the default Qt theme. I'm not aware of any others off-hand although one Qt app that uses the default theme is Qt Linguist if you can baseline test against that.

enp2s0 · 2018-03-26T10:43:39Z

I'm starting to think my Qt/GTK installation is broken...

The AppImage fails to start at all.

[nbrecht@nbrecht-desktop ~]$ Downloads/lmms-current.AppImage 
Carla appears to be installed on this system at /usr/lib[64]/carla so we'll use it.
Jack appears to be installed on this system, so we'll use it.
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.
/tmp/.mount_lmms-c4JEPtH/AppRun: line 23: 24826 Aborted                 (core dumped) QT_X11_NO_NATIVE_MENUBAR=1 $DIR/usr/bin/lmms.real "$@"

tresf · 2018-03-26T12:28:57Z

Can you try this one and see if it segfaults? The version from our download page had some linking errors with Jack which should now be resolved . #4094

https://github.com/tresf/lmms/releases/download/v1.2.0-rc4/lmms-1.2.0-rc4.207-linux-x86_64.AppImage

enp2s0 · 2018-03-26T18:57:10Z

If it matters, I'm running cinnamon as my DE. This could be an issue with gfx drivers, I recently did system update pacman -Syyu and didn't reboot, the proprietary nvidia drivers sometime cause random problems after update.

tresf · 2018-03-26T19:34:46Z

@noahb01 did the second AppImage segfault in the same fashion?

enp2s0 · 2018-03-27T02:30:14Z

Yup. Same error...

[nbrecht@nbrecht-desktop ~]$  ./Downloads/lmms-1.2.0-rc4.207-linux-x86_64.AppImage 
Carla appears to be installed on this system at /usr/lib[64]/carla so we'll use it.
Jack appears to be installed on this system, so we'll use it.
This application failed to start because it could not find or load the Qt platform plugin "xcb".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.
/tmp/.mount_lmms-1EuXUkC/AppRun: line 23: 29413 Aborted                 (core dumped) QT_X11_NO_NATIVE_MENUBAR=1 $DIR/usr/bin/lmms.real "$@"

tresf · 2018-03-27T02:33:25Z

Last hack before I give up... what if you do export LIBGL_ALWAYS_SOFTWARE=1; ? I had to do this in VirtualBox to avoid some crashes.

enp2s0 · 2018-03-27T02:39:02Z

This could be a Qt path error...

[nbrecht@nbrecht-desktop ~]$ ./Downloads/lmms-1.2.0-rc5-linux-x86_64.AppImage 
Carla appears to be installed on this system at /usr/lib[64]/carla so we'll use it.
Jack appears to be installed on this system, so we'll use it.
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.
/tmp/.mount_lmms-1mvLk7O/AppRun: line 23:  1005 Aborted                 (core dumped) QT_X11_NO_NATIVE_MENUBAR=1 $DIR/usr/bin/lmms.real "$@"

This application failed to start because it could not find or load the Qt platform plugin "xcb" in "".

I know xcb is installed:

[nbrecht@nbrecht-desktop ~]$ pacman -Ss libxcb
extra/libxcb 1.13-1 [installed]
    X11 client-side library
multilib/lib32-libxcb 1.13-1 [installed]
    X11 client-side library (32-bit)

export LIBGL_ALWAYS_SOFTWARE=1; doesn't fix anything; same error.

Anyways, even if the AppImage is broken for me, what could be causing the file-dialog segfault, the original problem?

Also, I have tried rebooting/reloading the nvidia drivers; no effect.

tresf · 2018-03-27T02:46:45Z

Most what I find online points to either missing Qt libraries or mismatched Qt libraries.
https://stackoverflow.com/q/17106315/3196753

I'm not sure what's causing this. We've tested our AppImage on Manjaro back in December without any issues.

enp2s0 · 2018-03-27T02:47:00Z

[nbrecht@nbrecht-desktop ~]$ ldd /usr/lib/libxcb.so
	linux-vdso.so.1 (0x00007ffe2ff75000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f01af155000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f01aef4f000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f01aeb98000)
	/usr/lib64/ld-linux-x86-64.so.2 (0x00007f01af582000)

This could be a problem with my system and not lmms. Should liux-vdso.so.6 point to something?
Shouldn't the AppImage contain all depenendcies though?

enp2s0 · 2018-03-27T02:58:04Z

Here's something interesting:
If you download/build from source, the first time you run it it works fine. As soon as you close it and run it again, file-dialog windows segfault.

enp2s0 · 2018-03-27T03:02:33Z

It works fine as well if you rm .lmmsrc.xml and run again.

tresf · 2018-03-27T03:13:27Z

.lmmsrc.xml does a few things, but in regards to those dialogs, it sets up the default ~/lmms path.

Why that would affect the common dialog boxes is unknown to me.

I suppose you could try to move the default path of ~/lmms elsewhere as a troubleshooting step. I'm at a loss.

Note, I did find an obscure issue with Arch and the cloud providers plugin, but the backtrace is quite a bit different. https://bbs.archlinux.org/viewtopic.php?id=232172

enp2s0 · 2018-03-27T03:38:00Z

I have a feeling that the config window that opens on first launch does some setup code that isnt normally done, thus preventing the segfault. Once .lmmrc.xml is created, the config window dosen't open at launch and something isn't fully set up.

Update!!
If you open lmms and immediately go to Edit -> Settings -> LMMS WORKING DIRECTORY and open the file picker there, you will be able to use the Open File button without a segfault. You don't even need to change the directory, just open the file picker and press OK.

enp2s0 · 2018-03-27T03:38:17Z

Oops wrong button

tresf · 2018-03-27T03:48:54Z

Yeah that's not the themed dialog, that's the native one per this comment earlier...

Something a bit unique about our theme is that we theme most of our own common dialog boxes, so if you hit a theming bug it may be specific to Qt apps that override the default Qt theme. I'm not aware of any others off-hand although one Qt app that uses the default theme is Qt Linguist if you can baseline test against that.

Here's the dialog you're describing on Mac for example:

Versus the File > Open dialog:

enp2s0 · 2018-03-27T03:52:30Z

Yes. My point is, by manually setting the working dir (either by rming .lmmsrc.xml and having lmms make it at launch or by manually setting it) you avoid segfaults even in the themed dialogs! For example, the File->Open dialog dosen't segfault after opening the non-themed dialog in Settings and clicking OK

enp2s0 · 2018-03-27T03:56:07Z

It comes down to this:

Themed file boxes do not segfault if you open a non-themed box first. After a non-themed box has been opened, themed boxes work without issue.

tresf · 2018-03-27T04:07:21Z

Here's the custom FileDialog code if you want to hack at it...

lmms/src/gui/dialogs/FileDialog.cpp

Line 42 in 32f07ac

setOption( QFileDialog::DontUseNativeDialog );

.

For example, you may be able to get a bit further by commenting out:

setOption( QFileDialog::DontUseNativeDialog );

The code is pretty simple. I'm not sure exactly what could cause a crash inside it. Some more information on the Qt class that is used: http://doc.qt.io/qt-5/qfiledialog.html

enp2s0 · 2018-03-27T04:11:05Z

Commenting it out stops the segfault and everything works fine. I still don't know why it fails with the custom theme.

tresf · 2018-03-27T04:16:02Z

Hmm... https://bugs.archlinux.org/task/57984

enp2s0 · 2018-03-27T04:17:46Z

Yup -- That's this bug.

Can confirm that opening a non themed dialog stops segfaults:

	QString new_dir = FileDialog::getExistingDirectory( this,
				tr( "Dummy dialog for testing" ), "/usr/share" );
	setOption( QFileDialog::DontUseNativeDialog );

Adding this code before setOption() opens 2 boxes, one unthemed and then one themed. Neither segfaults.

enp2s0 · 2018-03-27T04:22:29Z

If this is a GTK bug and not a LMMS bug, should we just close this issue and disable themed file boxes until it's fixed?

tresf · 2018-03-27T04:26:06Z

If this is a GTK bug and not a LMMS bug, should we just close this issue and disable themed file boxes until it's fixed?

If revering GTK fixes it, yes, we'd be inclined to close this out as upstream/wontfix.

enp2s0 · 2018-03-27T04:34:46Z

Source of getExistingDirectory()

QString QFileDialog::getExistingDirectory(QWidget *parent,
                                          const QString &caption,
                                          const QString &dir,
                                          Options options)
{
    const QStringList schemes = QStringList(QStringLiteral("file"));
    const QUrl selectedUrl = getExistingDirectoryUrl(parent, caption, QUrl::fromLocalFile(dir), options, schemes);
    return selectedUrl.toLocalFile();
}

And setOption()

void QFileDialog::setOption(Option option, bool on)
{
    const QFileDialog::Options previousOptions = options();
    if (!(previousOptions & option) != !on)
        setOptions(previousOptions ^ option);
}

Considering that dependencies can be difficult on Arch and that I've already had to reinstall one Arch box this week due to messed up dependencies, I'm not going to try and downgrade GTK on my system to test this. However, this definitely seems like a problem with either GTK or QT. (There are no segfaults if you compile with qt4 instead of qt5...)

For now though, couldn't we just disable the custom theming on the file boxes?

tresf · 2018-03-27T04:56:45Z

For now though, couldn't we just disable the custom theming on the file boxes?

Theoretically, yes but we generally don't code workarounds to a specific platform unless it's something we can detect at runtime. I guess it would depend on the scope of this bug (which will naturally grow the longer that it goes un-patched).

enp2s0 · 2018-03-28T00:39:25Z

Considering that this is an upstream Qt/GTK bug and that it seems to only affect me, I'm closing this issue.

If it causes trouble for anyone else, the current workarounds are:

Open a non-themed file dialog before opening any themed ones. This needs to be done every time you launch lmms.
Comment out setOption( QFileDialog::DontUseNativeDialog ); in lmms/src/gui/dialogs/FileDialog.cpp and compile from source; this is a permanent fix but removes the custom theme from all file dialogs. (Not a big deal IMO, it dosen't affect usage or performance in any way and most people aren't interacting with a FileDialog that often anyway.)

If anyone finds a real fix to this issue, feel free to reopen it/make a PR to fix it.

tresf · 2018-04-02T03:24:42Z

@noahb01... @Wallacoloo was kind enough to dig into this one and found #4280 which appears to be a bug with the utility we use for packaging.

Can you test this AppImage and let us know if it fixes the segfault? Thanks @Wallacoloo for the research. https://github.com/tresf/lmms/releases/download/v1.2.0-rc5/lmms-1.2.0-rc5.43-linux-x86_64.AppImage

Edit: On second thought... Due to the history and nature of this bug there's a good chance these two are unrelated entirely and that the new AppImage won't fix anything... I'll wait for some feedback. :)

Wallacoloo · 2018-04-02T03:41:09Z

The new AppImage fixes the file chooser crash for me on Arch (likely because it bundles its own version of some Qt libraries). My setup is probably not identical though (e.g. running Wayland, not X11), so having confirmation would be a plus.

enp2s0 · 2018-04-02T04:54:40Z

The AppImage loads successfully and does not crash with the file-dialogs. It does, however, fail to find the LADSPA plugins Limiter and Reverb (used in the project file I used to test the dialog; they load fine in 1.2.0-rc5.277 compiled from source)

tresf · 2018-04-02T04:56:57Z

@noahb01 which limiter? I threw that AppImage together in a bit of a hurry, but the LADSPA stuff should all build as normal I'm not sure what would have broken that on my end.

tresf · 2018-04-02T05:01:32Z

There's a bit of a search-path bug with the LADSPA stuff too. For example... calf.so has drastically changed their codebase and dropped entirely the LADSPAv1 specification so it's incompatible with LMMS now. We bundle our own, but if yours isn't working you may be picking up a system version instead. We're fixing this in 1.3.0 by forking and renaming the file to veal.so, but that won't happen in 1.2.0 unless someone backports the patches.

Edit: We may still be able to improve the search order for 1.2.0 to circumvent this bug.

More information here: #3942

enp2s0 · 2018-04-02T11:33:44Z

The error:

The missing plugin is a Limiter.

However, the plugin is listed in the plugin browser.

This is what happens on project load. This occurs for all projects, but only those 2 plugins. (Could be because I prefer using LMMS native plugins and those are the only 2 LADSPA plugins used.) The plugins do indeed not load and have no effect on the sound.

zonkmachine · 2018-04-02T11:41:28Z

This occurs for all projects, but only those 2 plugins.

Does this also happens with newly created projects (created on this AppImage)?

Could be because I prefer using LMMS native plugins and those are the only 2 LADSPA plugins used

Care to test with other plugins?

zonkmachine · 2018-04-02T11:57:57Z

they load fine in 1.2.0-rc5.277 compiled from source)

That's on master right?

enp2s0 · 2018-04-02T11:59:19Z

It's on master, compiled from source with qt5.

tresf · 2018-04-02T14:12:05Z

@noahb01 that makes more sense. Master has the veal.so patch. Projects created with master are not backwards compatible with stable-1.2.

If you need to, you can lmms -d myproject.mmpz > myproject_uncompressed.mmp and replace instances of veal with calf and it should load again in stable-1.2. This is as a result of #3942 actually. We had to rename that library and there's no easy way to provide retroactive compatibility.

NuLogicSystems · 2018-04-13T16:08:48Z

The new appimage above (lmms-1.2.0-rc5.43-linux-x86_64.AppImage) fixed this crash for me as well under Netrunner Rolling (Manjaro).

enp2s0 closed this as completed Mar 27, 2018

enp2s0 reopened this Mar 27, 2018

tresf added the won't fix label Mar 27, 2018

tresf added the upstream label Mar 27, 2018

enp2s0 closed this as completed Mar 28, 2018

Wallacoloo mentioned this issue Mar 31, 2018

Incompatibility between AppImage's libfreetype.so.6 and system's libfontconfig.so #4280

Closed

NuLogicSystems mentioned this issue Apr 13, 2018

Package request "AppImageLauncher" netrunner-rolling/2018.01#56

Closed

Segfault on file open dialog. #4275

Segfault on file open dialog. #4275

Comments

enp2s0 commented Mar 26, 2018

enp2s0 commented Mar 26, 2018

enp2s0 commented Mar 26, 2018

enp2s0 commented Mar 26, 2018

tresf commented Mar 26, 2018

enp2s0 commented Mar 26, 2018

tresf commented Mar 26, 2018

enp2s0 commented Mar 26, 2018

tresf commented Mar 26, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018 • edited Loading

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 27, 2018

tresf commented Mar 27, 2018

enp2s0 commented Mar 28, 2018

tresf commented Apr 2, 2018 • edited Loading

Wallacoloo commented Apr 2, 2018

enp2s0 commented Apr 2, 2018

tresf commented Apr 2, 2018

tresf commented Apr 2, 2018 • edited Loading

enp2s0 commented Apr 2, 2018 • edited Loading

zonkmachine commented Apr 2, 2018

zonkmachine commented Apr 2, 2018

enp2s0 commented Apr 2, 2018

tresf commented Apr 2, 2018

NuLogicSystems commented Apr 13, 2018

enp2s0 commented Mar 27, 2018 •

edited

Loading

tresf commented Apr 2, 2018 •

edited

Loading

tresf commented Apr 2, 2018 •

edited

Loading

enp2s0 commented Apr 2, 2018 •

edited

Loading