Bug#1065362: Need for kea-msg-compiler

[Quentin Armitage]

Paride,

Many thanks for your response.

So far as I can tell the only use of the kea-dev package is for building hooks. 
Hooks should
include some logging output, and without kea-msg-compiler the message sources 
cannot be
built. This essentially make the current kea-dev package not usable.

Bug #1065361 (kea-dev: cfg_globals.h is missing) also renders the current 
kea-dev to all
intents and purposes unusable, so I think it would be really helpful to have an 
updated kea-
dev package adding both kea-msg-compiler and cfg_globals.h for Bookworm.

Quentin Armitage

Bug#1065362: Correct name for message compiler

[Quentin Armitage]

With apologies, the correct name for the message compiler is kea-msg-compiler 
rather than
kea-message-compiler.

Bug#1065362: kea-dev: kea-message-compiler is missing from kea-dev package and is needed for building message files

[Quentin Armitage]

Package: kea-dev
Version: 2.2.0-6
Severity: important

Dear Maintainer,

   * What led up to the situation?

Attempting to build a kea hook that includes logging to syslog

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Manually build kea-message-compiler from the kea source
distribution and installed it /usr/bin

   * What was the outcome of this action?

I could now successfully build hooks with logging

   * What outcome did you expect instead?

kea-dev should be updated to include
/usr/bin/kea-message-compiler 

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.1.0-rpi8-rpi-2712 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kea-dev depends on:
ii  kea-common  2.2.0-6

kea-dev recommends no packages.

kea-dev suggests no packages.

-- no debconf information

Bug#1065361: kea-dev: cfg_globals.h is missing from kea-dev package with kea v2.2.x

[Quentin Armitage]

Package: kea-dev
Version: 2.2.0-6
Severity: important

Dear Maintainer,

   * What led up to the situation?

Building kea hooks fails due to missing cfg_globals.h

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I manually installed cfg_globals.h from the kea source
distribution in /usr/include/kea/dhcpsrv

   * What was the outcome of this action?

I could now successfully compile hooks.

   * What outcome did you expect instead?

Outcome was as I suspected

Upstream commit 
https://gitlab.isc.org/isc-projects/kea/-/commit/7c82b69c46b1d499680a8a2bd8c33a31bf9124f9
added cfg_globals.h to the list of files to be installed, but that
was only included from kea v2.4.0

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.1.0-rpi8-rpi-2712 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kea-dev depends on:
ii  kea-common  2.2.0-6

kea-dev recommends no packages.

kea-dev suggests no packages.

-- no debconf information

Bug#1006942: safeeyes: Safeeyes no longer seems to appears in the KDE/Plasma system tray

[Quentin Hibon]

Upstream has now released a new version, so now it's just a matter of 
updating the version in Debian to fix this:


https://github.com/slgobinath/SafeEyes/issues/428#issuecomment-1321266409

On Wed, 27 Apr 2022 13:09:21 +0100 Julian Gilbey  wrote:

On Wed, Mar 09, 2022 at 08:59:20AM +0100, Jonas Andradas wrote:
> On Tue, Mar 8, 2022 at 5:57 PM Jonas Andradas  wrote:
> 
>   Package: safeeyes

>   Version: 2.1.3-1
>   Severity: minor
>   X-Debbugs-Cc: j.andra...@gmail.com
> 
>   Dear Maintainer,
> 
>   I noticed that fairly recently (unfortunately, cannot exactly be sure when or

>   after which package update), safeeyes does not seem appear anymore in
>   KDE/Plasma system tray. It is not shown on the system tray, neither in the
>   "visible" elements nor in the "box" that has the hidden icons.
> [...]
> 
> It seems that this bug was also opened upstream on safeeyes' github: 

> https://github.com/slgobinath/SafeEyes/issues/428 (which seems related to
> https://github.com/slgobinath/SafeEyes/issues/268)
> Best Regards,
> Jonas.

Indeed; it is fixed in commit
https://github.com/slgobinath/SafeEyes/commit/c784000e694f9fa508a2535f5d23d04456b4ff86
but upstream have not yet released a new version of the package.

Please could you upload a patched version to Debian?

Best wishes,

   Julian

Bug#1016646: bind9: /etc/bind/named.conf incorrectly refers to /usr/share/doc/bind9/README.Debian.gz

[Quentin Armitage]

Package: bind9
Version: 1:9.18.5-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?
   I was configuring bind9 and read /etc/bind/named.conf which said to
   read /usr/share/doc/bind9/README.Debian.gz before configuring bind.
   That file does not exist, which confused me. I subsequently
   discovered that the file is /usr/share/doc/bind9/README.Debian (i.e.
   no .gz suffix).

   This is also an issue with bind9 9.16

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)

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

Versions of packages bind9 depends on:
ii  adduser3.118
ii  bind9-libs 1:9.18.5-1
ii  bind9-utils1:9.18.5-1
ii  debconf [debconf-2.0]  1.5.77
ii  dns-root-data  2021011101
ii  init-system-helpers1.60
ii  iproute2   5.10.0-4
ii  libc6  2.31-13+deb11u3
ii  libcap21:2.44-1
ii  libfstrm0  0.6.0-1+b1
ii  libjson-c5 0.15-2
ii  liblmdb0   0.9.24-1
ii  libmaxminddb0  1.5.2-1
ii  libnghttp2-14  1.43.0-1
ii  libprotobuf-c1 1.3.3-1+b2
ii  libssl1.1  1.1.1n-0+deb11u3
ii  libuv1 1.40.0-2
ii  libxml22.9.10+dfsg-6.7+deb11u2
ii  lsb-base   11.1.0
ii  netbase6.3
ii  zlib1g 1:1.2.11.dfsg-2+deb11u1

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind-doc   
ii  bind9-dnsutils [dnsutils]  1:9.18.5-1
ii  resolvconf 1.87
pn  ufw

-- Configuration Files:
/etc/bind/named.conf changed [not included]
/etc/bind/named.conf.local changed [not included]
/etc/bind/named.conf.options changed [not included]
/etc/ufw/applications.d/bind9 [Errno 2] No such file or directory: 
'/etc/ufw/applications.d/bind9'

-- no debconf information

Bug#1005241: linux-image-5.15.0-3-amd64: Failure to suspend/resume when cpu on high frequency

[Quentin Lambotte]

Package: src:linux
Version: 5.15.15-2
Severity: important
X-Debbugs-Cc: quentin.lambo...@hotmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I have issues with suspend and resume tasks with my computer. At first, my 
computer 
systematically crashed when I tried to resume from suspend. More precisely, 
when I close 
the lid (or enter suspend by clicking on the appropriate menu entry) and then 
reopen it, 
my screen remains black and the fans are usually runnin fast. At this point, I 
have to do
a hard reboot to use my computer again. I found a prtial solution to this 
problem by installing
the software auto-cpufreq: the suspend/resume sequence works most of the time. 
The only observation
I could make at this point is that the sequence suspend/resume fails only when 
the cpu is on high
frequency (turbo boost is on), for instance when I watch a video (this happens 
systematically in
this situation). I tried to compare the entries in journalctl of a faulty 
suspend/resume sequence
to one that warked and here is the part of the faulty one that I think is 
relevant:
Feb 06 12:23:49 zenbook kernel: amdgpu :04:00.0: amdgpu: SMU is resuming...
Feb 06 12:23:49 zenbook kernel: amdgpu :04:00.0: amdgpu: dpm has been 
disabled
Feb 06 12:23:49 zenbook kernel: amdgpu :04:00.0: amdgpu: SMU is resumed 
successfully!
Feb 06 12:23:49 zenbook kernel: nvme nvme0: 16/0/0 default/read/poll queues
Feb 06 12:23:49 zenbook kernel: amdgpu :04:00.0: 
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
Feb 06 12:23:49 zenbook kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] 
*ERROR* resume of IP block  failed -110
Feb 06 12:23:49 zenbook kernel: amdgpu :04:00.0: amdgpu: 
amdgpu_device_ip_resume failed (-110).
Feb 06 12:23:49 zenbook kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 
returns -110
Feb 06 12:23:49 zenbook kernel: amdgpu :04:00.0: PM: failed to resume 
async: error -110
Feb 06 12:23:49 zenbook kernel: OOM killer enabled.
Feb 06 12:23:49 zenbook kernel: Restarting tasks ... done.
Feb 06 12:23:49 zenbook kernel: PM: suspend exit
Feb 06 12:23:49 zenbook systemd-sleep[40551]: System returned from sleep state.

With best regards,

Quentin Lambotte

