Bug#1050036: pmount: Can't mount anything since the recent update of libmount1

2023-08-18 Thread Sébastien Dufromentel
Package: pmount
Version: 0.9.23-6
Severity: important
X-Debbugs-Cc: el...@fadrienn.irlnc.org

Dear Maintainer,

pmount was still perfectly working until recently, but now it fails any mount
complaining about a missing NTFS signature (even if the mounted drive is an
ext4 one, so shouldn't have any NTFS signature). It started a few weeks ago,
when libmount1 was updated from 2.38 to 2.39, so I guess it's related.

I tried to use the -t option to avoid this, but then I get an error from mount
complaining about “not mount point or bad option”, so it doesn't work either.
Don't exactly know what else I can try to have it working.

pumount still works, thought.

Regards,


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pmount depends on:
ii  libblkid1  2.39.1-4
ii  libc6  2.37-7

pmount recommends no packages.

Versions of packages pmount suggests:
pn  cryptsetup  

-- no debconf information


Bug#1028598: pathological: Unplayable game

2023-01-13 Thread Sébastien Dufromentel
Package: pathological
Version: 1.1.3-16
Severity: important
X-Debbugs-Cc: el...@fadrienn.irlnc.org

Dear Maintainer,

it looks like a cool game, so I installed it to try, but it just doesn't work.

When I launch the command, a window opens showing what looks like a menu, but I
can't interact with it. I tried using mouse, keyboard and joypad, nothing did
change the selected item nor activate it.

As it's really weird, maybe I'm doing something wrong?


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pathological depends on:
ii  python3 3.11.1-1
ii  python3-pygame  2.1.2+dfsg-5

pathological recommends no packages.

pathological suggests no packages.

-- no debconf information



Bug#1028594: balsa: Translation gone

2023-01-13 Thread Sébastien Dufromentel
Package: balsa
Version: 2.6.4-1
Severity: normal
X-Debbugs-Cc: el...@fadrienn.irlnc.org

Dear Maintainer,

since the 2.6.4, all the balsa interface is in english, despite my $LANG
environment variable set to “fr_FR.UTF-8”. It applies to toolbuttons, menus,
and the “On date, sender wrote:” line while answering mails, but the folder
names in the lateral pane (e.g. I still have “Boîte de réception” rather than
“INBOX”. Maybe because the configuration was created with a localized version).

When I try to launch it with another arbitrary value of $LANG, I get a GTK
warning about a locale not supported which I don't get with my basic setup, so
I guess the problem doesn't come from my settings.

Rolling back to the 2.6.3 solves the problem for now, but I'd rather use the
latest version in my own language if possible.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages balsa depends on:
ii  balsa-data  2.6.4-1
ii  libc6   2.36-8
ii  libcairo2   1.16.0-7
ii  libcanberra-gtk3-0  0.30-10
ii  libcanberra00.30-10
ii  libcompfaceg1   1:1.5.2-5.1
ii  libfribidi0 1.0.8-2.1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libglib2.0-02.74.4-1
ii  libgmime-3.0-0  3.2.13+dfsg-2
ii  libgnutls30 3.7.8-4
ii  libgpgme11  1.18.0-3
ii  libgspell-1-2   1.12.0-1+b1
ii  libgssapi-krb5-21.20.1-1
ii  libgtk-3-0  3.24.36-1
ii  libgtksourceview-4-04.8.4-3
ii  libical33.0.16-1+b1
ii  libldap-2.5-0   2.5.13+dfsg-2+b1
ii  libpango-1.0-0  1.50.12+ds-1
ii  libpangocairo-1.0-0 1.50.12+ds-1
ii  libsecret-1-0   0.20.5-3
ii  libsqlite3-03.40.1-1
ii  libwebkit2gtk-4.0-372.38.3-1
ii  libxml2 2.9.14+dfsg-1.1+b2
ii  pinentry-gnome3 [pinentry-x11]  1.2.1-1

Versions of packages balsa recommends:
ii  ca-certificates20211016
ii  gpgsm  2.2.40-1
pn  python3-html2text  
pn  yelp   

balsa suggests no packages.

-- no debconf information


Bug#1026884: Re : Bug#1026884: xfwm4: Reserved space through _NET_WM_STRUT property ignored

2023-01-03 Thread Sébastien Dufromentel

Hi there and happy new year,

I just did some more checks: it looks like xfce4-panel doesn't use the  
same property, which probably explain the difference.


There's two X properties to reserve space on screen: the _NET_WM_STRUT  
that I use, which reserve a whole border of the screen, and the  
_NET_WM_STRUT_PARTIAL used by xfce4-panel which is more complex but  
allows to reserve, for instance, half of a screen border.


It looks like Xfwm 4.18 still manages _NET_WM_STRUT_PARTIAL, which is  
why you didn't experiment the issue with xfce4-panel, but does no more  
manage _NET_WM_STRUT. I probably can patch my own applications to have  
them using the more advanced property, but I still think it's  
problematic to ignore the simple one, especially while all other WM I  
know still seem to support it.


Although the _NET_WM_STRUT is older and more seen to be used for  
backward compatibility, none of them are marked as deprecated in the  
specification so they should still be both supported:


https://specifications.freedesktop.org/wm-spec/latest/ar01s05.html#idm46443276574016

Regards,



Bug#1026884: Re : Bug#1026884: xfwm4: Reserved space through _NET_WM_STRUT property ignored

2022-12-28 Thread Sébastien Dufromentel

On 25/12/2022 20:23:59, Yves-Alexis Perez wrote:

control: tag -1 unreproducible moreinfo

On Fri, 2022-12-23 at 13:38 +0100, Sébastien Dufromentel wrote:
> Since the 4.18, it looks like Xfwm ignore such property: when I  
maximize some
> windows, they take the whole screen size and thus cover those  
reserved spaces,
> which is a bit problematic. The other WM I have on this computer,  
Compiz and
> Sawfish, still reserve space perfectly. I rollbacked to 4.16 using  
the bullseye
> package, and it works again too, so it looks like something very  
specific to

> this version of this particular WM.

Hi Sébastien, could you add more details on your configuration and  
especially
which applications use those reserved spaces? I didn't experience  
this issue

here at least with a standard Xfce desktop (so with xfce4-panel).

Regards,
--
Yves-Alexis



Hi there, sorry for the response delay.

I indeed use a custom environment with Xfwm and not the classical Xfce.  
I just launch xfwm4 and some hand-made applications at startup through  
a ~/.xsession script.


Here's attached a minimal script (using Python3/Xlib) to create a panel  
window reserving space at the top of the screen. When Xfwm 4.16 (or any  
other classical WM) is running in a standalone way, space is indeed  
avoided by the maximized window, so we have the panel and the maximized  
window's titlebar next to each other; but when Xfwm 4.18 is running,  
strut is ignored and the panel and the maximized window's titlebar end  
at the exact same location.


Hope it'll help.

Regards,#! /bin/python3
# coding: Utf-8

import time, array
import Xlib.display

disp = Xlib.display.Display()
screen = disp.screen()
geom = screen.root.get_geometry()

panel = screen.root.create_window(0, 0, geom.width, 24, 0,
screen.root_depth, background_pixel=0xFF00FF00)
panel.change_property(disp.intern_atom("_NET_WM_WINDOW_TYPE"),
disp.intern_atom("ATOM"), 32, array.array("I",
(disp.intern_atom("_NET_WM_WINDOW_TYPE_DOCK"),)))
panel.change_property(disp.intern_atom("_NET_WM_STRUT"),
disp.intern_atom("CARDINAL"), 32, array.array("I", (0, 0, 24, 0)))
panel.map()

while True:
while disp.pending_events() > 0:
ev = disp.next_event()
time.sleep(0.01)


Bug#1026884: xfwm4: Reserved space through _NET_WM_STRUT property ignored

2022-12-23 Thread Sébastien Dufromentel
Package: xfwm4
Version: 4.18.0-1
Severity: normal
X-Debbugs-Cc: el...@fadrienn.irlnc.org

Dear Maintainer,

Normally, windows like docks and panels can reserve some space on the screen
borders by using the X property _NET_WM_STRUT. It allow them to not be covered
by maximized windows, so they're always available visually and for mouse
action.

Since the 4.18, it looks like Xfwm ignore such property: when I maximize some
windows, they take the whole screen size and thus cover those reserved spaces,
which is a bit problematic. The other WM I have on this computer, Compiz and
Sawfish, still reserve space perfectly. I rollbacked to 4.16 using the bullseye
package, and it works again too, so it looks like something very specific to
this version of this particular WM.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xfwm4 depends on:
ii  libc6 2.36-6
ii  libcairo2 1.16.0-7
ii  libepoxy0 1.5.10-1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1
ii  libglib2.0-0  2.74.3-1
ii  libgtk-3-03.24.35-3
ii  libpango-1.0-01.50.12+ds-1
ii  libpangocairo-1.0-0   1.50.12+ds-1
ii  libstartup-notification0  0.12-6+b1
ii  libwnck-3-0   43.0-3
ii  libx11-6  2:1.8.3-2
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.4-1+b1
ii  libxfce4ui-2-04.18.0-1
ii  libxfce4util7 4.18.0-1
ii  libxfconf-0-3 4.18.0-1
ii  libxfixes31:6.0.0-2
ii  libxinerama1  2:1.1.4-3
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxrender1   1:0.9.10-1.1
ii  libxres1  2:1.2.1-1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.54.5+dfsg-1

Versions of packages xfwm4 suggests:
pn  xfce4  

-- no debconf information



Bug#951123: Acknowledgement (python3-wicd: Unable to get the ssid (external backend))

2020-02-12 Thread Sébastien Dufromentel
Okay, found it.

That's on line 50 in the file

/usr/lib/python3/dist-packages/wicd/wnettools.py

the regexp contained a “\t”, and the iwconfig output doesn't contain any 
tabulation (at least on my computer). I just replaced the regexp here by the 
one on line 49 in the file

/usr/lib/python2.7/dist-packages/wicd/wnettools.py

and now it works for me.

Bug#798755: Acknowledgement (pcsxr: Crash with Linux 4.1, works fine with 4.0)

2015-09-12 Thread Sébastien Dufromentel
Le 2015-09-12, Sébastien Dufromentel  a écrit :
> Tags: upstream

Oops, this was a mistake due to a clumsy clic on reportbug. I don't know if 
it's upstream or not. Sorry.

In addition, the output trace for launching the emulator on 4.0 kernel is just:

Intel Open Source Technology Center
Mesa DRI Intel(R) Haswell Mobile 

Bug#798755: pcsxr: Crash with Linux 4.1, works fine with 4.0

2015-09-12 Thread Sébastien Dufromentel
Package: pcsxr
Version: 1.9.92-4
Severity: important
Tags: upstream

Dear Maintainer,

on my system, pcsxr can't be launched with 4.1.* kernel.
I got this output:

ALSA lib pcm.c:7905:(snd_pcm_recover) underrun occurred
Intel Open Source Technology Center
Mesa DRI Intel(R) Haswell Mobile
pcsx: ../libpcsxcore/ix86_64/ix86-64.c :158 : MEMADDR_OP:  l'assertion
« !isreg || reg != 0 » a échoué.
Abandon

When I reboot on the old 4.0 kernel, there's no such problem, but I think
recent installations won't include this old kernel, so it may be problematic to
other people.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pcsxr depends on:
ii  libc6 2.19-19
ii  libgdk-pixbuf2.0-02.31.5-1
ii  libgl1-mesa-glx [libgl1]  10.6.5-1
ii  libglade2-0   1:2.6.4-2
ii  libglib2.0-0  2.44.1-1.1
ii  libgtk2.0-0   2.24.28-1
ii  libpango1.0-0 1.36.8-3
ii  libsdl1.2debian   1.2.15-11
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxtst6  2:1.2.2-1+b1
ii  libxv12:1.0.10-1+b1
ii  libxxf86vm1   1:1.1.4-1
ii  multiarch-support 2.19-19
ii  zlib1g1:1.2.8.dfsg-2+b1

pcsxr recommends no packages.

pcsxr suggests no packages.

-- no debconf information



Bug#737711: network-manager-gnome: Missing dependency

2014-02-05 Thread Sébastien Dufromentel
Package: network-manager-gnome
Version: 0.9.8.4-1
Severity: normal

This package recommends (and not depends of) gnome-keyring, but it does not
connect to wireless networks without having it installed. Strangely, even if I
ask not to remember the password.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-gnome depends on:
ii  dbus-x11 1.8.0-1
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  gconf-service3.2.6-1
ii  gnome-icon-theme 3.10.0-1
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-97
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libdbus-1-3  1.8.0-1
ii  libdbus-glib-1-2 0.100.2-1
ii  libgconf-2-4 3.2.6-1
ii  libgdk-pixbuf2.0-0   2.28.2-1+b1
ii  libglib2.0-0 2.36.4-1
ii  libgnome-bluetooth11 3.8.1-2
ii  libgnome-keyring03.8.0-2
ii  libgtk-3-0   3.8.6-1
ii  libnm-glib-vpn1  0.9.8.0-5
ii  libnm-glib4  0.9.8.0-5
ii  libnm-gtk0   0.9.8.4-1
ii  libnm-util2  0.9.8.0-5
ii  libnotify4   0.7.6-1
ii  libpango-1.0-0   1.36.0-1+b1
ii  libpangocairo-1.0-0  1.36.0-1+b1
ii  libsecret-1-00.15-2
ii  network-manager  0.9.8.0-5
ii  policykit-1-gnome0.105-2

Versions of packages network-manager-gnome recommends:
pn  gnome-bluetooth  
ii  gnome-keyring3.8.2-2
ii  iso-codes3.50-1
pn  mobile-broadband-provider-info   
ii  notification-daemon  0.7.6-1
ii  xfce4-notifyd [notification-daemon]  0.2.4-2

Versions of packages network-manager-gnome suggests:
pn  network-manager-openconnect-gnome  
pn  network-manager-openvpn-gnome  
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#732790: mpd: Unable to launch as user

2013-12-21 Thread Sébastien Dufromentel
Package: mpd
Version: 0.18.5-1
Severity: normal

mpd crashes when launched as user:

root@fadreils: ~$ service mpd stop
[ ok ] Stopping Music Player Daemon: mpd.

seth@fadreils: ~$ mpd ~/.config/mpd/rc
fatal_error: Failed to set supplementary groups of user "seth": Operation not
permitted

It worked well several monthes ago.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mpd depends on:
ii  adduser   3.113+nmu3
ii  init-system-helpers   1.13
ii  libadplug-2.2.1-0 2.2.1+dfsg3-0.1
ii  libao41.1.0-2
ii  libasound21.0.27.2-3
ii  libaudiofile1 0.3.6-2
ii  libavahi-client3  0.6.31-3
ii  libavahi-common3  0.6.31-3
ii  libavcodec54  10:1.2.4-dmo4
ii  libavformat54 10:1.2.4-dmo4
ii  libavutil52   10:2.1.1-dmo2
ii  libbz2-1.01.0.6-5
ii  libc6 2.17-97
ii  libcdio-cdda1 0.83-4.1
ii  libcdio-paranoia1 0.83-4.1
ii  libcdio13 0.83-4.1
ii  libcurl3-gnutls   7.34.0-1
ii  libfaad2  2.7-8
ii  libflac8  1.3.0-2
ii  libfluidsynth11.1.6-2
ii  libglib2.0-0  2.36.4-1
ii  libgme0   0.5.5-2
ii  libid3tag00.15.1b-10
ii  libiso9660-8  0.83-4.1
ii  libjack0 [libjack-0.116]  1:0.121.3+20120418git75e3e20b-2.1
ii  libmad0   0.15.1b-8
ii  libmikmod23.1.12-5
ii  libmms0   0.6.2-3
ii  libmodplug1   1:0.8.8.4-4
ii  libmp3lame0   1:3.99.5-dmo2
ii  libmpcdec62:0.1~r459-4
ii  libmpdclient2 2.9-1
ii  libmpg123-0   1.16.0-1
ii  libogg0   1.3.1-1
ii  libopenal11:1.14-4
ii  libopus0  1.1-1
ii  libpulse0 4.0-6+b1
ii  libresid-builder0c2a  2.1.1-14
ii  libroar2  1.0~beta10-1
ii  libsamplerate00.1.8-5
ii  libshout3 2.3.1-3
ii  libsidplay2   2.1.1-14
ii  libsidutils0  2.1.1-14
ii  libsndfile1   1.0.25-7
ii  libsqlite3-0  3.8.2-1
ii  libstdc++64.8.2-10
ii  libsystemd-daemon0204-5
ii  libvorbis0a   1.3.2-1.3
ii  libvorbisenc2 1.3.2-1.3
ii  libvorbisfile31.3.2-1.3
ii  libwavpack1   4.70.0-1
ii  libwildmidi1  0.2.3.4-2.1
ii  libwrap0  7.6.q-24
ii  libyajl2  2.0.4-4
ii  lsb-base  4.1+Debian12

mpd recommends no packages.

Versions of packages mpd suggests:
ii  avahi-daemon  0.6.31-3
pn  icecast2  
ii  mpc [mpd-client]  0.25-1
pn  pulseaudio

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#727004: xchat: Use wrong clipboard for text selection

2013-10-21 Thread Sébastien Dufromentel
Package: xchat
Version: 2.8.8-7.1+b1
Severity: normal

Selecting a text in the chan view send it to the “primary” clipboard (used
for the middle-clic paste), but send it to the “clipboard” one (used for
the classical copy/paste) too. So, selecting a text in the chan view means
losing the text/image/file/etc. stored in the main clipboard.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xchat depends on:
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-93
ii  libcairo21.12.16-2
ii  libdbus-1-3  1.6.16-1
ii  libdbus-glib-1-2 0.100.2-1
ii  libfontconfig1   2.10.2-2
ii  libfreetype6 2.4.9-1.1
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libglib2.0-0 2.36.4-1
ii  libgtk2.0-0  2.24.21-1
ii  libpango-1.0-0   1.32.5-5+b1
ii  libpangocairo-1.0-0  1.32.5-5+b1
ii  libpangoft2-1.0-01.32.5-5+b1
ii  libperl5.18  5.18.1-4
ii  libsexy2 0.1.11-2+b1
ii  libssl1.0.0  1.0.1e-3
ii  libx11-6 2:1.6.2-1
ii  libxml2  2.9.1+dfsg1-3
ii  xchat-common 2.8.8-7.1

Versions of packages xchat recommends:
ii  alsa-utils 1.0.27.1-1
ii  libnotify-bin  0.7.6-1
ii  libnotify4 0.7.6-1
ii  libpython2.7   2.7.5-8
ii  tcl8.5 8.5.14-2
ii  xdg-utils  1.1.0~rc1+git20111210-7

xchat suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#725677: wmclock: no more translations

2013-10-07 Thread Sébastien Dufromentel
Package: wmclock
Version: 1.0.14-2
Severity: normal

Dear Maintainer,

the last packaged version do no more include the image files (previously
/usr/share/wmclock/lang.*/[month|weekday].xpm) that allow to have a translated
clock. Is it possible to get them back, or to add a new dependency to another
package containing them?

Thanks.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages wmclock depends on:
ii  libc6 2.17-92+b1
ii  libx11-6  2:1.6.1-1
ii  libxext6  2:1.3.2-1
ii  libxpm4   1:3.5.10-1

wmclock recommends no packages.

wmclock suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org