Bug#836232: sooperlooper: upon initialization, slgui fails an assertion with SetTitle

chris mckenzie kristopolous at yahoo.com
Wed Aug 31 20:20:28 UTC 2016


Package: sooperlooper
Version: 1.7.3~dfsg0-2
Severity: important

Dear Maintainer,

I'm using slgui on debian sid.  I have it running on jessie fine however
when starting it up, I'm getting:

----------8<--------------

ASSERT INFO:
../src/gtk/toplevel.cpp(1365): assert "(m_widget != NULL)" failed in SetTitle(): invalid frame

BACKTRACE:
[1] wxTopLevelWindowGTK::SetTitle(wxString const&)
[2] wxThreadHelperThread::Entry()
[3] wxThreadHelperThread::Entry()
[4] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const
[5] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[6] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[7] wxEvtHandler::TryHereOnly(wxEvent&)
[8] wxEvtHandler::ProcessEventLocally(wxEvent&)
[9] wxEvtHandler::ProcessEvent(wxEvent&)
[10] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[11] wxTimerImpl::SendEvent()
[12] g_main_context_dispatch
[13] g_main_loop_run
[14] gtk_main
[15] wxGUIEventLoop::DoRun()
[16] wxEventLoopBase::Run()
[17] wxAppConsoleBase::MainLoop()
[18] wxEntry(int&, wchar_t**)
[19] main
[20] __libc_start_main
[21] main

----------8<--------------

This reliably (100%) comes up after a few seconds.  This *looks* like perhaps a different window
manager would alleviate the problem, alas I've tried numerous ones, including more conventional ones
like lxde and xfce.

Also, I've ran this over a remote X connection to confirm that there's nothing GL related (I 
don't know why there would be). 

My jack stack on sid other than this seems to work ok.  The only other problem that this machine has had recently, is something dbus related ... when running notion or twm, I can't start up, notably qjackctl or qsynth - X locks up (but the cursor curiously still responds). I can get into detail upon what is causing this, but I think this problem is unrelated and I consider the dbus problem my own to fix.

If time permits I'll probably try to fix this myself ... but that actualizing that desire I'm going to say is unreliable. Thanks.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sooperlooper depends on:
ii  libasound2                        1.1.2-1
ii  libc6                             2.23-5
ii  libgcc1                           1:6.2.0-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-2
ii  liblo7                            0.28-5
ii  libncurses5                       6.0+20160625-1
ii  librubberband2                    1.8.1-6+b1
ii  libsamplerate0                    0.1.8-8
ii  libsigc++-2.0-0v5                 2.8.0-2
ii  libsndfile1                       1.0.25-10
ii  libstdc++6                        6.2.0-1
ii  libtinfo5                         6.0+20160625-1
ii  libwxbase3.0-0v5                  3.0.2+dfsg-2
ii  libwxgtk3.0-0v5                   3.0.2+dfsg-2
ii  libxml2                           2.9.4+dfsg1-1+b1

sooperlooper recommends no packages.

sooperlooper suggests no packages.

-- no debconf information



More information about the pkg-multimedia-maintainers mailing list