Bug#349144: yakuake: console list at the bottom is badly displayed
Roberto Pariset
Version: 2.7.3-2
Severity: important
Hi.
When using yakuake I get a list of open consoles at the bottom of the
window. Now, it is very bad displayed, like if it was ruined or
something. In particular, it's almost impossible to tell which console
you are into at first glance (console1 or console2?). I am an amd64 user
and not really into kde, just in case it is of help. Greets,
Roberto
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=it_IT.UTF-8@euro, LC_CTYPE=it_IT.UTF-8@euro (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8@euro)
Versions of packages yakuake depends on:
ii kdelibs4c2a 4:3.5.0-3 core libraries for all KDE applica
ii konsole 4:3.5.0-4 X terminal emulator for KDE
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.2-7 GCC support library
ii libqt3-mt 3:3.3.5-3 Qt GUI Library (Threaded runtime v
ii libstdc++6 4.0.2-7 The GNU Standard C++ Library v3
yakuake recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ana Guerrero
Hi Roberto:
On Sat, Jan 21, 2006 at 11:33:32AM +0100, Roberto Pariset wrote:
> Package: yakuake
> Version: 2.7.3-2
> Severity: important
>
> Hi.
> When using yakuake I get a list of open consoles at the bottom of the
> window. Now, it is very bad displayed, like if it was ruined or
> something. In particular, it's almost impossible to tell which console
> you are into at first glance (console1 or console2?). I am an amd64 user
> and not really into kde, just in case it is of help. Greets,
Someone told me something like this in IRC (XFCE4 user if i recall
correctly), it looks like some dependency is missing but i need investigate
what is exactly.
It is not related to amd64 because i use yakuake at work (with KDE)
and it works fine.
Thanks for the bug report,
Ana
Cyril Brulebois
> Someone told me something like this in IRC (XFCE4 user if i recall
> correctly), it looks like some dependency is missing but i need
> investigate what is exactly.
Correct, that was under Xfce4. After some tests, it appears that having
yakuake running without having kdesktop running leads to this (I guess)
transparency problem. Possible workarounds are:
- (obviously) launch kdesktop, even from Xfce4 (or whatever WM/DE
you're running under)
- disable tab-bar by putting a "tabs=false" line in your configuration
file (~/.kde/share/config/yakuakerc)
It would be good to know (by asking upstream) whether this (strong IMHO)
dependency on kdesktop really makes sense, or whether this could be
avoided.
Cheers,
--
Cyril "KiBi" Brulebois
Roberto Pariset
> Correct, that was under Xfce4. After some tests, it appears that having
> yakuake running without having kdesktop running leads to this (I guess)
> transparency problem. Possible workarounds are:
> - (obviously) launch kdesktop, even from Xfce4 (or whatever WM/DE
> you're running under)
> - disable tab-bar by putting a "tabs=false" line in your configuration
> file (~/.kde/share/config/yakuakerc)
I can confirm this: with kdesktop it runs fine. By the way, I also get
some message like this on stderr:
Uh oh.. can't write data..
QLayout: Cannot add null widget to QVBoxLayout/unnamed
WARNING: DCOPReply<>: cast to 'QString' error
in case it matters...
I also found another problem, but I am not sure whether I should file
another bug or not. So here it is:
- open yakuake
- create another tab by cliccing on the [+] button
- use shift+right to move to the new tab
- use shift+left to move to the old tab
- close yakuake using the [x] button
- experience the crash :-S
All the best,
Rob
Cyril Brulebois
> I also found another problem, but I am not sure whether I should file
> another bug or not.
kind of KDE stuff.
> - open yakuake
> - create another tab by cliccing on the [+] button
> - use shift+right to move to the new tab
> - use shift+left to move to the old tab
> - close yakuake using the [x] button
> - experience the crash :-S
Reproducible on my side too. Signal 11.
I'm not sure I'll investigate on this one, because running yakuake
with a single tab and no tab-bar is sufficient for me, I use it as a
launcher (instead of xfrun4 for example).
Cheers,
--
Cyril Brulebois
Roberto Pariset
>>- open yakuake
>>- create another tab by cliccing on the [+] button
>>- use shift+right to move to the new tab
>>- use shift+left to move to the old tab
>>- close yakuake using the [x] button
>>- experience the crash :-S
>
> Reproducible on my side too. Signal 11.
>
> I'm not sure I'll investigate on this one, because running yakuake
> with a single tab and no tab-bar is sufficient for me, I use it as a
> launcher (instead of xfrun4 for example).
This happens with and without kdesktop running here... I think it's grave
that a program sigfaults this way :-/
As a launcher you could also use xfce4-minicmd-plugin :)
Greets,
Ana Guerrero
thanks
Hi Roberto, KiBi,
On Sat, Jan 28, 2006 at 10:49:47AM +0100, Roberto Pariset wrote:
> Cyril Brulebois ha scritto:
> >>- open yakuake
> >>- create another tab by cliccing on the [+] button
> >>- use shift+right to move to the new tab
> >>- use shift+left to move to the old tab
> >>- close yakuake using the [x] button
> >>- experience the crash :-S
> >
> > Reproducible on my side too. Signal 11.
> >
> > I'm not sure I'll investigate on this one, because running yakuake
> > with a single tab and no tab-bar is sufficient for me, I use it as a
> > launcher (instead of xfrun4 for example).
>
> This happens with and without kdesktop running here... I think it's grave
> that a program sigfaults this way :-/
>
Lovely upstream has fixed this bug \o/
It'll be fixed in the next upstream release.
Ana