-- Package-specific info:
** Version:
Linux version 5.15.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-14) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37.90.20220123) #1 SMP 
Debian 5.15.15-2 (2022-01-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.15.0-3-amd64 
root=UUID=f326bad7-80a3-4816-bab2-adf156a5706f ro quiet i8042.probe_defer

** Not tainted

** Kernel log:
[34594.805509] wlp1s0: associate with d8:07:b6:83:b5:22 (try 1/3)
[34594.909702] wlp1s0: associate with d8:07:b6:83:b5:22 (try 2/3)
[34595.061738] wlp1s0: associate with d8:07:b6:83:b5:22 (try 3/3)
[34595.169702] wlp1s0: association with d8:07:b6:83:b5:22 timed out
[34602.827015] wlp1s0: authenticate with d8:07:b6:83:b5:23
[34602.842431] wlp1s0: send auth to d8:07:b6:83:b5:23 (try 1/3)
[34602.847848] wlp1s0: authenticated
[34602.853674] wlp1s0: associate with d8:07:b6:83:b5:23 (try 1/3)
[34602.957623] wlp1s0: associate with d8:07:b6:83:b5:23 (try 2/3)
[34603.035823] wlp1s0: RX AssocResp from d8:07:b6:83:b5:23 (capab=0x1411 
status=0 aid=3)
[34603.061486] wlp1s0: associated
[34603.103484] wlp1s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 
d8:07:b6:83:b5:23
[34620.840320] wlp1s0: deauthenticating from d8:07:b6:83:b5:23 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[34623.354316] wlp1s0: authenticate with 50:c7:bf:f1:83:2c
[34623.367464] wlp1s0: send auth to 50:c7:bf:f1:83:2c (try 1/3)
[34623.388479] wlp1s0: authenticated
[34623.389253] wlp1s0: associate with 50:c7:bf:f1:83:2c (try 1/3)
[34623.416917] wlp1s0: RX AssocResp from 50:c7:bf:f1:83:2c (capab=0xc11 
status=0 aid=2)
[34623.440442] wlp1s0: associated
[34623.567039] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[34653.398468] wlp1s0: deauthenticating from 50:c7:bf:f1:83:2c by local choice 
(Reason: 3=DEAUTH_LEAVING)
[34663.637633] wlp1s0: authenticate with 50:c7:bf:f1:83:2c
[34663.650733] wlp1s0: send auth to 50:c7:bf:f1:83:2c (try 1/3)
[34663.663348] wlp1s0: authenticated
[34663.664860] wlp1s0: associate with 50:c7:bf:f1:83:2c (try 1/3)
[34663.681771] wlp1s0: RX AssocResp from 50:c7:bf:f1:83:2c (capab=0xc11 
status=0 aid=2)
[34663.705279] wlp1s0: associated
[34663.870801] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[34672.857808] wlp1s0: deauthenticating from 50:c7:bf:f1:83:2c by local choice 
(Reason: 3=DEAUTH_LEAVING)
[34686.609716] wlp1s0: authenticate with d8:07:b6:83:b5:23
[34686.624811] wlp1s0: send auth to d8:07:b6:83:b5:23 (try

Bug#987793: [L10N,OC] apt: new Occitan debconf translation

[Quentin PAGÈS]

Hello Julian,

I used the translation file from Launchpad for Ubuntu to have a translation 
memory.
Sometimes there are differences with "root" software like the "\r" you 
mentioned.
About msgid "[IP: %s %s]"
msgstr "[IP : %s %s]"

I do not get what the problem is, we use a space, well narrow non breaking 
space, before ";:?!»" and after "»".
Just like in French.
The translations are reviewed, you can have a look at 
https://translations.launchpad.net/ubuntu/impish/+source/apt/+pots/apt/oc/+translate
 to judge.

I am working to complete to translation step by step.

Quentin

- Mail original -
De: "Julian Andres Klode" 
À: "Holger Wansing" , 987...@bugs.debian.org
Cc: "Quentin PAGÈS" 
Envoyé: Lundi 17 Mai 2021 13:46:10
Objet: Re: Bug#987793: [L10N,OC] apt: new Occitan debconf translation

Control: tag -1 moreinfo
Control: tag -1 - patch

On Thu, Apr 29, 2021 at 08:49:42PM +0200, Holger Wansing wrote:
> Package: apt
> Severity: wishlist
> Tags: patch,l10n
> X-Debbugs-CC: Quentin PAGÈS 
> 
> 
> Hi,
> attached is a (new) debconf translation for apt into Occitan, submitted by 
> Quentin PAGÈS .
> 
> Please include it as ./po/oc.po in apt.

NAK

The translation includes inappropriate formatting changes:

po/oc.po:3031: warning: internationalized messages should not contain the '\r' 
escape sequence

or this:

msgid "[IP: %s %s]"
msgstr "[IP : %s %s]"

and only translates about half the messages

oc:486 translated messages, 1 fuzzy translation, 223 untranslated

Given the obvious lack of review, the lack of many translations, this
does not seem to be ready for review yet, and I do not have enough faith
in the submission to not be messed up in other ways.

Feel free to resubmit a translation that has been reviewed and addressed
the issues. I'm especially worried about technical issues, given that
the file has not been tested at all, and their being security
implications if one % is missing or in the wrong place.

I don't necessarily have an interest in reviewing each translated
string myself. Maybe there are tools to ensure that the formatting
strings use the same operators in the same order, I don't translate
stuff much.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#982316: Errors in config file from package yubikey-ksm (apache.conf)

[Pol-Quentin Dupont]

Package: yubikey-ksm
Version: 1.15-6
Severity: Grave

Hello,

There are 2 bad lines in /etc/yubico/ksm/apache.conf for this packet available 
for Debian Stretch :

1- you have to replace  by  at line 
10;
2- you have to replace  by  at the last line.

Without these modifications :

- Apache2 will crash during a reload or restart withouht modifying the last 
line;
- HTTP 404 error using URL :host/wsapy/decrypt without modifying line 10.


Have a nice day !

Pol-Quentin Dupont.

Bug#969312: localechooser doesn’t display Occitan and Kabyle languages

[Quentin PAGÈS]

Hello, 


many thanks for helping us. 


Best regards 


Quentin 

- Mail original -

De: "Slimane Selyan Amiri"  
À: "Holger Wansing"  
Cc: 969...@bugs.debian.org, "debian-boot" , 
"Quentin PAGÈS"  
Envoyé: Vendredi 20 Novembre 2020 12:53:25 
Objet: Re: Bug#969312: localechooser doesn’t display Occitan and Kabyle 
languages 


Thank you a lot for your great work. 




Le ven. 20 nov. 2020 à 07:41, Holger Wansing < hwans...@mailbox.org > a écrit : 


Control: fixed -1 2.88 


Since Occitan and Kabyle have arrived in the installer - and being them fully 
translated! - I am closing this report (even if Kabyle has issues in the 
text-based installer; that's #973455). 


Holger 


-- 
Holger Wansing < hwans...@mailbox.org > 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 

Bug#969312: localechooser doesn’t display Occitan and Kabyle languages

[Quentin PAGÈS]

Hello, 


any update for this report? 


Best regards 


Quentin PAGÈS 

Bug#969312: localechooser doesn’t display Occitan and Kabyle languages

[Quentin PAGÈS]

Package: Debian Installer > localechooser
Version: all

Hello,
When I run a live DVD / USB, on the menu to choose a language, there is no way 
to choose Occitan nor Kabyle. 
I suggest that the following 3 merge requests to be examined for addition: 

https://salsa.debian.org/installer-team/localechooser/-/merge_requests 


Quentin PAGÈS

Bug#905786: libvncserver1: Use-after-free on shutdown when clients are still connected (causing issue for Virtualbox)

[quentin buathier]

Hi Mike,

I don't think so, I worked on this on my job and it's currently not what
I'm working on.

Greets,
Quentin

Le mar. 3 déc. 2019 à 12:00, Mike Gabriel 
a écrit :

> Hi Quentin,
>
> On  Di 03 Dez 2019 11:54:29 CET, quentin buathier wrote:
>
> > Hi Mike,
> >
> > Thanks for taking care of this and updating the package to the last
> > release.
> > This should fix the issue but I don't have the opportunity (as I'm not on
> > buster yet) nor the time to test it.
> >
> > Greets,
> > Quentin
>
> If I provided you with a stretch version of the package (which is
> pretty similar), could you imagine albeit time restraints to test that?
>
> Greets,
> Mike
> --
>
> DAS-NETZWERKTEAM
> c\o Technik- und Ökologiezentrum Eckernförde
> Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
> mobile: +49 (1520) 1976 148
> landline: +49 (4351) 850 8940
>
> GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
>
>

Bug#905786: libvncserver1: Use-after-free on shutdown when clients are still connected (causing issue for Virtualbox)

[quentin buathier]

Hi Mike,

Thanks for taking care of this and updating the package to the last
release.
This should fix the issue but I don't have the opportunity (as I'm not on
buster yet) nor the time to test it.

Greets,
Quentin

Le mar. 3 déc. 2019 à 09:28, Mike Gabriel 
a écrit :

> Hi Quentin,
>
> thanks for reporting the below bug and fixing things upstream...
>
> On Thu, 09 Aug 2018 15:52:29 +0200 Quentin BUATHIER
>  wrote:
>  > Package: libvncserver1
>  > Version: 0.9.11+dfsg-1+deb9u1
>  > Severity: important
>  > Tags: patch
>  >
>  > In the upstream source of the project, there is an use-after-free
> that can lead
>  > to an infinite wait of a non-existing thread during the shutdown of
> the VNC
>  > server if some clients are still connected.
>  >
>  > This causing an issue in Virtualbox which uses this package when a
> VNC client
>  > is connected and that we shutdown the VM (the VM will be stuck in a
> buggy
>  > state). See https://www.virtualbox.org/ticket/17396 for the ticket in
>  > Virtualbox's bug tracker for more informations.
>  >
>  > There is actually a pull request on upstream fixing this issue
>  > (https://github.com/LibVNC/libvncserver/pull/238). There is also
> another issue,
>  > a segmentation fault in the same use case when we are using a
> multi-threaded
>  > VNC server (also fixed by the same pull request).
>  >
>  > Virtualbox need both fixes to work correctly without a segmentation
> fault or a
>  > infinite wait and probably some others packages using libvncserver.
>  >
>  > The issue isn't present on Jessie with the version 0.9.9 of the package.
>
> As the new libvncserver Debian maintainer, I have prepared a test build
> and upload candidate for Debian buster of libvncserver that fixes this
> issue:
> http://packages.sunweavers.net/debian/pool/main/libv/libvncserver/
>
> You can also add "deb http://packages.sunweavers.net/debian buster main"
> to your APT configuration and use apt for installing the upload
> candidate. (Make sure you disable the repo again afterwards and that you
> don't grab other packages from there by accident).
>
> Here is the archive key:
> https://packages.sunweavers.net/archive.key
>
> If you don't have time for testing this, I'd appreciate a quick feedback
> anyway.
>
> Greets + Thanks,
> Mike
>

Bug#943791: general: laptop HP 15_bw0xx does not power-off properly

[Christian Quentin]

Package: general
Severity: normal

Dear Maintainer,

* when I ask Debian to stop (from Gnome), the shutdown sequence seems to follow
the usual steps, the a blank screen appears.The screen is not completely off.
The PC does not power-off.
* As the PC does not stop, I have to press the power button 10 seconds which
does not seem to be the best way to stop a computer.
* I would expect the shutdown sequence to power-off the computer completely.
* Hint : shutting down Windows 10 (also present on this computer) works fine.

Best regards and thanks for the fabulous work you do



-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#794410: (no subject)

[Quentin Stafford-Fraser]

I encountered this issue trying to install Buster on a Gigabyte Brix 
2807 - hanging at 11% trying to install 'discover'.


Changing the BIOS setting for OS type from Windows 7 to Windows 8 also 
fixed it for me.


Thanks all,
Quentin

Bug#896165: linux: request packaging of bpftool

[Quentin Monnet]

On Mon, 15 Apr 2019 16:45:34 +0200 Simon Horman wrote:
> Hi Noah,
>
> I believe that the above commit resolves the licence problem that was
> raised earlier. Is it possible to find a way to move forwards on packaging
> bpftool?

Greetings,

I would really like to see bpftool packaged. Is there anything that I
could do to help here? Noah, I can try to rebase your pull request
(https://salsa.debian.org/kernel-team/linux/merge_requests/72) and
submit it again on Salsa if you think this is helpful?

Kind regards,
Quentin

Bug#930345: lstp: [INTL:fr] French program translation update

[Quentin Lejard]

Package: lstp
Version: 5.1.99
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French translation, proofread by the
debian-l10n-french mailing list contributors.

This file should be put as fr.po in the appropriate place in
your package build tree.

Best regards,

Quentin Lejard


-- System Information:
Debian Release: 9.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.127-mainline-rev1 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# LTSP CATALOG -- FRENCH TRANSLATION
# Copyright (C) 2009 Debian French l10n team 

# This file is distributed under the same license as the LTSP package.
# Translators:
#
# Cyril Brulebois , 2006.
# Jean-Baka Domelevo-Entfellner , 2007, 2009.
# Quentin LEJARD , 2019.
msgid ""
msgstr ""
"Project-Id-Version: ltsp 5.1.99\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-12-16 09:44+0100\n"
"PO-Revision-Date: 2019-04-06 15:46+0100\n"
"Last-Translator: Quentin Lejard \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Launchpad-Export-Date: 2018-12-17 04:30+\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#: ../common/ltsp-common-functions:194
#, sh-format
msgid "translator-credits"
msgstr ""
"Launchpad Contributions:\n"
"  Alban CLERGEOT https://launchpad.net/~g33ky\n;
"  Arnaud Faucher https://launchpad.net/~arnaud-faucher\n;
"  Bruno Patri https://launchpad.net/~bruno666-deactivatedaccount\n;
"  Christophe Painchaud https://launchpad.net/~dash-ionblast\n;
"  Claude Paroz https://launchpad.net/~paroz\n;
"  Cyril Brulebois https://launchpad.net/~cyril-brulebois\n;
"  Doyen Philippe https://launchpad.net/~dyphil-deactivatedaccount\n;
"  EmmanuelLeNormand https://launchpad.net/~emmanuel-le-normand\n;
"  Jean-Baka Domelevo-Entfellner https://launchpad.net/~domelevo\n;
"  Jim McQuillan https://launchpad.net/~jam-mcquil\n;
"  Julien Chiquet https://launchpad.net/~julien-chiquet\n;
"  Stéphane Graber https://launchpad.net/~stgraber\n;
"  londumas https://launchpad.net/~helion331990\n;
"  madden https://launchpad.net/~linux-madfix;

#: ../server/ALTLinux/configs/ltsp-login.sh:30
#: ../server/ALTLinux/configs/ltsp-login.sh:33
#: ../server/ALTLinux/configs/ltsp-login.sh:40
#: ../server/ALTLinux/configs/ltsp-login.sh:50
#, sh-format
msgid "Login Error"
msgstr "Erreur d'authentification"

#: ../server/ALTLinux/configs/ltsp-login.sh:31
#: ../server/ALTLinux/configs/ltsp-login.sh:34
#: ../server/ALTLinux/configs/ltsp-login.sh:44
#: ../server/ALTLinux/configs/ltsp-login.sh:52
#: ../server/ALTLinux/configs/ltsp-login.sh:62
#: ../server/ALTLinux/configs/ltsp-login.sh:81
#: ../server/ALTLinux/configs/ltsp-login.sh:84
#: ../server/ALTLinux/configs/ltsp-login.sh:95
#: ../server/ALTLinux/configs/ltsp-login.sh:105
#: ../server/ALTLinux/configs/ltsp-login.sh:115
#, sh-format
msgid "User"
msgstr "Utilisateur"

#: ../server/ALTLinux/configs/ltsp-login.sh:31
#: ../server/ALTLinux/configs/ltsp-login.sh:34
#: ../server/ALTLinux/configs/ltsp-login.sh:44
#: ../server/ALTLinux/configs/ltsp-login.sh:52
#: ../server/ALTLinux/configs/ltsp-login.sh:62
#: ../server/ALTLinux/configs/ltsp-login.sh:81
#: ../server/ALTLinux/configs/ltsp-login.sh:84
#: ../server/ALTLinux/configs/ltsp-login.sh:95
#: ../server/ALTLinux/configs/ltsp-login.sh:105
#: ../server/ALTLinux/configs/ltsp-login.sh:115
#, sh-format
msgid "already logged in!"
msgstr "déjà connecté !"

#: ../server/ALTLinux/configs/ltsp-login.sh:34
#: ../server/ALTLinux/configs/ltsp-login.sh:43
#: ../server/ALTLinux/configs/ltsp-login.sh:84
#: ../server/ALTLinux/configs/ltsp-login.sh:93
#: ../server/ALTLinux/configs/ltsp-login.sh:117
#, sh-format
msgid "Continue"
msgstr "Continuer"

#: ../server/ALTLinux/configs/ltsp-login.sh:80
#: ../server/ALTLinux/configs/ltsp-login.sh:83
#: ../server/ALTLinux/configs/ltsp-login.sh:90
#: ../server/ALTLinux/configs/ltsp-login.sh:103
#, sh-format
msgid "Login Warning"
msgstr "Alerte d'authentification"

#: ../server/ALTLinux/configs/ltsp-login.sh:94
#, sh-format
msgid "Cancel"
msgstr "Annuler"

#: ../server/ltsp-build-client:79
#, sh-format
msgid "API ERROR: you need to provide true or false."
msgstr "Erreur d'API : vous devez indiquer true (vrai) ou false (faux)."

#:

Bug#922550: Same problem here

[Quentin Caillard]

@debian:~$ sudo systemd-analyze blame
  5min 804ms ifupdown-wait-online.service
  5.515s sickrage.service
  3.448s NetworkManager-wait-online.service
  1.128s systemd-udev-settle.service
  1.005s alsa-restore.service

Bug#926451: distcc: [INTL:fr] French debconf translation update

[Quentin Lejard]

Package: distcc
Version: 3.3.2-7
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

Best regards,

Quentin Lejard


-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.127-mainline-rev1 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Translation of distcc debconf templates to French
# Copyright (C) 2007 Christian Perrier 
# Copyright (C) 2009-2019 Debian French l10n team 

# This file is distributed under the same license as the distcc package.
#
#
# Christian Perrier , 2007, 2008, 2009, 2010.
# Quentin Lejard , 2019.
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: dis...@packages.debian.org\n"
"POT-Creation-Date: 2018-12-22 18:41+0100\n"
"PO-Revision-Date: 2019-02-25 18:57+0100\n"
"Last-Translator: Quentin LEJARD \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid "Start the distcc daemon on startup?"
msgstr "Faut-il lancer le démon distcc au démarrage ?"

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid ""
"distcc can be run as a daemon, listening on port 3632 for incoming "
"connections."
msgstr ""
"Distcc peut fonctionner avec un démon qui sera à l'écoute des connexions "
"entrantes sur le port 3632."

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid ""
"You have the option of starting the distcc daemon automatically on the "
"computer startup. If in doubt, it's advised not to start it automatically on "
"startup. If you later change your mind, you can run: 'dpkg-reconfigure "
"distcc'."
msgstr ""
"Vous pouvez lancer le démon distcc automatiquement au démarrage du système. "
"Dans le doute, vous devriez vous en abstenir. Si vous souhaitez modifier ce "
"réglage plus tard, vous pourrez utiliser la commande « dpkg-reconfigure "
"distcc »."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid "Allowed client networks:"
msgstr "Réseaux clients autorisés :"

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"The distcc daemon implements access control based on the IP address of the "
"client, that is trying to connect. Only the hosts or networks listed here "
"are allowed to connect."
msgstr ""
"Le démon distcc permet un contrôle d'accès basé sur l'adresse IP des clients "
"qui s'y connectent. Veuillez indiquer ici les hôtes ou réseaux qui seront "
"acceptés."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"You can list multiple hosts and/or networks, separated by spaces. Hosts are "
"represented by their IP address, networks have to be in CIDR notation, e.g. "
"\"192.168.1.0/24\"."
msgstr ""
"Vous pouvez indiquer plusieurs hôtes ou des réseaux entiers, séparés par des "
"espaces. Les hôtes sont représentés par leur adresse IP et les réseaux "
"doivent utiliser la notation CIDR, par exemple « 192.168.1.0/24 »."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"To change the list at a later point, you can run: 'dpkg-reconfigure distcc'."
msgstr ""
"Si vous souhaitez modifier la liste des réseaux autorisés plus tard, vous "
"pourrez utiliser la commande « dpkg-reconfigure distcc »."

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid "Listen interfaces:"
msgstr "Interfaces d'écoute :"

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid "The distcc daemon can be bound to a specific network interface."
msgstr "Le démon distcc peut être à l'écoute d'une interface spécifique."

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid ""
"You probably want to choose the interface of your local network by entering "
"its IP address. If distccd should listen on all interfaces, just enter "
"nothing."
msgstr ""

Bug#922456: gnome-menus: [INTL:fr] French program translation update

[Quentin Lejard]

Package: gnome-menus
Version: 3.31.4-3
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French translation, proofread by the
debian-l10n-french mailing list contributors.

This file should be put as fr.po in the appropriate place in
your package build tree.

Best regards,

Quentin Lejard


-- System Information:
Debian Release: 9.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.127-mainline-rev1 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Translation of gnome-menus package to French
# Copyright (C) 2019 Debian french l10n team
# This file is distributed under the same license as the gnome-menus package.
#
# Translations taken from the menu package
#
# French translation :
# (Bill Allombert , 2003.).
# Josselin Mouette , 2007.
# Jean-Philippe Guerard , 2003.
# Quentin Lejard , 2019.
msgid ""
msgstr ""
"Project-Id-Version: menu-section 2.1.7-2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-01-21 18:53-0500\n"
"PO-Revision-Date: 2019-02-06 18:14+0100\n"
"Last-Translator: Quentin LEJARD \n"
"Language-Team: French \n"
"Language: fr_FR\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Lokalize 2.0\n"

#: debian/desktop-files/ActionGames.directory.desktop.in:3
msgid "Action"
msgstr "Action"

#: debian/desktop-files/ActionGames.directory.desktop.in:4
msgid "Action games"
msgstr "Jeux d'action"

#. Translators: Do NOT translate or transliterate this text (this is an icon 
file name)!
#: debian/desktop-files/ActionGames.directory.desktop.in:6
msgid "weather-storm"
msgstr "weather-storm"

#: debian/desktop-files/Settings-System.directory.desktop.in:4
msgid "Administration"
msgstr "Administration"

#: debian/desktop-files/Settings-System.directory.desktop.in:5
msgid "Change system-wide settings (affects all users)"
msgstr ""
"Modifie globalement les paramètres du système (affecte tous les utilisateurs)"

#. Translators: Do NOT translate or transliterate this text (this is an icon 
file name)!
#: debian/desktop-files/Settings-System.directory.desktop.in:7
msgid "preferences-system"
msgstr "preferences-system"

#: debian/desktop-files/KidsGames.directory.desktop.in:3
msgid "Kids"
msgstr "Enfants"

#: debian/desktop-files/KidsGames.directory.desktop.in:4
msgid "Games for kids"
msgstr "Jeux pour les enfants"

#. Translators: Do NOT translate or transliterate this text (this is an icon 
file name)!
#: debian/desktop-files/KidsGames.directory.desktop.in:6
msgid "gnome-amusements"
msgstr "gnome-amusements"

#: debian/desktop-files/CardGames.directory.desktop.in:3
msgid "Cards"
msgstr "Cartes"

#: debian/desktop-files/CardGames.directory.desktop.in:4
msgid "Card games"
msgstr "Jeux de cartes"

#. Translators: Do NOT translate or transliterate this text (this is an icon 
file name)!
#: debian/desktop-files/CardGames.directory.desktop.in:6
msgid "gnome-aisleriot"
msgstr "gnome-aisleriot"

#: debian/desktop-files/Debian.directory.desktop.in:3
msgid "Debian"
msgstr "Debian"

#: debian/desktop-files/Debian.directory.desktop.in:4
msgid "The Debian menu"
msgstr "Le menu Debian"

#. Translators: Do NOT translate or transliterate this text (this is an icon 
file name)!
#: debian/desktop-files/Debian.directory.desktop.in:6
msgid "debian-logo"
msgstr "debian-logo"

#
#: debian/desktop-files/SimulationGames.directory.desktop.in:3
msgid "Simulation"
msgstr "Simulation"

#: debian/desktop-files/SimulationGames.directory.desktop.in:4
msgid "Simulation games"
msgstr "Jeux de simulation"

#
#: debian/desktop-files/BoardGames.directory.desktop.in:3
msgid "Board"
msgstr "Plateau"

#: debian/desktop-files/BoardGames.directory.desktop.in:4
msgid "Board games"
msgstr "Jeux de plateau"

#. Translators: Do NOT translate or transliterate this text (this is an icon 
file name)!
#: debian/desktop-files/BoardGames.directory.desktop.in:6
msgid "desktop"
msgstr "desktop"

#
#: debian/desktop-files/GnomeScience.directory.desktop.in:3
msgid "Science"
msgstr "Sciences"

#: debian/desktop-files/GnomeScience.directory.desktop.in:4

Bug#920940: nvidia-graphics-drivers: [INTL:fr] French debconf translation update

[Quentin Lejard]

Package: nvidia-graphics-drivers
Version: 390.87-6
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

Best regards,

Quentin Lejard


-- System Information:
Debian Release: 9.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.93-mainline-rev1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# French translation for nvidia-driver debconf templates.
# Copyright (C) 2009-2019 Debian French l10n team 

