[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#998203: marked as done (yakuake's icon does not come in mate notification area)

Your message dated Wed, 24 Aug 2022 08:41:52 +0200
with message-id <2843069.e9J7NaK4W3@odyx.org>
and subject line Re: Bug#998203: yakuake's icon does not come in mate notification area
has caused the Debian Bug report #998203,
regarding yakuake's icon does not come in mate notification area
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
998203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998203
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: yakuake
Version: 21.08.0-1
Severity: normal

Dear Maintainer,
I am running yakuake on Debian-mate. But it seems that in the
notification area for some reason yakuake is not seen :( . Sharing a
screenshot of the notification area.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-debug'), (100,
'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50,
'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages yakuake depends on:
ii  kio                    5.86.0-1
ii  konsole-kpart          4:21.08.2-1
ii  libc6                  2.32-4
ii  libkf5archive5         5.86.0-1
ii  libkf5configcore5      5.86.0-1
ii  libkf5configgui5       5.86.0-1
ii  libkf5configwidgets5   5.86.0-1
ii  libkf5coreaddons5      5.86.0-1
ii  libkf5crash5           5.86.0-1
ii  libkf5dbusaddons5      5.86.0-1
ii  libkf5globalaccel-bin  5.86.0-1
ii  libkf5globalaccel5     5.86.0-1
ii  libkf5i18n5            5.86.0-1
ii  libkf5iconthemes5      5.86.0-1
ii  libkf5kiocore5         5.86.0-1
ii  libkf5newstuff5        5.86.0-3
ii  libkf5newstuffcore5    5.86.0-3
ii  libkf5notifications5   5.86.0-1
ii  libkf5notifyconfig5    5.86.0-1
ii  libkf5parts5           5.86.0-1
ii  libkf5service-bin      5.86.0-1
ii  libkf5service5         5.86.0-1
ii  libkf5waylandclient5   4:5.86.0-1
ii  libkf5widgetsaddons5   5.86.0-1
ii  libkf5windowsystem5    5.86.0-1
ii  libkf5xmlgui5          5.86.0-1
ii  libqt5core5a           5.15.2+dfsg-12
ii  libqt5dbus5            5.15.2+dfsg-12
ii  libqt5gui5             5.15.2+dfsg-12
ii  libqt5widgets5         5.15.2+dfsg-12
ii  libqt5x11extras5       5.15.2-2
ii  libstdc++6             11.2.0-10
ii  libx11-6               2:1.7.2-2+b1

yakuake recommends no packages.

yakuake suggests no packages.

-- no debconf information


-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Attachment: mate-notification-area.png
Description: PNG image


--- End Message ---
--- Begin Message --- 
Le mardi, 2 novembre 2021, 08.28:14 h CEST shirish शिरीष a écrit :
> On 01/11/2021, Diederik de Haas <didi.debian@cknow.org> wrote:
> > On Monday, 1 November 2021 11:57:52 CET shirish शिरीष wrote:
> >> Because there is no notification, it is difficult to know when Yakuake
> >> has started or not.
> > 
> > AFAIK it's always started as soon as you log in.
> > I would actually find an item in the notification area/systray a
> > regression/bug
> > as it's meant to be out of your way/sight, but available when you need it
> > (via
> > F12 by default).
> > It could be that it does actually put out a notification via the
> > notification
> > system (ie a 'popup'), but I have disabled that as I found even that
> > annoying.
> > 
> > So the answer to 'when is it available?' is: Always.
> 
> I am on defaults, so no, no notification, otherwise would have not
> filed the bug. Thank you anyays :)

From the bug log, my understanding is that this is "not a bug"; or is there 
anything you'd see in need of fixing?

I'm closing the bug for now; please re-open if you see anything actionable!

Best,

    OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: