Package: alarm-clock-applet
Version: 0.3.3-1
Severity: important
Dear Maintainer,
* What led up to the situation?
I upgraded from Debian 6.0.x (Squeeze) to 7.0 (Wheezy). On attempting
to run the applet from the console, I got an error message that it
could not find libnotify.so.1, and it failed to launch.
* What exactly did you do (or not do) that was effective (or
ineffective)?
cd /usr/lib/x86_64-linux-gnu/
ln -s libnotify.so.4.0.0 libnotify.so.1
* What was the outcome of this action?
alarm-clock-applet works as expected.
* What outcome did you expect instead?
The same.
* Comments:
Of course what I did is a hack. I wonder if there is a compilation
issue.
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (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 alarm-clock-applet depends on:
ii gconf-service 3.2.5-1+build1
ii gconf2 3.2.5-1+build1
ii gstreamer0.10-gconf 0.10.31-3+nmu1
ii gstreamer0.10-plugins-base 0.10.36-1.1
ii libappindicator1 0.4.92-2
ii libc6 2.13-38
ii libgconf-2-4 3.2.5-1+build1
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libgstreamer0.10-0 0.10.36-1.2
ii libgtk2.0-0 2.24.10-2
ii libnotify4 0.7.5-1
ii libunique-1.0-0 1.1.6-4
ii libxml2 2.8.0+dfsg1-7+nmu1
alarm-clock-applet recommends no packages.
alarm-clock-applet suggests no packages.
-- no debconf information
--
The right of the people to be secure in their persons, houses, papers,
and effects, against unreasonable searches and seizures, shall not be
violated, and no Warrants shall issue, but upon probable cause,
supported by Oath or affirmation, and particularly describing the
place to be searched, and the persons or things to be seized.
-- U.S. Const. Amendment IV
Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