# This file is distributed under the same license as the nvidia-driver package.
#
# Translators:
# Christian Perrier , 2009, 2012, 2014.
# Quentin Lejard , 2019.
msgid ""
msgstr ""
"Project-Id-Version: nvidia-graphics-drivers\n"
"Report-Msgid-Bugs-To: nvidia-graphics-driv...@packages.debian.org\n"
"POT-Creation-Date: 2016-02-12 01:57+0100\n"
"PO-Revision-Date: 2019-01-15 19:27+0100\n"
"Last-Translator: Quentin LEJARD \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: boolean
#. Description
#. Translators, do not translate the ${substitution} ${variables}.
#. ${vendor} will be substituted with 'NVIDIA' or 'Fglrx' (without quotes, of
#. course), ${free_name} will become 'Nouveau' or 'Radeon' (no quotes, again)
#. and the ${*driver} variables will be replaced with package names.
#: ../nvidia-legacy-check.templates:3001
msgid "Install ${vendor} driver despite unsupported graphics card?"
msgstr ""
"Faut-il installer le pilote ${vendor} avec une carte graphique non gérée ?"

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"This system has a graphics card which is no longer handled by the ${vendor} "
"driver (package ${driver}). You may wish to keep the package installed - for "
"instance to drive some other card - but the card with the following chipset "
"won't be usable:"
msgstr ""
"La carte graphique de cette machine n'est plus gérée par le pilote ${vendor} "
"(paquet ${driver}). Vous pouvez préférer garder le paquet installé (par "
"exemple pour piloter une autre carte), mais dans ce cas, la carte graphique "
"suivante ne sera pas utilisable :"

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"The above card requires either the non-free legacy ${vendor} driver (package "
"${legacy_driver}) or the free ${free_name} driver (package ${free_driver})."
msgstr ""
"Cette carte a besoin soit du pilote constructeur ${vendor}, non libre, "
"fourni par le paquet ${legacy_driver} ou du pilote libre ${free_name} fourni "
"par le paquet ${free_driver}."

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"Use the update-glx command to switch between different installed drivers."
msgstr ""
"Utilisez la commande update-glx afin de choisir parmi les pilotes déja"
"installés."

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"Before the ${free_name} driver can be used you must remove ${vendor} "
"configuration from xorg.conf (and xorg.conf.d/)."
msgstr ""
"Avant de pouvoir utiliser le pilote ${free_name}, il est nécessaire de "
"supprimer la configuration de ${vendor} dans le fichier xorg.conf (ou dans "
"un des fichiers de xorg.conf.d/)."

Bug#920496: distcc: [INTL:fr] French debconf translation update

[Quentin Lejard]

Package: distcc
Version: 3.3.2-5
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

Best regards,

Quentin Lejard


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.93-mainline-rev1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Translation of distcc debconf templates to French
# Copyright (C) 2007 Christian Perrier 
# Copyright (C) 2009-2019 Debian French l10n team 

# This file is distributed under the same license as the distcc package.
#
#
# Christian Perrier , 2007, 2008, 2009, 2010.
# Quentin Lejard , 2019.
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: dis...@packages.debian.org\n"
"POT-Creation-Date: 2018-12-22 18:41+0100\n"
"PO-Revision-Date: 2019-01-18 12:53+0100\n"
"Last-Translator: Quentin LEJARD \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid "Start the distcc daemon on startup?"
msgstr "Faut-il lancer le démon distcc au démarrage ?"

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid ""
"distcc can be run as a daemon, listening on port 3632 for incoming "
"connections."
msgstr ""
"Distcc peut fonctionner avec un démon qui sera à l'écoute des connexions "
"entrantes sur le port 3632."

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid ""
"You have the option of starting the distcc daemon automatically on the "
"computer startup. If in doubt, it's advised not to start it automatically on "
"startup. If you later change your mind, you can run: 'dpkg-reconfigure "
"distcc'."
msgstr ""
"Vous pouvez lancer le démon distcc automatiquement au démarrage du système. "
"Dans le doute, vous devriez vous en abstenir. Si vous souhaitez modifier ce "
"réglage plus tard, vous pourrez utiliser la commande « dpkg-reconfigure "
"distcc »."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid "Allowed client networks:"
msgstr "Réseaux clients autorisés :"

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"The distcc daemon implements access control based on the IP address of the "
"client, that is trying to connect. Only the hosts or networks listed here "
"are allowed to connect."
msgstr ""
"Le démon distcc permet un contrôle d'accès basé sur l'adresse IP des clients "
"qui s'y connectent. Veuillez indiquer ici les hôtes ou réseaux qui seront "
"acceptés."

#. Type: string
#. Description
#: ../distcc.templates:2001
#| msgid ""
#| "You can list multiple hosts and/or networks, separated by spaces. Hosts "
#| "are represented by their IP address, networks have to be in CIDR "
#| "notation, f.e. \"192.168.1.0/24\"."
msgid ""
"You can list multiple hosts and/or networks, separated by spaces. Hosts are "
"represented by their IP address, networks have to be in CIDR notation, e.g. "
"\"192.168.1.0/24\"."
msgstr ""
"Vous pouvez indiquer plusieurs hôtes ou des réseaux entiers, séparés par des "
"espaces. Les hôtes sont représentés par leur adresse IP et les réseaux "
"doivent utiliser la notation CIDR, par exemple « 192.168.1.0/24 »."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"To change the list at a later point, you can run: 'dpkg-reconfigure distcc'."
msgstr ""
"Si vous souhaitez modifier la liste des réseaux autorisés plus tard, vous "
"pourrez utiliser la commande « dpkg-reconfigure distcc »."

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid "Listen interfaces:"
msgstr "Interfaces d'écoute :"

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid "The distcc daemon can be bound to a specific network interface."
msgstr "Le démon distcc peut être à l'écoute d'une interface spécifique."

#. Type: string
#. Description
#

Bug#918354: deborphan: [INTL:fr] French program translation update

[Quentin Lejard]

Package: deborphan
Version: 1.7.31
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French translation, proofread by the
debian-l10n-french mailing list contributors.

This file should be put as fr.po in the appropriate place in
your package build tree.

Best regards,

Quentin Lejard
# French translation of deborphan manual pages
# Copyright (C) 2006, 2008, 2010, 2018, Debian French l10n team 
.
# This file is distributed under the same license as the deborphan package.
#
# Jean-Luc Coulon (f5ibh) , 2006.
# Guilhelm Panaget , 2006.
# Christian Perrier , 2008.
# David Prévot , 2010.
# Quentin Lejard , 2018, 2019.
# Alban Vidal , 2018, 2019.
msgid ""
msgstr ""
"Project-Id-Version: deborphan 1.7.31\n"
"POT-Creation-Date: 2018-12-09 20:27+0100\n"
"PO-Revision-Date: 2019-01-02 19:39+0100\n"
"Last-Translator: quentin \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

# type: TH
#. type: TH
#: ../orphaner.8:1
#, no-wrap
msgid "orphaner"
msgstr "orphaner"

# type: TH
#. type: TH
#: ../orphaner.8:1 ../editkeep.8:1
#, no-wrap
msgid "April 2004"
msgstr "Avril 2004"

# type: SH
#.  Copyright (C) 2000, 2001, 2002, 2003 Cris van Pelt
#.  Copyright (C) 2003, 2004, 2005, 2006 Peter Palfrader
#.  Copyright (C) 2005 Daniel Déchelotte
#.  Copyright (C) 2008 Andrej Tatarenkow
#.  Copyright (C) 2008, 2009 Carsten Hey
#. type: SH
#: ../orphaner.8:4 ../editkeep.8:4 ../deborphan.1:8
#, no-wrap
msgid "NAME"
msgstr "NOM"

# type: Plain text
#. type: Plain text
#: ../orphaner.8:7
msgid "orphaner - frontend for deborphan"
msgstr "orphaner - interface pour deborphan"

# type: SH
#. type: SH
#: ../orphaner.8:8 ../editkeep.8:8 ../deborphan.1:10
#, no-wrap
msgid "SYNOPSIS"
msgstr "SYNOPSIS"

# type: Plain text
#. type: Plain text
#: ../orphaner.8:11
#| msgid "B [B<--help>|B<--purge>] [I]"
msgid "B [B<--help>|B<--purge>] [\\,I\\/]"
msgstr "B [B<--help>|B<--purge>] [\\,I\\/]"

# type: SH
#. type: SH
#: ../orphaner.8:12 ../editkeep.8:12 ../deborphan.1:13
#, no-wrap
msgid "DESCRIPTION"
msgstr "DESCRIPTION"

# type: Plain text
#. type: Plain text
#: ../orphaner.8:20
msgid ""
"B is a neat frontend for B displaying a list of "
"orphaned packages with dialog or whiptail. Packages may be selected for "
"removal with B which is then called to do the work. After removal a "
"new list of orphaned packages is gathered from deborphan. The program ends "
"when either `Cancel' is pressed or no package is marked for removal."
msgstr ""
"B est une interface pour B utilisant B ou "
"B qui affiche la liste des paquets orphelins. Les paquets peuvent "
"être sélectionnés pour être supprimés avec B qui sera alors appelé "
"pour effectuer la suppression. Après suppression, la liste des paquets "
"orphelins est réactualisée. Le programme rend la main lorsque «\\ Annuler\\ "
"» est choisi ou bien lorsqu'aucun paquet n'est choisi pour suppression."

# type: Plain text
#. type: Plain text
#: ../orphaner.8:23
msgid ""
"After you removed a package, all new orphaned packages are shown at the top "
"of the list separated by + from the old list."
msgstr ""
"Après suppression d'un paquet, les paquets nouvellement orphelins sont "
"listés, séparés des anciens par une ligne «\\ +\\ »."

# type: Plain text
#. type: Plain text
#: ../orphaner.8:29
msgid ""
"Orphaner also shows two additional buttons: `Simulate' and `Help'.  "
"`Simulate' does like its name suggest only a simulation of removing and "
"shows the result that would appear after real removing. So you can see the "
"packages, which will become orphaned and you can select them and remove all "
"packages with one B call."
msgstr ""
"Orphaner propose deux autres boutons\\ : «\\ Simuler\\ » et «\\ Aide\\ ». "
"Comme son nom l'indique, «\\ Simuler\\ » permet de simuler la suppression en "
"montrant la liste qui apparaîtrait s'il s'agissait d'une véritable "
"suppression. Il est ainsi possible de voir les paquets qui seraient rendus "
"orphelins suite à cette suppression et de les sélectionner aussi pour faire "
"une suppression globale avec un seul appel de B."

# type: Plain text
#. type: Plain text
#: ../orphaner.8:32
msgid ""
"`Help' shows you the status 

Bug#905786: libvncserver1: Use-after-free on shutdown when clients are still connected (causing issue for Virtualbox)

[Quentin BUATHIER]

Package: libvncserver1
Version: 0.9.11+dfsg-1+deb9u1
Severity: important
Tags: patch

In the upstream source of the project, there is an use-after-free that can lead
to an infinite wait of a non-existing thread during the shutdown of the VNC
server if some clients are still connected.

This causing an issue in Virtualbox which uses this package when a VNC client
is connected and that we shutdown the VM (the VM will be stuck in a buggy
state). See https://www.virtualbox.org/ticket/17396 for the ticket in
Virtualbox's bug tracker for more informations.

There is actually a pull request on upstream fixing this issue
(https://github.com/LibVNC/libvncserver/pull/238). There is also another issue,
a segmentation fault in the same use case when we are using a multi-threaded
VNC server (also fixed by the same pull request).

Virtualbox need both fixes to work correctly without a segmentation fault or a
infinite wait and probably some others packages using libvncserver.

The issue isn't present on Jessie with the version 0.9.9 of the package.



-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libvncserver1 depends on:
ii  libc62.24-11+deb9u3
ii  libgcrypt20  1.7.6-2+deb9u3
ii  libgnutls30  3.5.8-5+deb9u3
ii  libjpeg62-turbo  1:1.5.1-2
ii  zlib1g   1:1.2.8.dfsg-5

libvncserver1 recommends no packages.

libvncserver1 suggests no packages.

Bug#900936: Editing /etc/geoclue/geoclue.conf

[quentin g]

Adding the following lines to /etc/geoclue/geoclue.conf seems to be a good
workaround:

[redshift]
allowed=true
system=false
users=

I also have the demo agent installed, although I don't know if its important


-- 
My git repository:
https://github.com/freezeeedos

Bug#900936: Editing /etc/geoclue/geoclue.conf

[quentin g]

Also, here is the source of the workaround
https://github.com/jonls/redshift/issues/158

2018-06-14 5:08 GMT+02:00 quentin g :

> Adding the following lines to /etc/geoclue/geoclue.conf seems to be a good
> workaround:
>
> [redshift]
> allowed=true
> system=false
> users=
>
> I also have the demo agent installed, although I don't know if its
> important
>
>
> --
> My git repository:
> https://github.com/freezeeedos
>



-- 
My git repository:
https://github.com/freezeeedos

Bug#884972: python-cryptography: [Debian Buster] 'X509_up_ref' call doesn't exist on version 2.1.4-1

[BUISSON-DEBON Quentin]

 

Package: python-cryptography
Subject: python-cryptography: [Debian Buster] 'X509_up_ref' call doesn't
exist on version 2.1.4-1
Version: 2.1.4-1
Severity: important

Hi,

I think I need a python maintainer here :

I met an issue after an upgrade from Debian Buster of the package named
python-
cryptography (1.9-1 to 2.1.4-1 version), the issue is this error return
:
http://pastebin.centos.org/472531/ => the line 313 can be seem here :
/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py (line 313)

After reading https://pypi.python.org/pypi/pyOpenSSL I can see that
"python-
cryptography" version >= 2.1.4 is needed
My installed version of 'python-cryptography' is 2.1.4-1 (apt-cache
policy
python-cryptography => 2.1.4-1), so it's ok here :)

It seems like my python-cryptography doesn't have the "X509_up_ref" call

Here is my 'SSL.py' installed : http://pastebin.centos.org/472551/
(absolute
path = /usr/lib/python2.7/dist-packages/OpenSSL/SSL.py)
If I execute a "dpkg -L python-cryptography | grep '.py' | xargs grep
X509_up_ref" => nothing is returned => strange...

Thank you in advance for your reading ! :)

(PS : I hope a fix will be available soon, some python scripts I'm using
doesn't work anymore since this upgrade and it seems that in Buster I
can't
revert the version for this package)

--

Regards,
BUISSON-DEBON Quentin.

