Quassel Client won't start with recent updates (3/30/2014)

[JaSauders]

I'm running Quassel Client on an Ubuntu 14.04 laptop, along with Quassel Core on my Ubuntu 12.04.4 server. My client machine is running Quassel Client from the standard trusty repos. This morning I checked for updates and acquired quite a number of them. Following a restart, Quassel Client will not start. I can see the processes populating in System Monitor and I can kill them accordingly, but Quassel Client itself just never actually runs, even following a reboot.

I also removed my ~/.config/quassel-irc.org folder in an effort to reset the settings, but no change.

Thank you for your time and efforts!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: quassel-client (not installed)
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 30 14:53:07 2014
InstallationDate: Installed on 2014-03-19 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
SourcePackage: quassel
UpgradeStatus: No upgrade log present (probably fresh install)

[JaSauders (jasauders)]

Once I submitted the bug I noticed this line in the automatically generated output above.

Package: quassel-client (not installed)

I do apologize, I actually installed quassel-client-qt4 but accidentally ran the ubuntu-bug apport against quassel-client. If any additional information is needed that might be missing due to my goof up please let me know and I'd be happy to provide that information.

Thanks again!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ronald Kinard (furyhunter)]

Noticing some inconsistent behaviors between my 14.04 installations -- on my desktop, the `quassel-client` package runs fine, but `quassel-client-qt4` does not. On my laptop, neither work.

Both start up fine and seem to connect to the core, but don't show a window at all. Here's what appears in stdout:

No DockManager available
Legacy core detected, switching to compatibility mode
Using the legacy protocol...
Starting encryption...
...

[JaSauders (jasauders)]

With my issue in particular, I just reinstalled 14.04 since the laptop I was running 14.04 on at the time was a spare unit. Once I reinstalled, it was fine. Prior to reinstalling, I wiped everything in my home directory including the hidden items; no change.

Sorry it doesn't really help, but given the fact another user reported similar weirdness, it at least confirms that I'm not crazy. :P

[Harald Sitter (apachelogger)]

Please check that the client windows is not minimized, supposedly there's something wrong in the config that makes the window not *visually* appear, which would for example be the window being minimized without you realizing it.

[Charles Kerr (charlesk)]

Thanks for reporting this bug and helping make Ubuntu better!

Judging from the side comments about Quassel in bug #1299738, I believe the underlying problem is bug #1301192. So, I'm marking this ticket as a duplicate of the latter bug.

[Maciej Wisniowski (pigletto-gmail)]

Bug #1301192 is marked as fixed but even though I've installed latest phonon-backend-gstreamer1.0 package I'm still not able to use Quassel client. Doesn't matter if it's quassel-client-qt4 or quassel-client. Both are starting in the background not showing any icon etc in Unity

[Scott Kitterman (kitterman)]

If it's a problem specific to the Unity environment, there's not much we can
do. Upstream doesn't support Unity. There might be something they can do to
address it. It works fine in KDE. I don't know what Unity is doing different
that might break packages like this.

[Scott Kitterman (kitterman)]

I don't think it's a duplicate of the other bug in any case.

[Andrew Starr-Bochicchio (andrewsomething)]

As Harold said, please check that the client windows is not minimized.

I just installed this under Unity and it works as expected out of the box. The issue seems to only happen if you enable UseSystemTrayIcon and MinimizeOnClose. To be able to access the window once this has been done, remove the following settings from ~/.config/quassel-irc.org/quasselclient.conf

MainWinHidden=true
UseSystemTrayIcon=true
MinimizeOnClose=true

Though all that's just a work around. Installing quassel-client pulls in libindicate-qt1, so the tray icon should work. It looks like this is upstream bug #1269 which already has a patch attached:

http://bugs.quassel-irc.org/issues/1269

[Daniel Albers (al)]

The proposed fix was committed upstream.

[Scott Kitterman (kitterman)]

On Tuesday, August 05, 2014 10:48:17 you wrote:
> The proposed fix was committed upstream.

What commit?

[Daniel Albers (al)]

https://github.com/quassel/quassel/commit/3939820389d995f56a073fc1d54ab245c6558312

[skimo (bkufo)]

Thanks for the solution. My machine was fixed by editing the ~/.config/quassel-irc.org/quasselclient.conf so that the MainWinHidden=true was changed to ‘false’. That was already mentioned above, but i think that another mention wouldn't hurt, since i had been looking for this fix for quite a few months now. Thanks : )

[Rick Harris (rickfharris)]

That committed upstream fix was reverted due to some other dbus problems.

Still tracking re-opened Quassel bug at http://bugs.quassel-irc.org/issues/1269