Your message dated Sat, 15 Oct 2016 01:57:20 -0500
with message-id <20161015065720.fdb73e2mnhp4p...@knives.aquaticape.us>
and subject line Re: Bug#756748: notification-daemon causing xfce4-panel to be 
unresponsive
has caused the Debian Bug report #756748,
regarding notification-daemon causing xfce4-panel to be unresponsive
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 ow...@bugs.debian.org
immediately.)


-- 
756748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: notification-daemon
Version: 0.7.6-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
     On booting, an error message saying notification-daemon cannot load
because another instance already running.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     The problem seems to just pop up randomly, and the panel becomes
unresponsive. If I left-click on any part of the panel, it becomes right-
clicked and brings up panel menu. Other applications that require keyboard
input become unresponsive (as if somebody pressed shift) as well. For instance,
terminal: If I press D on the keyboard, the window closes. Or in browsers
(chromium, midori  and iceweasel), and geany, if I scroll down, the page is
zoomed out.
   * What was the outcome of this action?
     Panel and some applications become unresponsive. I have to log out and
back in to solve the problem. I had the same problem in xubuntu 14.04 and
switched to debian to see if the problem persisted. At first there wasn't any
problem, but after adding notification-daemon to the panel, and a few booting
latter, the proble came back.
   * What outcome did you expect instead?
     All works normal.



-- System Information:
Debian Release: 7.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages notification-daemon depends on:
ii  libatk1.0-0         2.4.0-2
ii  libc6               2.13-38+deb7u3
ii  libcairo2           1.12.2-3
ii  libcanberra-gtk3-0  0.28-6
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-0        2.33.12+really2.32.4-5
ii  libgtk-3-0          3.4.2-7
ii  libx11-6            2:1.5.0-1+deb7u1

notification-daemon recommends no packages.

notification-daemon suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Fri, Aug 01, 2014 at 07:04:50PM +0800, lewowpard wrote:
>    * What led up to the situation?
>      On booting, an error message saying notification-daemon cannot load
> because another instance already running.
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>      The problem seems to just pop up randomly, and the panel becomes
> unresponsive. If I left-click on any part of the panel, it becomes right-
> clicked and brings up panel menu. Other applications that require keyboard
> input become unresponsive (as if somebody pressed shift) as well. For 
> instance,
> terminal: If I press D on the keyboard, the window closes. Or in browsers
> (chromium, midori  and iceweasel), and geany, if I scroll down, the page is
> zoomed out.
>    * What was the outcome of this action?
>      Panel and some applications become unresponsive. I have to log out and
> back in to solve the problem. I had the same problem in xubuntu 14.04 and
> switched to debian to see if the problem persisted. At first there wasn't any
> problem, but after adding notification-daemon to the panel, and a few booting
> latter, the proble came back.
>    * What outcome did you expect instead?
>      All works normal.

Closing due to no response

--- End Message ---

Reply via email to