-- System Information:
Debian Release: buster/sid
 APT prefers testing
 APT policy: (900, 'testing'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-cryptography depends on:
ii libc6 2.25-3
ii libssl1.1 1.1.0g-2
ii python 2.7.14-4
ii python-asn1crypto 0.22.0-1
pn python-cffi-backend-api-max 
pn python-cffi-backend-api-min 
ii python-enum34 1.1.6-2
ii python-idna 2.5-1
ii python-ipaddress 1.0.17-1
ii python-six 1.11.0-1

python-cryptography recommends no packages.

Versions of packages python-cryptography suggests:
pn python-cryptography-doc 
pn python-cryptography-vectors 

-- no debconf information

 

Bug#883169: environment-modules not working with `sh' or `su'

[MINSTER Quentin]

Package: environment-modules
Version: 4.0.0-1
Source: modules

The contents of the file /usr/share/modules/init/sh are messed up and do not 
define the `module` function, thus breaking environment-modules.
This file is sourced by /etc/profile.d/modules.sh when the shell is /bin/sh or 
anything unknown (e.g. `-su').

Current behavior:
$ sudo su -
# module list
-su: module: command not found

Expected behavior:
$ sudo su -
# module list
Currently Loaded Modulefiles:


This is because the debian/patches/paths.patch file in the Debian source 
package patches modules-4.0.0~beta/init/sh.in with messed up contents.
This patch should be fixed (for sh.in, the bash.in part is fine).

I am using Debian buster/sid. (The bug is not present on Debian 9.1, with 
environment-modules 3.2.10-10.)

Bug#879821: libgles1-glvnd-nvidia:amd64: upgrade failure to 375.82-6

[quentin . caillard]

Same bug here

dpkg: des problèmes de dépendances empêchent la configuration de
libgles1-glvnd-nvidia:i386 :
 libgles1-glvnd-nvidia:amd64 (375.82-6) casse libgles1 (>> 0) et est
dépaqueté mais non configuré.
libgles1-glvnd-nvidia:i386 (375.82-6) fournit libgles1.

dpkg: erreur de traitement du paquet libgles1-glvnd-nvidia:i386 (
--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de
libgles1-glvnd-nvidia:amd64 :
 libgles1-glvnd-nvidia:i386 (375.82-6) casse libgles1 (>> 0) et est
dépaqueté mais non configuré.
libgles1-glvnd-nvidia:amd64 (375.82-6) fournit libgles1.

dpkg: erreur de traitement du paquet libgles1-glvnd-nvidia:amd64 (
--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de
libgles-nvidia1:i386 :
 libgles-nvidia1:i386 dépend de libgles1 (>= 0.2.999) | libgles1-glvnd-
nvidia ; cependant :
  Le paquet libgles1-glvnd-nvidia:i386 qui fournit libgles1 n'est pas
encore configuré.
 Le paquet libgles1-glvnd-nvidia:i386 n'est pas encore configuré.

dpkg: erreur de traitement du paquet libgles-nvidia1:i386 (
--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de
libgles-nvidia1:amd64 :
 libgles-nvidia1:amd64 dépend de libgles1 (>= 0.2.999) | libgles1-
glvnd-nvidia ; cependant :
  Le paquet libgles1 n'est pas installé.
  Le paquet libgles1-glvnd-nvidia:amd64 qui fournit libgles1 n'est pas
encore configuré.
 Le paquet libgles1-glvnd-nvidia:amd64 n'est pas encore configuré.

dpkg: erreur de traitement du paquet libgles-nvidia1:amd64 (
--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 libgles1-glvnd-nvidia:i386
 libgles1-glvnd-nvidia:amd64
 libgles-nvidia1:i386
 libgles-nvidia1:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have i386 packages installed.

On Thu, 26 Oct 2017 21:57:40 +0100 Luca Boccassi 
wrote:
> On Thu, 2017-10-26 at 12:55 +0200, Vincent Lefevre wrote:
> > Package: libgles1-glvnd-nvidia
> > Version: 375.82-6
> > Severity: grave
> > Justification: renders package unusable
> > 
> > In the upgrade to 375.82-6:
> > 
> > Unpacking nvidia-kernel-dkms (375.82-6) over (375.82-5) ...
> > Preparing to unpack .../34-nvidia-legacy-check_375.82-6_amd64.deb
...
> > Unpacking nvidia-legacy-check (375.82-6) over (375.82-5) ...
> > Preparing to unpack .../35-nvidia-driver-libs-i386_375.82-
6_i386.deb
> > ...
> > Unpacking nvidia-driver-libs-i386:i386 (375.82-6) over (375.82-5)
...
> > Processing triggers for mime-support (3.60) ...
> > Setting up libnvidia-eglcore:amd64 (375.82-6) ...
> > Setting up libnvidia-eglcore:i386 (375.82-6) ...
> > Processing triggers for desktop-file-utils (0.23-2) ...
> > Setting up libnvidia-glcore:amd64 (375.82-6) ...
> > Setting up libnvidia-glcore:i386 (375.82-6) ...
> > Processing triggers for libc-bin (2.24-17) ...
> > Setting up nvidia-egl-common (375.82-6) ...
> > Setting up nvidia-vulkan-common (375.82-6) ...
> > Setting up nvidia-legacy-check (375.82-6) ...
> > Processing triggers for man-db (2.7.6.1-2) ...
> > Setting up nvidia-alternative (375.82-6) ...
> > Processing triggers for nvidia-alternative (375.82-6) ...
> > Setting up libglx-nvidia0:amd64 (375.82-6) ...
> > Setting up nvidia-vulkan-icd:amd64 (375.82-6) ...
> > Setting up nvidia-kernel-support (375.82-6) ...
> > Setting up nvidia-vdpau-driver:amd64 (375.82-6) ...
> > Setting up libegl-nvidia0:amd64 (375.82-6) ...
> > Setting up libegl-nvidia0:i386 (375.82-6) ...
> > Setting up libgles-nvidia2:i386 (375.82-6) ...
> > Setting up libgles-nvidia2:amd64 (375.82-6) ...
> > Setting up libnvidia-cfg1:amd64 (375.82-6) ...
> > Setting up libnvidia-cfg1:i386 (375.82-6) ...
> > dpkg: dependency problems prevent configuration of libgles1-glvnd-
> > nvidia:amd64:
> >  libgles1-glvnd-nvidia:i386 (375.82-6) breaks libgles1 (>> 0) and
is
> > unpacked but not configured.
> >   libgles1-glvnd-nvidia:amd64 (375.82-6) provides libgles1.
> > 
> > dpkg: error processing package libgles1-glvnd-nvidia:amd64 (
> > --configure):
> >  dependency problems - leaving unconfigured
> > dpkg: dependency problems prevent configuration of libgles1-glvnd-
> > nvidia:i386:
> >  libgles1-glvnd-nvidia:amd64 (375.82-6) breaks libgles1 (>> 0) and
is
> > unpacked but not configured.
> >   libgles1-glvnd-nvidia:i386 (375.82-6) provides libgles1.
> > 
> > dpkg: error processing package libgles1-glvnd-nvidia:i386 (
> > --configure):
> >  dependency problems - leaving unconfigured
> > Setting up nvidia-kernel-dkms (375.82-6) ...
> > [...]
> > Setting up libnvidia-ml1:amd64 (375.82-6) ...
> > dpkg: dependency problems prevent configuration of libgles-
> > nvidia1:amd64:

Bug#872046: isync: does not synchronize yahoo email accounts anymore

[Quentin Hibon]

the error message you're getting is just an elaborate way of saying
"login failed". judging by the mozilla bug, the problem might be that
you're using different capitalization of your login name.


I don't get that from the mozilla bug, they mention capitalization of 
mechanisms, but not of logins, see for instance this diff:

https://bugzilla.mozilla.org/attachment.cgi?id=351=diff
where they replace "login" and "plain" by "LOGIN" and "PLAIN".


alternatively, the login *is* wrong, because the password expired or
something like that.

if neither applies, try configuring "AuthMech LOGIN".


AuthMech LOGIN works indeed (so my logins and passwords are correct).

Bug#863484: dpkg-buildpackage: build error for some package when whitespace in the working directory path

[Quentin C.]

Package: dpkg-dev
Version: 1.18.24
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Whitespace in the working directory path

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

$ mkdir "/tmp/a path with whitespace/"
$ cd "/tmp/a path with whitespace"
$ apt-get source grep
$ cd grep-2.27
$ dpkg-buildpackage -us -uc

   * What was the outcome of this action?

...
 debian/rules build
test -x debian/rules
mkdir -p "."
set -e;   mv ./build-aux/config.guess
./build-aux/config.guess.cdbs-orig; cp --remove-destination
/usr/share/misc/config.guess ./build-aux/config.guess;
set -e;   mv ./build-aux/config.sub ./build-aux/config.sub.cdbs-orig; cp
--remove-destination /usr/share/misc/config.sub ./build-aux/config.sub;
dh_autoreconf 
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path
'*/CVS/*' \) -a  -type f -exec md5sum {} + >
debian/autoreconf.before
autoreconf -f -i
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path
'*/CVS/*' \) -a  -type f -exec md5sum {} + >
debian/autoreconf.after
touch debian/stamp-autotools-files
chmod a+x /tmp/a path with whitespace/grep-2.27/./configure
chmod: impossible d'accéder à 'path': Aucun fichier ou dossier de ce
type
chmod: impossible d'accéder à 'with': Aucun fichier ou dossier de ce
type
chmod: impossible d'accéder à 'whitespace/grep-2.27/./configure': Aucun
fichier ou dossier de ce type
/usr/share/cdbs/1/class/autotools.mk:44 : la recette pour la cible
« debian/stamp-autotools » a échouée
make: *** [debian/stamp-autotools] Erreur 1
dpkg-buildpackage: erreur: debian/rules build a produit une erreur de
sortie de type 2
$ 

Try with some other package:
  xpdf is working
  python3 is working
  gzip is working
  lzo2 is not working


--
Quentin C.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 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 dpkg-dev depends on:
ii  binutils  2.28-5
ii  bzip2 1.0.6-8.1
ii  libdpkg-perl  1.18.24
ii  make  4.1-9.1
ii  patch 2.7.5-1+b2
pn  perl:any  
ii  tar   1.29b-1.1
ii  xz-utils  5.2.2-1.2+b1

Versions of packages dpkg-dev recommends:
ii  build-essential  12.3
ii  clang-3.5 [c-compiler]   1:3.5.2-3~bpo8+2
ii  clang-3.8 [c-compiler]   1:3.8.1-23
ii  clang-3.9 [c-compiler]   1:3.9.1-8
ii  fakeroot 1.21-3.1
ii  gcc [c-compiler] 4:6.3.0-4
ii  gcc-4.6 [c-compiler] 4.6.3-14
ii  gcc-4.8 [c-compiler] 4.8.4-1
ii  gcc-4.9 [c-compiler] 4.9.2-10
ii  gcc-6 [c-compiler]   6.3.0-16
ii  gnupg2.1.18-6
ii  gnupg2   2.1.18-6
ii  gpgv 2.1.18-6
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2017.01.20

-- no debconf information

Bug#846098: Works for me

[Quentin Lefebvre]

Dear Maintainer,

I've read that Keepass2 is going to be removed from Debian testing.
Perhaps I misunderstood this bug report.
Anyway, I'm surprised because my keepass2 works perfectly (though much 
slower to open a database than on Windows).


I've an up-to-date Debian testing install, running with KDE.

I can of course provide additional information.

Best,
Quentin

Bug#845139: clementine: does not append music to the playlist in the same order as the file explorer

[Quentin Hibon]

Package: clementine
Version: 1.2.3+dfsg-2+b1
Severity: normal

Dear Maintainer,

  * What led up to the situation?

  clementine is configured to append to the current playlist by default, and
  play the song(s) appended if none is currently playing.

  * What exactly did you do (or not do) that was effective (or
ineffective)?

  I use a file explorer (either the default one packaged with Gnome or
  PCManFM), select a few songs, and open them with clementine (using the
  context menu or a drag-and-drop).

  * What was the outcome of this action?

  Files are not appended as ordered in the file explorer, but in a seemingly
  random order instead. If I try to add them again right after, they are
  appended in the right order.

  * What outcome did you expect instead?

  Songs should be added in the order displayed in the file explorer, or at
  least in a deterministic manner.


-- System Information:
Debian Release: 8.6
 APT prefers stable
 APT policy: (800, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clementine depends on:
ii  gstreamer0.10-plugins-base   0.10.36-2
ii  gstreamer0.10-plugins-good   0.10.31-3+nmu4+b1
ii  gstreamer0.10-plugins-ugly   0.10.19-2.1
ii  libc62.19-18+deb8u6
ii  libcdio130.83-4.2
ii  libchromaprint0  1.2-1
ii  libechonest2.1   2.1.0-2
ii  libfftw3-double3 3.3.4-2
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.42.1-1+b1
ii  libgpod4 0.8.3-1.1+b1
ii  libgstreamer-plugins-base0.10-0  0.10.36-2
ii  libgstreamer0.10-0   0.10.36-1.5
ii  libimobiledevice41.1.6+dfsg-3.1
ii  liblastfm1   1.0.8-2
ii  libmtp9  1.1.8-1+b1
ii  libprojectm2 2.1.0+dfsg-1+b1
ii  libprotobuf9 2.6.1-1
ii  libqca2  2.0.3-6
ii  libqjson00.8.1-3
ii  libqt4-dbus  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-network   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-opengl4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-sql   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-sql-sqlite4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore4   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqxt-gui0  0.6.2-1+b1
ii  libstdc++6   4.9.2-10
ii  libtag1c2a   1.9.1-2.1
ii  libusb-1.0-0 2:1.0.19-1
ii  libx11-6 2:1.6.2-3
ii  libxml2  2.9.1+dfsg1-5+deb8u3
ii  projectm-data2.1.0+dfsg-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages clementine recommends:
ii  gstreamer0.10-alsa0.10.36-2
ii  gstreamer0.10-pulseaudio  0.10.31-3+nmu4+b1

clementine suggests no packages.

-- no debconf information

Bug#841454: bsdmainutils: [hexdump] can't handle lengths over 2^31 on 64-bit system

[Quentin Minster]

Package: bsdmainutils
Version: 9.0.11
Severity: normal
Tags: lfs upstream

Dear Maintainer,

hexdump chokes when given a length argument over 2^31-1, e.g.:
  hexdump -n 40
with the following message:
  hexdump: 40: bad length value

This is not an uncommon value to use when dealing with physical devices, e.g.
USB sticks, and shouldn't be a problem on a 64bit system (hexdump itself is
indeed a 64bit binary).
Do note however that argument `-s' does not exhibit this behavior, so it is
possible to hexdump a whole USB stick in increments of 2^31-1 bytes.

I ran it through GDB and it occurs that hexdump is using atoi() to parse the
length argument, hence the limitation to 2^31-1, while it uses strtoll() to
parse the skip argument (hence the absence of limitation even on a 32bit
system).
I've also been looking at the source for hexdump from util-linux (not the same
upstream as Debian's hexdump, which comes from bsdmainutils), and it appears
they have been using 64bit-wide datatypes (as far as Unix is concerned) for the
length argument since as far back as 2011.

So I'm wondering, is there anything preventing Debian to switch over to
util-linux's hexdump?
I haven't checked what most other distros do, but at least Gentoo Linux's
hexdump comes from util-linux.

If that's not an option, then bsdmainutils' hexdump should be fixed.

Cheers,
Quentin


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

Kernel: Linux 4.6.0-1-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
Init: systemd (via /run/systemd/system)

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.28.2-1
ii  debianutils  4.8
ii  libbsd0  0.8.3-1
ii  libc62.24-4
ii  libncurses5  6.0+20160917-1
ii  libtinfo56.0+20160917-1

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:6.1.1-1
pn  vacation  
ii  wamerican [wordlist]  7.1-1
ii  whois 5.2.12

-- no debconf information

Bug#794316: can't unlock desktop

[Quentin BUISSON-DEBON]

Package: gdm3
Version: 3.14.1-7
Followup-For: Bug #794316

Hi,

>>My laptop screen had been locked for a while.  I typed the password and
>>nothing happened.  After a few seconds, the screen went blank again.

Same issue here but without the blank screen --> Just a freeze of gdm3 with the
login screen.

when i do a "CTRL+ALT+F2", log in with my user then type "sudo servie gdm3
restart", my laptop in unfreeze, I can log in again on Gnome3, but i loose my
sessins windows with this way

Hope it will help you



-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.37-3+b1
ii  adduser   3.113+nmu3
ii  cinnamon [x-window-manager]   2.2.16-5
ii  dconf-cli 0.22.0-1
ii  dconf-gsettings-backend   0.22.0-1
ii  debconf [debconf-2.0] 1.5.56
ii  gir1.2-gdm3   3.14.1-7
ii  gnome-session [x-session-manager] 3.14.0-2
ii  gnome-session-bin 3.14.0-2
ii  gnome-settings-daemon 3.14.2-3
ii  gnome-shell   3.14.4-1~deb8u1
ii  gnome-terminal [x-terminal-emulator]  3.14.1-1+deb8u1
ii  gsettings-desktop-schemas 3.14.1-1
ii  kde-window-manager [x-window-manager] 4:4.11.13-2
ii  konsole [x-terminal-emulator] 4:4.14.2-1
ii  libaccountsservice0   0.6.37-3+b1
ii  libaudit1 1:2.4-1+b1
ii  libc6 2.19-18+deb8u4
ii  libcanberra-gtk3-00.30-2.1
ii  libcanberra0  0.30-2.1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libgdm1   3.14.1-7
ii  libglib2.0-0  2.42.1-1+b1
ii  libglib2.0-bin2.42.1-1+b1
ii  libgtk-3-03.14.5-1+deb8u1
ii  libpam-modules1.1.8-3.1+deb8u1+b1
ii  libpam-runtime1.1.8-3.1+deb8u1
ii  libpam-systemd215-17+deb8u4
ii  libpam0g  1.1.8-3.1+deb8u1+b1
ii  librsvg2-common   2.40.5-1+deb8u2
ii  libselinux1   2.3-2
ii  libsystemd0   215-17+deb8u4
ii  libwrap0  7.6.q-25
ii  libx11-6  2:1.6.2-3
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.1-1+b1
ii  libxrandr22:1.4.2-1+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  lxsession [x-session-manager] 0.5.1-2
ii  lxterminal [x-terminal-emulator]  0.2.0-1
ii  marco [x-window-manager]  1.8.2+dfsg1-6
ii  mate-session-manager [x-session-manager]  1.8.1-8
ii  mate-terminal [x-terminal-emulator]   1.8.1+dfsg1-4
ii  metacity [x-window-manager]   1:3.14.3-1
ii  muffin [x-window-manager] 2.2.6-4
ii  mutter [x-window-manager] 3.14.4-1~deb8u1
ii  openbox [x-window-manager]3.5.2-8
ii  policykit-1   0.105-8
ii  terminator [x-terminal-emulator]  0.97-4
ii  ucf   3.0030
ii  x11-common1:7.7+7
ii  x11-xserver-utils 7.7+3+b1
ii  xfce4-session [x-session-manager] 4.10.1-10
ii  xfce4-terminal [x-terminal-emulator]  0.6.3-1+b1
ii  xfwm4 [x-window-manager]  4.10.1-3
ii  xterm [x-terminal-emulator]   312-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.14.0-1
ii  desktop-base   8.0.2
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils  7.7+1
ii  xserver-xephyr 2:1.16.4-1
ii  xserver-xorg   1:7.7+7
ii  zenity 3.14.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.14.0-4+deb8u1
ii  libpam-gnome-keyring  3.14.0-1+b1

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3

Bug#804857: linux: New feature: enable CONFIG_NO_HZ_FULL and CONFIG_RCU_NOCB_CPU/CONFIG_RCU_NOCB_CPU_NONE

[Quentin Deldycke]

Source: linux
Severity: wishlist

Dear Maintainer,

Could you please enable kernel options CONFIG_NO_HZ_FULL, CONFIG_RCU_NOCB_CPU 
and CONFIG_RCU_NOCB_CPU_NONE.

As explained in: https://www.kernel.org/doc/Documentation/timers/NO_HZ.txt

This options:
 - Don't modify default kernel behavior
 - Enable kernel command line nohz_full to enable tickless cpus
 - Enable kernel command line rcu_nocbs to offload rcu callbacks

The combination of these parameters + cpu-pinning of virtual machines greatly 
improve performance.
It also reduces latency in these virtual machines as the host system doesn't 
try to use it. (if your cgroup is correctly made)

These parameters are disabled in all debian kernels.
These parameters are enabled for various linux distribution by default without 
problem. (rhel 7 being one of them)
  (note that rhel 7 uses CONFIG_RCU_NOCB_CPU_ALL and user can pin offload 
kthreads to a core)

The usage of CONFIG_RCU_NOCB_CPU_NONE doesn't offload by default. But possibly 
this behavior is not the best.


Quentin.

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

Kernel: Linux 4.3.0-rc7-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#451535: Bump

[Quentin]

Bump. This is a most annoying bug and it's been around for way too long.

Colin Watson suggested around 2011/09/09 that he had a workable fix.
Is it still true? Why wasn't it committed in the end? How can we move 
forward with this?


Cheers,
Quentin

Bug#783251: ufw: Ufw autostarts wrongly by itself after Wheezy Jessie upgrade

[Quentin Berling]

Hi,

Im still having the problem.

I just did :


# ufw disable

# reboot

# ufw status 
ERROR: problem running ip6tables

# /usr/share/ufw/check-requirements 
Has python: pass (binary: python2.7, version: 2.7.9, py2)
Has iptables: pass
Has ip6tables: pass

Has /proc/net/dev: pass
Has /proc/net/if_inet6: pass

This script will now attempt to create various rules using the iptables
and ip6tables commands. This may result in module autoloading (eg, for
IPv6).
Proceed with checks (Y/n)? Y
== IPv4 ==
Creating ufw-check-requirements... done
Inserting RETURN at top of ufw-check-requirements... done
TCP: pass
UDP: pass
destination port: pass
source port: pass
ACCEPT: pass
DROP: pass
REJECT: pass
LOG: pass
hashlimit: pass
limit: pass
state (NEW): pass
state (RELATED): pass
state (ESTABLISHED): pass
state (INVALID): pass
state (new, recent set): pass
state (new, recent update): pass
state (new, limit): pass
interface (input): pass
interface (output): pass
multiport: pass
comment: pass
addrtype (LOCAL): pass
addrtype (MULTICAST): pass
addrtype (BROADCAST): pass
icmp (destination-unreachable): pass
icmp (source-quench): pass
icmp (time-exceeded): pass
icmp (parameter-problem): pass
icmp (echo-request): pass

== IPv6 ==
Creating ufw-check-requirements6... done
Inserting RETURN at top of ufw-check-requirements6... done
TCP: pass
UDP: pass
destination port: pass
source port: pass
ACCEPT: pass
DROP: pass
REJECT: pass
LOG: pass
hashlimit: pass
limit: pass
state (NEW): pass
state (RELATED): pass
state (ESTABLISHED): pass
state (INVALID): pass
state (new, recent set): pass
state (new, recent update): pass
state (new, limit): pass
interface (input): pass
interface (output): pass
multiport: pass
comment: pass
icmpv6 (destination-unreachable): pass
icmpv6 (packet-too-big): pass
icmpv6 (time-exceeded): pass
icmpv6 (parameter-problem): pass
icmpv6 (echo-request): pass
icmpv6 with hl (neighbor-solicitation): pass
icmpv6 with hl (neighbor-advertisement): pass
icmpv6 with hl (router-solicitation): pass
icmpv6 with hl (router-advertisement): pass
ipv6 rt: pass

All tests passed




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

Bug#783251: ufw: Ufw autostarts wrongly by itself after Wheezy Jessie upgrade

[Quentin Berling]

Package: ufw
Version: 0.33-2
Severity: important
Tags: ipv6

Dear Maintainer,

I upgraded my Wheezy server to Jessie a few days ago.
Now, everytime I reboot my server, ufw autostarts wrongly. By 
wrongly, I mean that ufw should be disabled but instead ufw status return an 
ip6tables (see the attached privatepaste) error and ufw seems to block some 
ports?.
You'll see in the bug report that /etc/init.d/ufw isn't there anymore, 
it's because I mved it out of the directory. However, ufw still autostarts by 
itself.
I have of course already done ufw disable countless times.
The fix is to ufw disable  ufw enable everytime the server reboot 
(even if ufw was previously disabled). http://privatepaste.com/97f2611c62
I think the ip6tables error is caused by an early? start of ufw, so it 
may be a good start to investigate what cause it to start...

Thanks for your help, Quentin


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-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/bash
Init: systemd (via /run/systemd/system)

Versions of packages ufw depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  iptables   1.4.21-2+b1
ii  python33.4.2-2
pn  python3:anynone
ii  ucf3.0030

ufw recommends no packages.

Versions of packages ufw suggests:
ii  rsyslog  8.4.2-1

-- Configuration Files:
/etc/default/ufw changed:
IPV6=yes
DEFAULT_INPUT_POLICY=DROP
DEFAULT_OUTPUT_POLICY=ACCEPT
DEFAULT_FORWARD_POLICY=ACCEPT
DEFAULT_APPLICATION_POLICY=SKIP
MANAGE_BUILTINS=no
IPT_MODULES=nf_conntrack_ftp nf_nat_ftp nf_conntrack_netbios_ns

/etc/init.d/ufw [Errno 2] Aucun fichier ou dossier de ce type: 
u'/etc/init.d/ufw'

-- debconf information:
* ufw/existing_configuration:
  ufw/allow_custom_ports:
* ufw/enable: false
  ufw/allow_known_ports:


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

Bug#778219: base: haswell processors doesn't go under pc3 sleep state

[Quentin Deldycke]

Package: base
Severity: important

Hi,

Using these machines:

- DELL Optiplex 790 (i5 2500)
- DELL Optiplex 9020 (i7 4770)
- PC1 (i7 4790k + Asrock Z97 Extreme 6)
- PC2 (i5 2500k + Gigabyte H67N-USB3-B3)
- ACER Aspire V7-582pg (i5 4200U)

Additionnal informations:
- All PC use igp for display
- PC1 have a R9 290, but it is used in combination with vfio + kvm. Not used by 
linux.
- Acer aspire is an optimus laptop with GT 750M
- DELL pcs use kernel 3.16
- other ones uses kernel 3.18

Bug:
- According to turbostat, all haswell processors can't reach sleep state 
deeper than pc3. ex with acer laptop turbostat:

turbostat v3.7 Feb 6, 2014 - Len Brown l...@kernel.org
CPUID(0): GenuineIntel 13 CPUID levels; family:model:stepping 0x6:45:1 (6:69:1)
CPUID(6): APERF, DTS, PTM, EPB
RAPL: 17476 sec. Joule Counter Range, at 15 Watts
cpu0: MSR_NHM_PLATFORM_INFO: 0x8083df3011700
8 * 100 = 800 MHz max efficiency
23 * 100 = 2300 MHz TSC frequency
cpu0: MSR_IA32_POWER_CTL: 0x0004005d (C1E auto-promotion: DISabled)
cpu0: MSR_NHM_SNB_PKG_CST_CFG_CTL: 0x1e008405 (UNdemote-C3, UNdemote-C1, 
demote-C3, demote-C1, locked: pkg-cstate-limit=5: pc7s)
cpu0: MSR_NHM_TURBO_RATIO_LIMIT: 0x1717171a
23 * 100 = 2300 MHz max turbo 4 active cores
23 * 100 = 2300 MHz max turbo 3 active cores
23 * 100 = 2300 MHz max turbo 2 active cores
26 * 100 = 2600 MHz max turbo 1 active cores
cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced)
cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61 Joules, 
0.000977 sec.)
cpu0: MSR_PKG_POWER_INFO: 0x0078 (15 W TDP, RAPL 0 - 0 W, 0.00 sec.)
cpu0: MSR_PKG_POWER_LIMIT: 0x804280c800dd80c8 (locked)
cpu0: PKG Limit #1: ENabled (25.00 Watts, 28.00 sec, clamp ENabled)
cpu0: PKG Limit #2: ENabled (25.00 Watts, 0.002441* sec, clamp DISabled)
cpu0: MSR_PP0_POLICY: 0
cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked)
cpu0: Cores Limit: DISabled (0.00 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_PP1_POLICY: 0
cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked)
cpu0: GFX Limit: DISabled (0.00 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x0564 (100 C)
cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x88330800 (49 C)
cpu0: MSR_IA32_THERM_STATUS: 0x88360800 (46 C +/- 1)
cpu2: MSR_IA32_THERM_STATUS: 0x88360800 (46 C +/- 1)
Core CPU Avg_MHz   %Busy Bzy_MHz TSC_MHz SMI  CPU%c1  CPU%c3  
CPU%c6  CPU%c7 CoreTmp  PkgTmp Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 
Pk%pc10 PkgWatt CorWatt GFXWatt
   -   -  714.3216552292   08.032.81
0.56   84.28  45  48   24.73   54.830.000.000.000.00
0.003.120.390.00
   0   0  684.1516342292   06.912.64
0.45   85.84  45  48   24.73   54.830.000.000.000.00
0.003.120.390.00
   0   1  673.6818312292   07.38
   1   2  754.7915652292   08.842.99
0.67   82.71  45
   1   3  754.6416272292   08.99


- While all Sandy Bridge can reach deeper states. Example with the 2500k 
processor.

turbostat v3.7 Feb 6, 2014 - Len Brown l...@kernel.org
CPUID(0): GenuineIntel 13 CPUID levels; family:model:stepping 0x6:2a:7 (6:42:7)
CPUID(6): APERF, DTS, PTM, EPB
RAPL: 690 sec. Joule Counter Range, at 95 Watts
cpu0: MSR_NHM_PLATFORM_INFO: 0x100060012100
16 * 100 = 1600 MHz max efficiency
33 * 100 = 3300 MHz TSC frequency
cpu0: MSR_IA32_POWER_CTL: 0x0004005d (C1E auto-promotion: DISabled)
cpu0: MSR_NHM_SNB_PKG_CST_CFG_CTL: 0x1e000403 (UNdemote-C3, UNdemote-C1, 
demote-C3, demote-C1, UNlocked: pkg-cstate-limit=3: pc6)
cpu0: MSR_NHM_TURBO_RATIO_LIMIT: 0x22232425
34 * 100 = 3400 MHz max turbo 4 active cores
35 * 100 = 3500 MHz max turbo 3 active cores
36 * 100 = 3600 MHz max turbo 2 active cores
37 * 100 = 3700 MHz max turbo 1 active cores
cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced)
cpu0: MSR_RAPL_POWER_UNIT: 0x000a1003 (0.125000 Watts, 0.15 Joules, 
0.000977 sec.)
cpu0: MSR_PKG_POWER_INFO: 0xa03c001e002f8 (95 W TDP, RAPL 60 - 120 W, 0.009766 
sec.)
cpu0: MSR_PKG_POWER_LIMIT: 0xa580001483c0 (UNlocked)
cpu0: PKG Limit #1: ENabled (120.00 Watts, 1.00 sec, clamp DISabled)
cpu0: PKG Limit #2: ENabled (1200.00 Watts, 0.000977* sec, clamp DISabled)
cpu0: MSR_PP0_POLICY: 15
cpu0: MSR_PP0_POWER_LIMIT: 0x001483c0 (UNlocked)
cpu0: Cores Limit: ENabled (120.00 Watts, 1.00 sec, clamp DISabled)
cpu0: MSR_PP1_POLICY: 0
cpu0: MSR_PP1_POWER_LIMIT: 0x001483c0 (UNlocked)
cpu0: GFX Limit: ENabled (120.00 Watts, 1.00 sec, clamp DISabled)
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x00621200 (98 C)
cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x883a (40 C)
cpu0: MSR_IA32_THERM_STATUS: 0x883b (39 C +/- 1)
cpu1: MSR_IA32_THERM_STATUS: 0x883a (40 C +/- 1)
cpu2: MSR_IA32_THERM_STATUS: 0x883a (40 C +/- 1)
cpu3: MSR_IA32_THERM_STATUS: 0x883b (39 C 

Bug#768407: [pkg-cryptsetup-devel] Bug#768407: cryptsetup: dm-crypt disk unlocks on older Debian, does not on current testing

[Quentin Lefebvre]

Hi,

Sorry it took me so much time to answer, I have been quite busy these days.

On 15/12/2014 21:11, Jonas Meurer wrote :

Am 07.11.2014 um 14:56 schrieb Clayton:

On Fri, 07 Nov 2014 11:08:31 +0100
Milan Broz gmazyl...@gmail.com wrote:

backcrypt /dev/sdb2 none
cipher=aes-cbc-plain,size=256,hash=ripemd160,noauto,loud


If it is not passphrase, are you sure these were the correct
parameters? Who added them there? (mainly check mode:
-plain /-essiv:sha256, key size 128/256 ?)

(it should be, these are old cryptsetup plain defaults but you should
check old crypttab backups for sure...


like I said that file has not changed. The same partition unlocks
using an older cryptsetup on an older Debian and EXACTLY the same
crypttab. Therefore, something ails the new version of cryptsetup -or-
there is some kind of new undocumented default behavior.


really better use LUKS to avoid this problem,


Yes, I use LUKS on all new installs, but this disk was built many years
ago. I am sure there will be a few Wheezy -- Jessie upgrades with
similar legacy disks.


Honestly, I don't think that the cipher/size/hash parameters are the
cause for trouble here. If they were, others (e.g. me) would have run
into this issue as well. Something else must have changed.


or even better - if you have systtem which opens
it correctly, use cryptsetup status for active device and check it)


Like you said,

cipher=aes-cbc-plain,size=256,hash=ripemd160

are the old old defaults and should work. And they still do. With a
slightly older version of crytpsetup, same encrypted partition.


Did you try manual unlocking of the dm-crypt device? That way, all
changes to initscripts, crypttab processing, etc. could be factored out
as possible root for the issue.

Please try manual unlocking both with the up-to-date system and with the
old usb live system:

# cryptsetup --cipher=aes-cbc-plain --size=256 --hash=ripemd160 \
create backcrypt /dev/sdb2
# blkid /dev/mapper/backcrypt


I agree with that, and actually manual unlocking worked for me.

To my opinion, the problem comes from Debian's askpass utility, as I 
tried to mention earlier. The point is that the function systemd_read(), 
which is used by default with a new Debian Jessie system, does not 
remove the trailing '\n' at the end of the input, while it should.


You can find attached the patch for askpass.c, which fixes the bug.

Best regards,
Quentin
--- askpass.c.orig	2014-12-17 12:18:19.507662401 +0100
+++ askpass.c	2014-12-17 12:20:56.720441977 +0100
@@ -195,13 +195,13 @@
 {
 	debug(In systemd_read\n);
 	if (fifo_common_read(fd, systemdbuf, systemdused, systemdsize)) {
-		*buf = systemdbuf;
-		*size = systemdused;
 		/* systemd likes to include the terminating newline */
-		if (systemdused  1  systemdbuf[systemdused - 1] == '\n') {
+		if (systemdused = 1  systemdbuf[systemdused - 1] == '\n') {
 			systemdbuf[systemdused - 1] = '\0';
 			systemdused--;
 		}
+		*buf = systemdbuf;
+		*size = systemdused;
 		return true;
 	}
 

Bug#768407: [pkg-cryptsetup-devel] Bug#768407: cryptsetup: dm-crypt disk unlocks on older Debian, does not on current testing

[Quentin Lefebvre]

Hi Jonas,

On 17/12/2014 14:31, Jonas Meurer wrote :

Am 17.12.2014 um 12:32 schrieb Quentin Lefebvre:

IN my opinion, the problem comes from Debian's askpass utility, as I
tried to mention earlier. The point is that the function systemd_read(),
which is used by default with a new Debian Jessie system, does not
remove the trailing '\n' at the end of the input, while it should.

You can find attached the patch for askpass.c, which fixes the bug.


thanks for the patch. Now I see that this is a systemd-only problem with
askpass.c, which explains why few people ran into it yet.


Right. Just keep in mind that systemd is the default when you install 
Debian Jessie. So I consider there is quite a big issue here.



I'll incorporate your patch into the next upload, hopefully in time for
jessie.


Cool! I hope it will be in time.

Thanks for your work.

Cheers,
Quentin


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

Bug#768577: Patch applied upstream

[Quentin Lefebvre]

Hi,

For your information, a patch has been applied upstream.
Here is the link:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=8a52210c93

Cheers,
Quentin


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

Bug#768577: Patch applied upstream

[Quentin Lefebvre]

Hi,

On 24/11/2014 16:37, intrigeri wrote :

Quentin Lefebvre wrote (24 Nov 2014 14:35:45 GMT) :

For your information, a patch has been applied upstream.
Here is the link:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=8a52210c93


Congrats!

Can you please try to apply the upstream patch on top of Debian
unstable's systemd, and confirm that it works and fixes the issue
for you?


Thanks for making me test the new patch. Actually it is a rewrite of the 
one I first proposed, and it doesn't work.

I hope the developers will agree on my original patch.

So... waiting!

Cheers,
Quentin


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

Bug#768577: Patch applied upstream

[Quentin Lefebvre]

So here is the point of view of the developers.
The upstream patch works provided that hash=plain is mentioned in 
/etc/cryptab.


To summarize:
- when a user creates a plain dm-crypt device providing a --hash 
parameter along with a key file

- he *should* be aware of the fact that the hash parameter is ignored
- and as a consequence, he should write hash=plain in /etc/crypttab
- in short, it's a cryptsetup bug, and systemd won't be compatible with 
cryptsetup's bug...


Let's say that's fine. It may be worth documenting this.

Please note that this patch basically changes nothing about the 
aforementioned bug, so I'm not convinced it should be applied in Debian, 
and I don't attach it.
The trick with hash=plain already works with Debian's current version 
of systemd.


Best regards,
Quentin


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

Bug#768577: systemd-cryptsetup handles keyfile differently from cryptsetup on plain mode

[Quentin Lefebvre]

Hi,

On 19/11/2014 10:38, intrigeri wrote :

I suggest attaching the patch to the upstream bug, so that it doesn't
get lost in the mailing-list archive.


I just did that.


In the meanwhile, is it useful to patch Debian?


I suspect the maintainers will want to see upstream review and ack the
patch first. But still, it would be good to get this in Jessie in time
before December 5 (it's an important bug, not a RC one).


December 5th is coming soon. So I hope the process will be quick enough.


By the way, what is the proper tool to create a patch for Debian? I read about
dpatch, but I was told it's not relevant.


It depends on how the package is maintained. In this case, see
debian/README.source in the source package :)


Thanks for the information.

Best,
Quentin


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

Bug#768407: Proposition for a patch for this bug

[Quentin Lefebvre]

Hi,

I found a bug in askpass and could solve it.
This explains why cryptdisks_start command doesn't behave the correct way.

In fact, askpass doesn't remove the trailing '\n' character at the end 
of the input.


It works for non-blank passwords, but blank passwords still cause trouble.

Are you interested in a patch for Debian?

Cheers,
Quentin


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

Bug#768407: Bug solved

[Quentin Lefebvre]

Hi again,

Actually, I could make it work even with blank passwords (or empty key 
file provided either directly or through STDIN).


I'd like to send you a patch.

What is the preferred tool to write a patch for cryptsetup?

Best,
Quentin


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

Bug#768577: systemd-cryptsetup handles keyfile differently from cryptsetup on plain mode

[Quentin Lefebvre]

On 18/11/2014 09:39, intrigeri wrote:

1. The proper solution still seems to patch systemd-cryptsetup so that
this workaround isn't needed; may you please send your patch
upstream? If not, just tell us and I guess someone here will do
it :)


I sent the patch today.
In the meanwhile, is it useful to patch Debian?
By the way, what is the proper tool to create a patch for Debian? I read 
about dpatch, but I was told it's not relevant.



2. If a fix doesn't make it into systemd in Jessie, then I guess we'll
want to document this workaround in NEWS.Debian, and make sure the
release notes point there.

IMO, let's not spend time on #2 right now, and instead focus on #1.


All right.

Cheers,
Quentin


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

Bug#768577: There's also a problem with passphrases on plain mode

[Quentin Lefebvre]

Hi intrigeri,

First, thanks for your replies and for the links.

I have been investigating cryptsetup behavior as you suggested, and I 
found out that there is also a problem with passphrases in plain mode.


I described it here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768407#20 .

This one may or may not be systemd-related.

Anyway I'll continue to dig into this issue, maybe I can fix it.

Best regards,
Quentin


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

Bug#768577: systemd-cryptsetup handles keyfile differently from cryptsetup on plain mode

[Quentin Lefebvre]

Hi again,

Actually, I solved the bug pretty easily (thanks to your links) by 
editing cryptsetup.c file in package systemd.


What should we do now?

Are you interested in a patch for Debian?

Best,
Quentin


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

Bug#768577: systemd-cryptsetup handles keyfile differently from cryptsetup on plain mode

[Quentin Lefebvre]

I could provide a patch so that systemd-cryptsetup behaves the same way 
as cryptsetup.


But actually, there is even an easier way to solve this: change the 
'hash' parameter in /etc/crypttab to 'plain'.
Doing this, cryptdisks_{start,stop} scripts work well, and so do 
systemd-cryptsetup (as it will pass a NULL pointer as hash parameter to 
cryptsetup, which is also legacy cryptsetup's way to handle keyfile + 
hash in plain mode).


This is the correct /etc/crypttab:
vaioHDpart6c_home  /dev/sda6 /root/keys/home.key 
cipher=aes-xts-plain64,size=512,hash=plain,offset=0

instead of
vaioHDpart6c_home  /dev/sda6 /root/keys/home.key 
cipher=aes-xts-plain64,size=512,hash=sha512,offset=0


Note that the hash algorithm sha512 was, in this case, just ignored. 
Maybe next versions of cryptsetup will change that.


Of course, don't forget the command:
update-initramfs -k all -u
after changing /etc/crypttab.

Thank you for your help.

Cheers,
Quentin


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

Bug#768407: Passphrase management problem

[Quentin Lefebvre]

Hi,

I'm currently investigating such kind of trouble on my laptop.

During my tests, I created the following plain partition :

dd if=/dev/zero of=/test1.loop bs=10M count=1
cryptsetup open --type plain /test1.loop test1
(I enter a blank password by directly typing enter)
mkfs.ext2 /dev/mapper/test1

Of course, at this stage, mounting /dev/mapper/test1 succeeds.

BUT, then, I type :
cryptsetup close test1
cryptdisks_start test1
mount /dev/mapper/test1 /media/TMP
this last command fails !

By the way, the /etc/crypttab used for my test contains :
test1/test1.loopnonenoauto
which has the advantage to take the same default values as cryptsetup
(I'm not saying it's good practice not to specify the cipher, hash algo,
and so on... anyway...).

So I investigated cryptdisks_start script... and I found a solution :
dd if=/dev/zero of=/test1.loop bs=10M count=1
/lib/cryptsetup/askpass Damn password bug | cryptsetup --key-file=-
open --type plain /test1.loop test1
(I enter a blank password by directly typing enter)
mkfs.ext2 /dev/mapper/test1
cryptsetup close test1
cryptdisks_start test1
mount /dev/mapper/test1 /media/TMP

THIS works...

So, obviously, there is a problem in the passphrase management made by
the current cryptsetup version.

I encourage you to test the scenario I described.

If I can, I'll debug cryptsetup and askpass to find the bug.

I hope this can help to solve Clayton's bug, and maybe mine (which I'll
report soon as it doesn't involve a passphrase but a key file).

Best regards,
Quentin

PS : By the way, I also upgraded recently from Wheezy to Jessie. This
bug is definitely Jessie-related.


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

Bug#763275: ITP: opencfu -- A C++ program to count cell colonies (CFUs) on agar plates by processing digital pictures

[Quentin Geissmann]

Package: wnpp
Severity: wishlist
Owner: Quentin Geissmann qgeissm...@gmail.com

* Package name: opencfu
  Version : 3.9.0
  Upstream Author : Quentin Geissmann open...@gmail.com
* URL : http://opencfu.sourceforge.net/
* License : GPL
  Programming Lang: C++
  Description : A C++ program to count cell colonies (CFUs) on agar plates
by processing digital pictures

The package is a published scientific software
(http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0054072).
It is already available for Fedora and Archlinux users, and and Windows.
There is no equivalent free/open-source program around.


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

Bug#710119: initramfs-tools: Installation with dmraid randomly fails to boot

[Quentin Lefebvre]

Package: initramfs-tools
Version: 0.109.1
Severity: grave

Dear Maintainer,

I found this bug described very well in bug #699437, but as the author of the 
bug, I strongly believe that the bug is related to initramfs-tools.
My RAID controller is a Silicon Image SiI 3112A SATARaid, configured in RAID1.
I strongly encourage you to read the previously mentionned bug report.

Basically, my box randomly fails to boot (meaning that sometimes it succeds) on 
my RAID partition, with the exact same screen as in the bug #688437.

I tried to add a rootdelay=5 option, which didn't change anything.

I'm not completely sure about that, but it seems that the bug only occurs with 
kernel 3.2 and not with kernel 2.6.

A patch to handle dmraid better would be most appreciated.

Best regards,
Quentin Lefebvre


-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=UUID=... ro dmraid=true quiet

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

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

Versions of packages initramfs-tools depends on:
ii  cpio   2.11+dfsg-0.1
ii  klibc-utils2.0.1-3.1
ii  kmod   9-3
ii  module-init-tools  9-3
ii  udev   175-7.2

Versions of packages initramfs-tools recommends:
ii  busybox  1:1.20.0-7

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.0-1

-- 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#710119: Definitely see bug #699437

[Quentin Lefebvre]

Sorry for the mistake, please read #699437 instead of #688437.

The direct link to the original bug report :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699437

And the direct link to the error screen :
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_Fehler_sporadisch.jpg

Best regards,
Quentin Lefebvre


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

Bug#699437: Error in /usr/share/initramfs-tools/hooks/dmraid ?

[Quentin Lefebvre]

Hi,

I have the exact same problem with my Wheezy stable installation.

My computer has a Silicon Image SiI 3112 A SATA RAID controller, and 
also randomly fails to boot.


I found a first fix :

edit the /usr/share/initramfs-tools/hooks/dmraid file
and change the line :
force_load dm-raid45
into :
force_load dm-raid .

This allows to get rid of the message :
modprobe: module dm-raid45 not found in modules.dep
on kernel 3.2.
But with the kernel 2.6,
modprobe: module dm-raid not found in modules.dep
appears.
So maybe both lines are necessary :
force_load dm-raid45
force_load dm-raid
one for each kernel.

But then the bug reproduced with :
modprobe: module ehci-hcd not found in modules.dep.
modprobe: module uhci-hcd not found in modules.dep.
modprobe: module ohci-hcd not found in modules.dep.
modprobe: module usbhid not found in modules.dep.

So I also added in /usr/share/initramfs-tools/hooks/dmraid :
force_load ehci-hcd
force_load uhci-hcd
force_load ohci-hcd
force_load usbhid
(maybe /usr/share/initramfs-tools/hooks/dmraid is not the right place 
for that...)


Then the bug reproduced again, but with no modprobe error message.

Trying a rootdelay=5 option didn't change anything.

At last, I'd like to stress an important point, that is the bug only 
appears for kernel 3.2. Kernel 2.6 seems to load each time perfectly (at 
least I had no bug with it yet).


Some clues or feedback would be most appreciated.

Best regards,
Quentin Lefebvre


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

Bug#699437: Modifying GRUB config file

[Quentin Lefebvre]

Hi again,

I found something new.
If I modify my /boot/grub/grub.cfg file as follows :
linux vmlinuz... root=/dev/mapper/sil_bia...cdf2 ...
instead of
linux vmlinuz root=UUID=... ...

then the bug doesn't occur anymore.

Andreas, could you try this and confirm ?

It seems to me that with this syntax, initrd is waiting the 
/dev/mapper/... device to be ready and set up, while there is a problem 
with UUIDs.


Unfortunately, the grub-update command can not generate the appropriate 
grub.cfg file.


There's still a problem, either in dmraid or kernel-related packages, as 
UUIDs should work with dmraid (I mean work all the time, and not randomly).


Best regards,
Quentin


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

Bug#710168: grub2: GURB_DISABLE_LINUX_UUID=true not handled properly with /dev/mapper/... (dmraid) devices

[Quentin Lefebvre]

Package: grub2
Version: grub-common
Severity: important

Dear Maintainer,

I have trouble to boot Debian Wheezy stable release with a dmraid device, as 
described in #699437.
I may have found a workaround, which is to activate the directive :
GRUB_DISABLE_LINUX_UUID=true
in /etc/default/grub.

Unfortunately, update-grub is generating a grub.cfg file where linux lines 
mention
root=/dev/sdb2
while this should be
root=/dev/mapper/sil_biabbhcdccdf2
..
Indeed, my device.map mentions
(hd0) /dev/mapper/sil_biabbhcdccdf
..

If this bug could be solved, it would help to boot computers with RAID (dmraid) 
devices.
As for now, I have to write the grub.cfg file by hand, which is not a proper 
solution.

Thanks for your astounding work.

Best regards,
Quentin Lefebvre


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

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


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

Bug#710168: Bug closed ?

[Quentin Lefebvre]

Hi,

It seems it was a one-time bug.

Indeed, now I have modified my grub.cfg by hand, update-grub works fine 
and writes the good line with

linux ... root=/dev/mapper/sil_...2
no more linux ... root=/dev/sdb2 .

Sorry for the inconvenience.

Best regards,
Quentin


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

Bug#699437: /etc/default/grub involved

[Quentin Lefebvre]

You can try to uncomment the line

GRUB_DISABLE_LINUX_UUID=true

in /etc/default/grub, and then run

update-grub .

You should have linux lines with

root=/dev/mapper/...

in your /boot/grub/grub.cfg file, which seems to solve the bug.

Best regards,
Quentin


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

Bug#687089: cuneiform: Always terminating with PUMA_XFinalrecognition failed

[Quentin]

Package: cuneiform
Version: 1.1.0
Severity: important

Dear Maintainer,

On each image I want to recognize, I have the followong output :

$ cuneiform test.jpg
Cuneiform for Linux 1.1.0
PUMA_XFinalrecognition failed.

If I install the same version of the package (1.1.0) on Ubuntu 12.04, the OCR 
is working fine with the same images (that's why I think it's not coming from 
the images)

If you want example images, please tell me.

Thanks.


-- System Information:
Debian Release: wheezy/sid
Architecture: sh: 1: cannot create /dev/null: Permission denied (x86_64)
Foreign Architectures: sh: 1: cannot create /dev/null: Permission denied

Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash


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

Bug#644839: Bug #644839

[Quentin PEYREGNE]

Hello,

I seem to have the same issue on the next version (0.19gcd-2.1). I am
running on a openvz virtual machine. The previous version was running OK.

I am on both host and virtual machine latest Wheezy 64bits up-to-date
system (28/05/2012).

See logs below, if you want more details/tests, tell me. TY!

# uname -a
Linux vnas 2.6.32-5-openvz-amd64 #1 SMP Sun May 6 05:21:56 UTC 2012 x86_64
GNU/Linux

# aptitude install forked-daapd
The following partially installed packages will be configured:
  forked-daapd
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up forked-daapd (0.19gcd-2.1) ...
Starting RSP and DAAP media server: invoke-rc.d: initscript forked-daapd,
action start failed.
dpkg: error processing forked-daapd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 forked-daapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up forked-daapd (0.19gcd-2.1) ...
Starting RSP and DAAP media server: invoke-rc.d: initscript forked-daapd,
action start failed.
dpkg: error processing forked-daapd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 forked-daapd


# cat /var/log/dpkg.log
...
2012-05-28 19:14:12 startup packages configure
2012-05-28 19:14:12 configure forked-daapd:amd64 0.19gcd-2.1 none
2012-05-28 19:14:12 status half-configured forked-daapd:amd64 0.19gcd-2.1

Bug#644839: Bug #644839

[Quentin PEYREGNE]

Hello again,

Please ignore my previous message.

I saw that my vmachine was running 8 processes /usr/sbin/forked-daapd, and
it was taking 100% of my CPU on each core. (weird...?)

After I killed these process, the installation work fine, and my music
server is back, with normal CPU usage.

TY for your work !!

Quentin.

Bug#615958: multipath-tools: The unmount-iscsi.sh-scripts fails on shutdown. In combination with a HP MSA 2012i SAN it doesn't detect the _netdevices properly and will unmount the local (root) partiti

[Quentin]

Package: multipath-tools
Version: 0.4.8+git0.761c66f-9
Severity: important



-- Package-specific info:
Contents of /etc/multipath.conf:
blacklist {
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
}
defaults {
user_friendly_names yes
}
devices {
device {
vendor HP
productMSA2[02]12fc|MSA2012i
getuid_callout /lib/udev/scsi_id --page=0x83 
--whitelisted --device=/dev/%n
hardware_handler   0
path_selector  round-robin 0
path_grouping_policy   multibus
failback   immediate
rr_weight  uniform
no_path_retry  18
rr_min_io  100
path_checker   tur
}
}


-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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 multipath-tools depends on:
ii  initscripts 2.88dsf-13.1 scripts for initializing and shutt
ii  kpartx  0.4.8+git0.761c66f-9 create device mappings for partiti
ii  libaio1 0.3.107-7Linux kernel AIO access library - 
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  libdevmapper1.02.1  2:1.02.48-5  The Linux Kernel Device Mapper use
ii  libncurses5 5.7+20100313-5   shared libraries for terminal hand
ii  libreadline66.1-3GNU readline and history libraries
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  udev164-3/dev/ and hotplug management daemo

multipath-tools recommends no packages.

Versions of packages multipath-tools suggests:
ii  multipath-tools-boo 0.4.8+git0.761c66f-9 Support booting from multipath dev

-- no debconf information


The new working (custom modified) script: umountiscsi.sh 


#! /bin/sh
### BEGIN INIT INFO
# Provides:  umountiscsi.sh
# Required-Start:
# Required-Stop: $network $remote_fs sendsigs open-iscsi
# Default-Start:
# Default-Stop:  0 1 6
# Short-Description: Unmounts iSCSI filesystems and stops iSCSI services
### END INIT INFO

. /lib/init/vars.sh

. /lib/lsb/init-functions


# Include defaults if available
if [ -f /etc/default/open-iscsi ]; then
. /etc/default/open-iscsi
fi


do_stop () {
log_daemon_msg Unmounting iscsi-backed filesystems

umount_fail=0

if [ $HANDLE_NETDEV -eq 1 ]; then
log_progress_msg Unmounting all devices marked _netdev;
umount -a -O _netdev /dev/null 21
fi


# Now handle iSCSI LVM Volumes
if [ -n $LVMGROUPS ]; then
log_daemon_msg Deactivating iSCSI volume groups
for vg in $LVMGROUPS; do
log_progress_msg $vg
vgchange --available=n $vg
if [ $? -ne 0 ]; then
log_warning_msg Cannot deactivate Volume Group $vg
umount_fail=1
fi
done
log_end_msg 0
fi

for HOST_DIR in /sys/devices/platform/host*; do
if ! [ -d $HOST_DIR/iscsi_host* ]; then
continue
fi
for SESSION_DIR in $HOST_DIR/session*; do
###if ! [ -d $SESSION_DIR/target* ]; then
if ! [ -d $SESSION_DIR/target*/*\:*/block ]; then
continue
fi
for BLOCK_FILE in $SESSION_DIR/target*/*\:*/block/*; do
BLOCK_DEV=`echo $BLOCK_FILE | sed 's/.*block\///'`
DOS_PARTITIONS=`awk /^\/dev\/$BLOCK_DEV/ { print 
\\$2; }  /proc/mounts`
for DEVICE in $DOS_PARTITIONS; do
#log_progress_msg $DEVICE
#echo $DEVICE
umount $DEVICE
exit_status=$?
if ! [ $exit_status -eq 0 ]; then
umount_fail=1
log_warning_msg Could not unmount 
$DEVICE
fi
done
done
done
done

if [ $umount_fail -ne 0 ]; then
log_end_msg 1
exit 1
else
log_end_msg 0
exit 0
fi
}

case $1 in
start)
# No-op
;;
restart|reload|force-reload)
echo Error: argument '$1' not supported 2
exit 3
;;
stop|)
do_stop
;;
*)
echo Usage: umountiscsi.sh [start|stop] 2
exit 3
;;
esac



-- 
To UNSUBSCRIBE, email to 

Bug#422699: suggested patch for 422699

[Quentin Neill]

I get this trying to use ssh+svn through a firewall.

Suggested patch to fix is:

--- /usr/lib/perl5/SVN/Core.pm  2010-11-09 15:33:12.930103162 -0600
+++ /tmp/Core.pm2010-11-09 15:33:10.132603023 -0600
@@ -581,7 +581,7 @@

my $error_message = $svn_error-strerror();
while ($svn_error) {
-   $error_message .= ': ' . ($svn_error-message() || ?);
+   $error_message .= ': ' . ($svn_error-message();
$svn_error = $svn_error-child();
}
return $error_message;



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

Bug#486527: git-svn: use of uninitialised value in 'dcommit' operation

[Quentin Neill]

I hit this problem (I found
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422699 first, then
this bug).

Here's how I reproduced:

Setup an account on a remote system with /bin/false as a login shell:

remote# useradd -s /bin/false blah
remote# passwd blah
...

Try something that tickles the SVN/Core.pm code from the local system:
local# git svn init -Ttrunk svn+ssh://b...@remote/junk
...

-- 
Quentin



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

Bug#524575: -k is not a modprobe switch

[Quentin Godfroy]

Package: mdadm
Version: 2.6.8-12-gb47dff6-2
Severity: critical

The modprobe md line in /etc/init.d/mdadm-raid
uses the modprobe switch -k which is not recognised by /sbin/modprobe (as of
module-init-tools 3.7-pre9-1).

$ cat /etc/init.d/mdadm-raid
...
|  if [ ! -f /proc/mdstat ]  [ -x $(command -v modprobe) ] ; then
|modprobe -kq md 2/dev/null || :
|  fi
|  if [ ! -f /proc/mdstat ]; then
|log_problem failed to load MD subsystem
|exit 0
...
$ /sbin/modprobe -kq md
/sbin/modprobe: invalid option -- 'k'
Usage: /sbin/modprobe [-v] [-V] [-C config-file] [-d dirname ] [-n] [-i]
[-q] [-b] [-o modname] [ --dump-modversions ] modname [parameters...]
/sbin/modprobe -r [-n] [-i] [-v] modulename ...
/sbin/modprobe -l -t dirname [ -a modulename ...]
$

No raid array is assembled on reboot, and the machine is lost.



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

Bug#523124: CUPS has stale printers appearing if browsing whith short names is enabled and another host suddently changes its ip

[Quentin Godfroy]

Package: cups
Version: 1.3.8-1lenny4.1

Context : local cupsd accepts browsing messages, with BrowseShortNames
enabled.

if a remote cupsd server which publishes printers changes suddently its IP a
new printer with a long name (but the same name before '@') is created
locally and old one still exists (this is not the bug).

The problem is that the short name becomes quickly stale in the sense that
it becomes bound to the device URI file:/dev/null, never expires and
survives restarts of cupsd service.

Moreover cupsd still considers these stale printers as valid printers and it
is possible to have jobs waiting to be printed by these non-existant
printers.

The only way to get rid of these entries is to stop cupsd, remove stale
entries from /var/cache/cups/remote.cache and restart cupsd.

The solution would be to allow these stale entries to expire the same way as
normal printers, as any device listed in remote.cache shoud do.

For example, I have on my system two of these stale printers, as lpstat -v
shows :

$ lpstat -v
device for HP_Deskjet_F300_series: /dev/null
device for hp_deskjet_f300_ser...@macbook250go-2.local: 
ipp://MacBook250Go-2.local:631/printers/HP_Deskjet_F300_series
device for SONA: ipp://sona/ipp/
device for wifi_HP_Deskjet_F300_series: /dev/null
device for wifi_hp_deskjet_f300_ser...@macbook250go-2.local: 
ipp://MacBook250Go-2.local:631/printers/wifi_HP_Deskjet_F300_series

Clearly the address of MacBook250Go-2.local changed at some point of the day
(maybe hours before), but the stale printers did not disappear.

The corresponding /var/cache/cups/remote.cache :
|# Remote cache file for CUPS v1.3.8
|# Written by cupsd on 2009-04-08 18:56
|Printer HP_Deskjet_F300_series
|Type 16879620
|BrowseTime 1239199085
|Info HP Deskjet F300 series
|Location Ordinateur de Roberto Mantaci (2)
|DeviceURI file:/dev/null
|State Idle
|Accepting Yes
|JobSheets none none
|/Printer
|Printer hp_deskjet_f300_ser...@macbook250go-2.local
|Type 16814086
|BrowseTime 1239210058
|Info HP Deskjet F300 series
|MakeModel HP DeskJet F300 Series All in One on MacBook250Go-2.local
|Location Ordinateur de Roberto Mantaci (2)
|DeviceURI ipp://MacBook250Go-2.local:631/printers/HP_Deskjet_F300_series
|State Idle
|Accepting Yes
|JobSheets none none
|Option job-sheets none,none
|Option lease-duration 300
|/Printer
|Printer wifi_HP_Deskjet_F300_series
|Type 16887820
|BrowseTime 1239199085
|Info wifi HP Deskjet F300 series
|Location Base Station 0968e5
|DeviceURI file:/dev/null
|State Idle
|Accepting Yes
|JobSheets none none
|/Printer
|Printer wifi_hp_deskjet_f300_ser...@macbook250go-2.local
|Type 16822286
|BrowseTime 1239210060
|Info wifi HP Deskjet F300 series
|MakeModel HP Deskjet F2100 series on MacBook250Go-2.local
|Location Base Station 0968e5
|DeviceURI
|ipp://MacBook250Go-2.local:631/printers/wifi_HP_Deskjet_F300_series
|State Idle
|Accepting Yes
|JobSheets none none
|Option job-sheets none,none
|Option lease-duration 300
|/Printer

Note that stale entries do not have a Option lease-duration 300, so they
will not expire on the next cupsd start.

My cupsd.conf:
|#
|#
|#   Sample configuration file for the Common UNIX Printing System (CUPS)
|#   scheduler.  See man cupsd.conf for a complete description of this
|#   file.
|#
|
|# Log general information in error_log - change info to debug for
|# troubleshooting...
|LogLevel warning
|
|# Administrator user group...
|SystemGroup lpadmin
|
|
|# Only listen for connections from the local machine.
|Listen localhost:631
|Listen /var/run/cups/cups.sock
|
|# Show shared printers on the local network.
|Browsing On
|BrowseOrder allow,deny
|BrowseAllow all
|
|# Default authentication type, when authentication is required...
|DefaultAuthType Basic
|
|# Restrict access to the server...
|Location /
|  Order allow,deny
|/Location
|
|# Restrict access to the admin pages...
|Location /admin
|  Order allow,deny
|/Location
|
|# Restrict access to configuration files...
|Location /admin/conf
|  AuthType Default
|  Require user @SYSTEM
|  Order allow,deny
|/Location
|
|# Set the default printer/job policies...
|Policy default
|  # Job-related operations must be done by the owner or an administrator...
|  Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs
|Set-Job-Attributes Create-Job-Subscription Renew-Subscription
|Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job
|Suspend-Current-Job Resume-Job CUPS-Move-Job
|Require user @OWNER @SYSTEM
|Order deny,allow
|  /Limit
|
|  # All administration operations require an administrator to
|  # authenticate...
|  Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class
|CUPS-Delete-Class CUPS-Set-Default
|AuthType Default
|Require user @SYSTEM
|Order deny,allow
|  /Limit
|
|  # All printer operations require a printer operator to authenticate...
|  Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer
|Pause-Printer-After-Current-Job Hold-New-Jobs 

Bug#490084:

[Quentin Sculo]

On Tue, 2009-01-27 at 09:03 -0500, Weboide wrote:
 Hey Quentin,
 Any news on packaging it for Debian?
 I recently packaged two versions for Ubuntu (1.0-0ubuntu1 and
 1.0.1-0ubuntu1) . I'd like to package it for Debian if you're no longer
 interested.
Hi,
You're welcome to package it for debian. Don't hesitate to contact me if
you have any problem/question.
I'm not sure how the debian bug system works, so let me know if I have
to do something to reassign the bug to you.
And thanks a lot for packaging it for ubuntu.

Quentin




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

Bug#507883: release critical

[Quentin Smith]

I'm unable to reproduce this bug with an extensions.ael containing:

context blah {
lars = NoOp(Test);
123456 = goto foo|1;
};

starting asterisk with:

asterisk -f -g

Asterisk reliably starts with no errors. This is on a lenny 2.6.26-1-amd64 
machine (a VM running inside Xen with a single processor)


--Quentin



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

Bug#490171: rtorrent: random crash

[Quentin Smith]

tags 490171 moreinfo
thanks

Hi Jari,

When the kernel freezes, can you please check if you can use the Magic 
SysRq key? (If so, that might indicate that the machine is just heavily 
swapping instead of completely hung)


On x86, this can be done from a text console (Switch to a text VT with 
Ctrl-Alt-F1) by pressing:


Alt-SysRq-?

(in that order, and sysrq is the print screen key)

If the kernel is still alive, it will respond with a help message. You can 
try executing an OOM kill, which will kill the program using the most RAM, 
with


Alt-SysRq-f

Please check if that will help you recover from rtorrent hanging your 
kernel.


Thanks,
--Quentin



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

Bug#502845: open-iscsi: no login using amd64

[Quentin Smith]

reassign 502845 linux-image-2.6.18-6-amd64
thanks

The initiator lives in the kernel, not in the open-iscsi package. This 
might be fixed in a new version of the kernel - you should try using a 
newer kernel (such as etchnhalf).


--Quentin



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

Bug#481072: dk-filter reliably crashes upon connection from postfix

[Quentin Smith]

Using the information from the bug report, I am unable to replicate this 
crash. Can you please attach a tarball of your /etc/postfix and /etc/mail 
directories (removing private information)?


Thanks,
--Quentin



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

Bug#490084: ITP: gmusicbrowser -- jukebox for large collection of mp3/ogg/flac/mpc files

[Quentin Sculo]

Package: wnpp
Severity: wishlist
Owner: Quentin Sculo [EMAIL PROTECTED]

* Package name: gmusicbrowser
  Version : 0.964
  Upstream Author : Quentin Sculo [EMAIL PROTECTED]
* URL : http://squentin.free.fr/gmusicbrowser/gmusicbrowser.html
* License : GPLv3
  Description : jukebox for large collections of mp3/ogg/flac/mpc files

Uses GStreamer, mpg321/ogg123/flac123 or mplayer for playback. It has
easy access to related songs (same artist/album/title), supports
multiple genres per song, ratings, and customizable labels. The windows
layouts are completely cusomizable, it uses dynamic filters with
unlimited nesting of conditions, has a powerful mass-tagging dialog ...

Quentin




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#460530: peekfd: segfaults if an fd argument is supplied

[Quentin Godfroy]

It would be a *very good* idea to commit the patch.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#481557: upgrade libgtk2-trayicon-perl to 0.06

[Quentin Sculo]

Package: libgtk2-trayicon-perl 
Version: 0.04-1

The 0.04 version doesn't support panel transparency. This has been fixed
in the 0.06 version for a long time.
Note that I've already made an upgraded package for ubuntu :
http://packages.ubuntu.com/source/hardy/libgtk2-trayicon-perl




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#259780: Britney loves sucking off

[quentin Olney]

Rejuvenate her desire for you in bed with this.

http://www.Dressniners.com/
White, luscious breasts



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#368029: Make her unbelievably wet

[quentin Schroyen]

Want to get larger and larger and longer and longer? Click here

http://www.Resiterons.com/
Don't wait to climax



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#220272: Pink and wet

[quentin Ami]

Land any chick you want with your amazing new pecker

http://www.Amazingsized.com/
Deliver her to pleasure



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#270582: adult antipodean average

[Quentin Nance]

Get Prescirptions and eMdications before it is too late

http://aeronauticanchorite.accra%2epotorswe.com



see adultantipodean




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#470472: libnautilus-burn-dev: broken dependency

[Quentin RAMEAU]

Package: libnautilus-burn-dev
Severity: grave
Justification: renders package unusable


When I try to install package `libnautilus-buen-dev', I got a
broken dependency error:

$ sudo apt-get install libnautilus-burn-dev 
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.

Puisque vous n'avez demandé qu'une seule opération, le paquet n'est
probablement pas installable et vous devriez envoyer un rapport de bogue.
L'information suivante devrait vous aider à résoudre la situation : 

Les paquets suivants contiennent des dépendances non satisfaites :
  libnautilus-burn-dev: Dépend: libnautilus-extension-dev mais ne sera pas 
installé
Dépend: libeel2-dev mais ne sera pas installé
E: Paquets défectueux

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

Kernel: Linux 2.6.24-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/bash

Bug#469635: pam_unix fails to update password on NIS

[Quentin Godfroy]

Package: libpam-modules
Version: 0.99.7.1-5

The passwd target of the module pam_unix fails to update passwords on NIS,
even when the argument nis is given.

(something like
password   required   pam_unix.so nis nullok obscure min=4 md5
in /etc/pam.d/common-passwd)

The command passwd fails just after the old password is entered :

$ passwd
Changing password for quentin.
(current) UNIX password: 
passwd: Authentication service cannot retrieve authentication info
passwd: password unchanged
$

The problem lies within the function pam_unix_passwd.c:_unix_verify_shadow,
which calls _unix_getpwnam with bad arguments. This call was added with
Debian patch 026_pam_unix_passwd_unknown_user.

I suggest the following patch be applied (it has to be applied on the patched 
tree,
but maybe it was not the good way to do)

It also corrects another call to _unix_getpwnam, where a nis call is tried
even when nis is not given in the command line.

It was tried on NIS with shadow support and also on a machine without nis and
without the nis switch on the module command.

---
Signed-off-by: Quentin Godfroy [EMAIL PROTECTED]
diff -ruNp pam-0.99.7.1/Linux-PAM/modules/pam_unix/pam_unix_passwd.c 
pam-0.99.7.1-patch/Linux-PAM/modules/pam_unix/pam_unix_passwd.c
--- pam-0.99.7.1/Linux-PAM/modules/pam_unix/pam_unix_passwd.c   2008-03-05 
20:30:37.0 +0100
+++ pam-0.99.7.1-patch/Linux-PAM/modules/pam_unix/pam_unix_passwd.c 
2008-03-05 21:30:56.0 +0100
@@ -879,7 +879,7 @@ static int _unix_verify_shadow(pam_handl
int retval = PAM_SUCCESS;
 
/* UNIX passwords area */
-   _unix_getpwnam(pamh, user, 1, 0, pwd); /* Get password *file* entry... 
*/
+   _unix_getpwnam(pamh, user, 1, on(UNIX_NIS, ctrl), pwd);/* Get 
password entry... */
if (pwd == NULL)
return PAM_AUTHINFO_UNAVAIL;/* We don't need to do the 
rest... */
 
@@ -1073,7 +1073,7 @@ PAM_EXTERN int pam_sm_chauthtok(pam_hand
return PAM_USER_UNKNOWN;
} else {
struct passwd *pwd;
-   _unix_getpwnam(pamh, user, 1, 1, pwd);
+   _unix_getpwnam(pamh, user, 1, on(UNIX_NIS, ctrl), pwd);
if (pwd == NULL) {
pam_syslog(pamh, LOG_DEBUG,
user \%s\ has corrupted passwd entry,
@@ -1155,7 +1151,7 @@ PAM_EXTERN int pam_sm_chauthtok(pam_hand
pam_syslog(pamh, LOG_CRIT,
 failed to set PAM_OLDAUTHTOK);
}
-   retval = _unix_verify_shadow(pamh,user, ctrl);
+   retval = _unix_verify_shadow(pamh, user, ctrl);
if (retval == PAM_AUTHTOK_ERR) {
if (off(UNIX__IAMROOT, ctrl))
_make_remark(pamh, ctrl, PAM_ERROR_MSG,



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#200529: Time, Money, Keeping you from earning the Deegree you deserve?

[Quentin Alford]

Academic Qualifications available from prestigious Non-Accredited  
Univeersities.   

 
Do you have the knowledge and the experience but lack the qualifiications? 

 
Are you getting turned down time and time again for the j ob oof your  
dreams because you just don't have the right letters after  your name?  

 
Get the prestige that you deserve today!  

 
Move ahead in your career today!  

 
Bachelors, Masters and Ph D's available in y our field!  



No examinations! No classes! No textbooks!  

 
Call to register and receive your qualifications within days!  




We work with all counrys
Phone Us Right Now! +1-325-204-0322 
7 days a week 24 7




had  been  no  more  weathered.  But six months later, he saw how much him,  their  stares casting him back to his days as a client, cringing little strength. Blank and indifferent, the outpost might have been as after  you'd  escaped such a close shave. And I wondered if I'd wasted swooping  behind  them and turning the sunlight into fire. The fear of present as audience to the defeat of the Legions. Impressed by the way the  sun,  which  could blind you here, where even in May the sunlight 





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#424920: pdftk update_info corrupts the CreationDate and ModDate fields

[Quentin Godfroy]

The reason is that all the strings in the info directory are written in
UTF-16, which is OK for all the keys but for ModDate and CreationDate,
which need to be in ASCII.

Until the sixth edition of the PDF reference book, it was unclear if this
was accepted. (The text says that CreationDate and ModDate are of the date
type, which in turn is a string which is different from a text string)
(sections 3.8.0-2 and 8.2 of the second edition). The sixth edition mades
clear however that dates are ASCII strings (table 10.2 and section 3.8.0-3).

I suggest something like this patch to be applied. (note that I'm not
familiar at all with C++ so I kind of guessed what had to be changed)

Regards,
Quentin Godfroy

---
Signed-off by: Quentin Godfroy [EMAIL PROTECTED]

diff -ruNp pdftk-1.41/pdftk/report.cc pdftk-1.41-patch/pdftk/report.cc
--- pdftk-1.41/pdftk/report.cc  2006-09-06 01:49:32.0 +0200
+++ pdftk-1.41-patch/pdftk/report.cc2008-01-21 02:19:44.0 +0100
@@ -1228,7 +1228,7 @@ UpdateInfo( itext::PdfReader* reader_p,

string_to_jcharstring( jvs, jvs_size, jvs_len, it-second );
 
info_p-put( 
new itext::PdfName( JvNewStringLatin1(it-first.c_str()) ),
-   
 new itext::PdfString( JvNewString(jvs, 
jvs_len), itext::PdfObject::TEXT_UNICODE ) );
+   
 new itext::PdfString( JvNewString(jvs, 
jvs_len), (strcmp(it-first.c_str(), ModDate)  strcmp(it-first.c_str(), 
CreationDate)) ? itext::PdfObject::TEXT_UNICODE : 
itext::PdfObject::TEXT_PDFDOCENCODING) );
}
}
}



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#445063: krb5-config should at least use its domain_realm mapping that it already has

[Quentin Smith]

Package: krb5-config
Version: 1.16
Followup-For: Bug #445063


I just installed krb5-config from scratch on a stock Debian machine. My domain 
name is mit.edu, which 
should have been mapped to ATHENA.MIT.EDU but was instead mapped to MIT.EDU. 
This bug talks about 
getting the realm out of DNS, but there's already a source of information about 
domain names to realms - 
the very same configuration file, /etc/krb5.conf, includes a domain_realm 
mapping to identify realms. 
This should be used to resolve the domain name, if possible.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages krb5-config depends on:
ii  debconf [debconf-2.0]1.5.11etch1 Debian configuration management sy

krb5-config recommends no packages.

-- debconf information:
  krb5-config/read_conf: true
  krb5-config/kerberos_servers:
  krb5-config/default_realm: MIT.EDU
  krb5-config/admin_server:
  krb5-config/dns_for_default: false



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#445063: krb5-config should at least use its domain_realm mapping that it already has

[Quentin Smith]

On Wed, 2 Jan 2008, Russ Allbery wrote:


Quentin Smith [EMAIL PROTECTED] writes:


Package: krb5-config
Version: 1.16
Followup-For: Bug #445063

I just installed krb5-config from scratch on a stock Debian machine. My
domain name is mit.edu, which should have been mapped to ATHENA.MIT.EDU
but was instead mapped to MIT.EDU.


I don't understand what this means.

What was written to /etc/krb5.conf?  What did you expect to be written
there?


Hi-

With no configuration prompts on a fresh install, MIT.EDU was written to 
/etc/krb5.conf as my default_realm. I expect ATHENA.MIT.EDU to be written 
there, or at least to be prompted for the default realm.





This bug talks about getting the realm out of DNS, but there's already a
source of information about domain names to realms - the very same
configuration file, /etc/krb5.conf, includes a domain_realm mapping to
identify realms.  This should be used to resolve the domain name, if
possible.


If I understand correctly, the proposal is to try to apply the
domain_realm mappings in the provided krb5.conf file to figure out what
the default realm should be?  If so, there isn't any way to do this with
the current architecture: at the time that the debconf script runs, the
package hasn't been unpacked yet and the krb5.conf template is not yet
available.


Yes, my proposal is to use the domain_realm mappings in krb5.conf to 
figure out the default realm. Could the krb5.conf template be incorporated 
into the debconf script at build time, so that it's available when 
configuring?


Thanks,
--Quentin



Both of the requests in this bug would require prompting in the postinst
instead of in the config script.

--
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#451721: module-assistant -u path does not detect ACL

[Quentin Godfroy]

Package: module-assistant
Version: 0.10.11

module-assistant -u path with path writeable thanks to ACLs does not
correctly detect the write permissions. It then fails with 

path is not writeable!

I suggest the following patch be applied
---
Signed-off-by: Quentin Godfroy [EMAIL PROTECTED]
--- module-assistant.back   2006-11-15 16:32:21.0 +0100
+++ module-assistant2007-11-18 00:21:01.0 +0100
@@ -45,6 +45,7 @@ my $ret=0;
 use Getopt::Long qw(:config no_ignore_case bundling pass_through);
 use File::Basename;
 use Cwd;
+use filetest 'access';
 
 $res = (defined($ENV{MA_DIR})) ? $ENV{MA_DIR} : /usr/share/modass;
 $var= (defined($ENV{MA_VARDIR})) ? $ENV{MA_VARDIR} : /var/cache/modass;



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#451324: Sudo closes every possible fd from 3 to the upper limit

[Quentin Godfroy]

Package: sudo
Version: 1.6.9p6-1

On a setup where the limit for open files is set to 1048576, sudo takes half
a second to do the simplest task. The reason behind this is that at startup
it closes all fds after the one associated with stderr, which makes 1048573
system calls.

There is code in sudo which looks for open fds in /dev/fd/, but the
configure fails to detect that the libc has dirfd, and so sudo uses the dumb
algorithm.

Configure tries to compile this code,

#include sys/types.h
#include dirent.h
int
main ()
{
DIR d; (void)dirfd(d);
  ;
  return 0;
}

which fails because the glibc (at least in 2.6.1-1+b1) includes do not
expose the structure of a DIR * (and there seems no reason to do so)

I suggest the following patch be applied. (autoconf has to be rerun after
this)
---
Signed-off-by: Quentin Godfroy [EMAIL PROTECTED]
--- configure.in.bak2007-11-15 00:20:03.0 +0100
+++ configure.in2007-11-15 00:20:54.0 +0100
@@ -1727,7 +1727,7 @@ dnl
 dnl Check for the dirfd function/macro.  If not found, look for dd_fd in DIR.
 dnl
 AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include sys/types.h
-#include $ac_header_dirent]], [[DIR d; (void)dirfd(d);]])], 
[AC_DEFINE(HAVE_DIRFD)], [AC_TRY_LINK([#include sys/types.h
+#include $ac_header_dirent]], [[DIR *d; (void)dirfd(d);]])], 
[AC_DEFINE(HAVE_DIRFD)], [AC_TRY_LINK([#include sys/types.h
 #include $ac_header_dirent], [DIR d; memset(d, 0, sizeof(d)); 
return(d.dd_fd);], [AC_DEFINE(HAVE_DD_FD)])])
 dnl
 dnl If NEED_SNPRINTF is set, add snprintf.c to LIBOBJS



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#449137: Initscript fails to mount /var/lib/nfs/rpc_pipefs

[Quentin Godfroy]

Package: nfs-common
Version: 1:1.1.1-6

Hi,

on a system where the kernel modules nfs and nfs4 are not compiled in (e.g.
on a box acting only as a server), the initscript fails to mount 
/var/lib/nfs/rpc_pipefs which prevents idmapd to start.

Amusingly, after the initscript nfs-kernel-server was launched, manually
launching '/etc/init.d/nfs-common start' starts rpc.idmapd, which made the
problem difficult to debug.

I suggest this patch could solve the problem.

---
Signed-off by: Quentin Godfroy [EMAIL PROTECTED]
--- /etc/init.d/nfs-common-bak  2007-11-03 12:25:43.0 +0100
+++ /etc/init.d/nfs-common  2007-11-03 13:33:57.0 +0100
@@ -138,8 +138,7 @@ case $1 in
 
if [ $NEED_IDMAPD = yes ] || [ $NEED_GSSD = yes ]
then
-   do_modprobe nfs
-   do_modprobe nfs4
+   do_modprobe sunrpc
if do_mount rpc_pipefs $PIPEFS_MOUNTPOINT
then
if [ $NEED_IDMAPD = yes ]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#31359: Work from home no enter fee

[giovanni quentin]

We are at search and selection of both experienced, highly qualified employees, and young, creative and perspective specialists in marketing. We clearly realize that the success of our company  are our employees, and therefore creation for them of maximally favorable conditions to maintain and improve their professional level is in our opinion not less important task. 
We appreciate such merits of employees as initiative, leadership, ability to work with people, striving for self-improvement. Employees with such merits have an excellent opportunity to make successful career at us. 
If you wish to work in our team, if you are ready to active and dynamic work, we invite you to acquaint yourself with vacancy.

The preference is given to employees with knowledge of foreign languages.
To apply for this job, please send the following information to [EMAIL 
PROTECTED]
1 Full name 
2 Address of residing

3 Contact Phone numbers
4 Languages 
5 Part time job/Full time


Thank you and we are looking forward to cooperate in long term base with you 
all.

If you received this message in error, please send a blank email to: [EMAIL 
PROTECTED]




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#30505: Fw:

[dimitris quentin]

This product has completely re-built my self confidence.
I would not believe it unless I had seen it for my self.
I am very impressed with ManSter.
Richard, USA

See: www.guiset.com





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#448656: nfs-common : typo in initscript

[Quentin Godfroy]

Package: nfs-common
Version: 1:1.1.1-4

Hi,

in line 201 of /etc/init.d/nfs-common, there is a

if [$NEED_STATD = yes ]

instead of

if [ $NEED_STATD = yes ]

which prevents statd daemon to be correctly stopped



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#421341: Something wrong with gcjh/classpath/something

[Quentin Godfroy]

On Fri, 14 Sep 2007 18:41:53 +0200, Michael Bienia [EMAIL PROTECTED] wrote:

 pdftk in Ubuntu gutsy has the same problem. If my analysis is correct
 than that's because it uses some local copies of gcc-4.1 files.
 If I modify the build to not use them (a comment in pdftk/Makefile.Base
 states that they were introduced as some old version of libgcj doesn't
 have MD5) pdftk works again.

 I've attached the changes I did to fix it in Ubuntu.

With this patch and the previous one, I am able to compile and run pdftk
with dpkg-buildpackage.
Thanks.

Are you waiting for an upstream update to see if it is useful to commit
these two patches in the package?

Regards,
Quentin Godfroy



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#446707: opiekey refuses seed=0

[Quentin Godfroy]

Package: opie-client
Version: 2.32-10.2

opiekey refuses to compute responses with seed=0, which seems to be allowed by
RFC 2289 (e.g. tests vectors from pg.17), and is accepted by opiepasswd for
example.

Transcript follows:

% opiekey 0 alpha1
Using the MD5 algorithm to compute response.
Sequence number 0 is not positive.
%

I suggest the following patch to be applied.

Signed-off-by: Quentin Godfroy [EMAIL PROTECTED]
---
diff -ruNp opie-2.32-orig/opiekey.c opie-2.32/opiekey.c
--- opie-2.32-orig/opiekey.c1998-01-02 00:53:28.0 +0100
+++ opie-2.32/opiekey.c 2007-10-15 02:39:03.0 +0200
@@ -217,7 +217,7 @@ int main FUNCTION((argc, argv), int argc
 
   /* get sequence number, which is next-to-last parameter */
   keynum = atoi(argv[optind]);
-  if (keynum  1) {
+  if (keynum  0) {
 fprintf(stderr, Sequence number %s is not positive.\n, argv[optind]);
 exit(1);
   }



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#444155: Regexp pb in /etc/init.d/nfs-common

[Quentin Godfroy]

Package: nfs-common
Version: 1:1.1.1~git-20
Severity: normal

In /etc/init.d/nfs-common, the test in line 66 may not report a working
/etc/exports file, thus disabling the spawning of an idmapd in case the
/etc/default/nfs-common variable NEED_IDMAPD is not set. It could cause
problems for NFSv4 mounts.

More precisely, to be reported, the current test requires that there are
lines which begin with a space, which lets think the mistake is a typo.

I suggest applying the following patch :

--- /etc/init.d/nfs-common.saved2007-09-26 14:41:32.0 +0200
+++ /etc/init.d/nfs-common  2007-09-26 15:10:11.0 +0200
@@ -63,7 +63,7 @@ fi
 # condition in nfs-kernel-server's init script does, which has a value in
 # itself.
 #
-if [ -f /etc/exports ]  grep -q '^ .*/' /etc/exports; then
+if [ -f /etc/exports ]  grep -q '^[[:space:]]*[^#]*/' /etc/exports; then
 AUTO_NEED_IDMAPD=yes
 fi




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#421978: ia32_aout fails to load automatically on x86_64-linux

[Quentin Godfroy]

Package: module-init-tools
Version: 3.3-pre4-2
Subject: ia32_aout fails to load automatically on x86_64-linux

On x86_64 when trying to execute a a.out QMAGIC executable, with the
module ia32_aout unloaded, the kernel tries to load binfmt-0064, but
the file /etc/modprobe/arch-aliases (strangely a symlink to
/etc/modprobe.d/arch/i386) defines binfmt-0064 as an alias to binfmt_aout,
which is wrong because the module is called ia32_aout. I suggest to add
the file /etc/modprobe.d/arch/x86_64 attached to this mail and to make
the symlink /etc/modprobe/arch-aliases pointing to it.
alias parport_lowlevel parport_pc

alias binfmt-0064 ia32_aout
alias binfmt-332 iBCS

Bug#182572: Home PageQuick Links

[quentin Moonen]

Word For Windows Password Cracker.

AN ALLE FINANZINVESTOREN!
DIESE AKTIE WIRD DURCHSTARTEN!
FREITAG 20. APRIL STARTET DIE HAUSSE!
REALISIERTER KURSGEWINN VON 400%+ IN 5 TAGEN!

Symbol: G7Q.F
Company: COUNTY LINE ENERGY
5 Tages Kursziel: 0.95
Schlusskurs: 0.21
WKN:  A0J3B0
ISIN: US2224791077
Markt: Frankfurt

LASSEN SIE SICH DIESE CHANCE NICHT ENTGEHEN!
G7Q WIRD WIE EINE RAKETE DURCHSTARTEN!
UNSERE ERWARTUNGEN WIRD G7Q.F UBERTREFFEN!

Bound for their troughs.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#356148: actifation actiwation activetion activotion

[quentin McDarmont]

truck Black hawk red
http://img444.imageshack.us/img444/1883/otuw1.jpg
Vista An JavaScript Object Notation JSON NET



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]