On 04/14/2014 02:52 PM, Chris Knadle wrote:
On Monday, April 14, 2014 12:30:40 RedOmen wrote:
On 04/14/2014 10:30 AM, Chris Knadle wrote:
On Sunday, April 13, 2014 20:58:35 redomen wrote:
Package: mumble
Version: 1.2.5-245-g221a5d7-1
Severity: normal
Dear Maintainer,

Everything was fine until a recent system update and now when running the
mumble client and selecting settings from the dropdown menu it always
crashes. If I delete my user config files and start clean I am able to
access settings but if I attempt to assign my push-to-talk key (my super
key) it crashes in the same place again.
I'm able to set a push-to-talk key, so I'm not able to reproduce this bug.
Sorry to hear that you're having trouble -- I'd like to try to narrow down
what's causing it.

What window manager / desktop environment are you using?

    -- Chris

--
Chris Knadle
chris.kna...@coredump.us
I'm using XFCE4.  I have no problems binding the super key in the window
manager settings although currently nothing is assigned to it.
Just a reminder: remember to CC 744...@bugs.debian.org concerning this bug.

Okay.  It looks like you're using Testing but have not included the Wheezy
(i.e. stable) repo; I've heard that that can cause some unusual bugs since
there are a few packages that only exist in Stable.  Also since you've got a
foreign architecture available (i386), double-check that you've got the amd64
mumble package loaded, not the i386 package.

I have an amd64 Debian Testing VM loaded, and just tested mumble
1.2.5-245-g221a5d7-1 in XFCE and was able to change the push-to-talk key.
I'm not able to make anything of the gdb output you included either, sorry to
say.

So the best suggestion I've got for starters is to add the Debian wheezy repo
and apt-get update + upgrade to see if that pulls in any missing packages.

   -- Chris

--
Chris Knadle
chris.kna...@coredump.us

I poked around in the mumble source and disabled the file system watcher 
in './src/mumble/GlobalShortcut_unix.cpp', rebuilt the client and now 
everything works normally for me again.  I guess if my devices change 
while mumble is running I'll just have to restart it.
--- GlobalShortcut_unix.old     2014-04-17 03:13:06.673746435 -0700
+++ GlobalShortcut_unix.cpp     2014-04-17 03:08:57.696720278 -0700
@@ -51,16 +51,16 @@

 #ifdef Q_OS_LINUX
        QString dir = QLatin1String("/dev/input");
- QFileSystemWatcher *fsw = new QFileSystemWatcher(QStringList(dir), this); - connect(fsw, SIGNAL(directoryChanged(const QString &)), this, SLOT(directoryChanged(const QString &)));
-       directoryChanged(dir);
+// QFileSystemWatcher *fsw = new QFileSystemWatcher(QStringList(dir), this); +// connect(fsw, SIGNAL(directoryChanged(const QString &)), this, SLOT(directoryChanged(const QString &)));
+//     directoryChanged(dir);

        if (qsKeyboards.isEmpty()) {
                foreach(QFile *f, qmInputDevices)
                        delete f;
                qmInputDevices.clear();

-               delete fsw;
+//             delete fsw;
qWarning("GlobalShortcutX: Unable to open any keyboard input devices under /dev/input, falling back to XInput");
        } else {
                return;


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to