Bug#1011121: peding rebuild is taking quite long

Hi, Apparently there are lintian errors that prevent the rebuild to suceed... I would like to avoid applying patches by myself and rebuilding. -- eric _ Ce message et ses

Bug#788100: fixed

-- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou

Bug#942512: partitionmanager: 4.0.0-1 does not work at all : warning about missing plugin and later hangs forever

Package: partitionmanager Version: 4.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, 1) warning message about missing default plugin "" 2) then hangs forever in scanning devices here are trace from root console: partitionmanager   QStandardPaths:

Bug#907384: plasma-discover: needrestart breaks Plasma-discover upgrade mechanism

On 10/16/2018 05:28 PM, Matthias Klumpp wrote: Am Mo., 27. Aug. 2018 um 11:36 Uhr schrieb Eric Valette : Package: plasma-discover Version: 5.13.4-1 Severity: important For security reasons, many sceurity tools including lynis recommend to install needrestart package in order to automatically

Bug#834359: Fixed for good now

notfound 834359 5.8.4-1 -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses,

Bug#823330: closed by gustavo panizzo <g...@zumbi.com.ar> (Bug#823330: fixed in tsocks 1.8beta5-9.5)

On 10/28/2016 01:03 PM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the tsocks package: #823330: tsocks: The actual configure command disable host name resolution in tsocks.conf when it was

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

On 10/21/2016 11:43 AM, Eric Valette wrote: On 10/21/2016 11:40 AM, Konstantin Demin wrote: I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26

Bug#797999: We are now more than one year later and this critical bug is not fixed

On 10/10/2016 11:48 AM, Maximiliano Curia wrote: ¡Hola eric2.valette! First of all, the bug is not critical because it only affects a very specific setup for a particular video driver. A docked station using a nvidia driver is not that uncommon I guess... I suspect that the bug

Bug#797999: We are now more than one year later and this critical bug is not fixed

Just updated to kde 5.8, and lib 5.26.0 and it still does not correctly detect my external screen when lid is closed.I still need kdm! -- eric _ Ce message et ses pieces

Bug#815565: In addition it prefix each table index entries by the entry number

Which also looks terrible... --eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre

Bug#815559: konsole: Konsole fails to use default font when selected font in profile becomes unavailable

On 02/22/2016 03:11 PM, Maximiliano Curia wrote: Control: severity -1 normal Control: tag -1 + confirmed upstream Control: forwarded -1 + https://bugs.kde.org/show_bug.cgi?id=359669 ¡Hola Eric! El 2016-02-22 a las 13:45 +0100, Eric Valette escribió: Package: konsole Version: 4:15.12.1-1

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

On 01/22/2016 01:11 PM, VALETTE Eric OLNC/OLPS wrote: On 01/20/2016 03:07 PM, Ludovic Rousseau wrote: It does not look like the problem is the Broadcom reader. Can you generate a log as documented in

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

On 01/22/2016 03:06 PM, Ludovic Rousseau wrote: Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit : On 01/20/2016 03:07 PM, Ludovic Rousseau wrote: It does not look like the problem is the Broadcom reader. Can you generate a log as documented in

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

On 01/22/2016 03:52 PM, Ludovic Rousseau wrote: Le 22/01/2016 15:18, eric2.vale...@orange.com a écrit : On 01/22/2016 03:06 PM, Ludovic Rousseau wrote: Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit :

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

On 01/20/2016 01:31 PM, Ludovic Rousseau wrote: Le 20/01/2016 13:03, Eric Valette a écrit : Package: pcscd Version: 1.8.15-1 Severity: critical Justification: breaks unrelated software Twice in two days, I noticed my laptop fan was going carsy allthough I was only doing many mail activity.

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

On 01/20/2016 03:07 PM, Ludovic Rousseau wrote: Le 20/01/2016 14:02, eric2.vale...@orange.com a écrit : It does not look like the problem is the Broadcom reader. Can you generate a log as documented in https://pcsclite.alioth.debian.org/pcsclite.html#support ? Start the log and then connect

Bug#804669: libreoffice-kde (5.1): integration with dolphin is bugged

On 11/10/2015 02:33 PM, Rene Engelhard wrote: tag 804669 + moreinfo thanks This is the first time I did see this beahvior. Up to now, libreoffice 5.x was always correctly working with dolphin. -- eric

Bug#796957: sddm servive stop and then service starts make keyboard unresponsive => unable to login

On 09/14/2015 01:42 PM, Maximiliano Curia wrote: Control: reassign -1 sddm 0.11.0-3 Control: tag -1 + unreproducible moreinfo Control: severity -1 normal Hi, On 26/08/15 10:14, Eric Valette wrote: stopped/started sddm on a computer that was still

Bug#796956: Note that this is a docked laptop using external monitor

I now have half a dozen boxes that works correctly and this is the only one that is a docked laptop using an external monitor with internal LVDS display off. So far as I had multiple temporary breakage on various boxes due to partial/incompatible packages versions uploads, I did not consider

Bug#797999: sddm fails to start whereas kdm works correctly

On 09/07/2015 11:00 PM, Dominik George wrote: Control: tags -1 + moreinfo Hi Eric, On Fri, 4 Sep 2015 13:00:11 0200 Eric Valette wrote: If I do dpkg-reconfigure sddm, select it and reboot, I just get a black screen, with X running, no cursor, no mouse nothing

Bug#797999: sddm fails to start whereas kdm works correctly

On 09/08/2015 12:43 PM, Dominik George wrote: Hi Eric, Unfortunately no. This is likely to be due to docking as I now have a half dozen boxes that work with sddm the only one that fails is a docked laptop. And this laptop, does it by any chance use an Intel graphics chip? No. It uses nvidia

Bug#797999: Tested with the new 0.12.0 => still fails

Same black screen sddm process runs, X started but no greeter only black screen with no mouse, nothing and an empty sddm.log and no errors in .xsession.errors --eric

Bug#796956: Bug is still présent with 0.12.0

On 09/07/2015 02:43 PM, Matthias Klumpp wrote: 2015-09-07 14:30 GMT+02:00 : Konsole output ls -ld /etc/sddm/Xsession -rwxr-xr-x 1 root root 1426 Sep 3 17:24 /etc/sddm/Xsession Konsole output ls -l /var/lib/sddm/ ls: cannot open directory /var/lib/sddm/: Permission

Bug#796956: sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze : works

But I see no sddm-greeter process when I do a PS after login on console via CTRL-ALT-F1 -- eric _ Ce message et ses pieces jointes peuvent contenir des informations

Bug#796956: Bug is still présent with 0.12.0

Konsole output ls -ld /etc/sddm/Xsession -rwxr-xr-x 1 root root 1426 Sep 3 17:24 /etc/sddm/Xsession Konsole output ls -l /var/lib/sddm/ ls: cannot open directory /var/lib/sddm/: Permission denied ls -ld /var/lib/sddm/ drwxr-x--- 5 sddm sddm 4096 Sep 3 09:45 /var/lib/sddm/ Again kdm works, no

Bug#797519: Must be member of input group. Why?

After analyzing the startx error leading to no mouse and no keyboard, I found that I add to add myself in *input* group because all /dev/input/* devices belongs to root.input with some not being world readable. I have no clue of why I had to do this to use startx. I never had to do this

Bug#788913: Fwd: Re: Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 10:20 AM, VALETTE Eric OLNC/OLPS wrote: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab LABEL=TMP /tmp ext2defaults

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab LABEL=TMP /tmp ext2defaults0 2 -- eric

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 11:40 AM, Michael Biebl wrote: Am 16.06.2015 um 10:42 schrieb eric2.vale...@orange.com: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no separate /usr partition at all. There is just to much stuff that is (silently) broken by this. I just

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 01:30 PM, Michael Biebl wrote: Am 16.06.2015 um 13:18 schrieb eric2.vale...@orange.com: On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no

Bug#788100: 20141122 is not likely to fix the problem

Hi Tobias, Thanks for looking at the bug. FYI: When I first encountered it, I manually downloaded the last upstream version and tried it. This was not the debian version and I dunno what additional patches you may add but the problem was not fixed (few from memory). I will try your newer

Bug#782077: systemd: /etc/systemd/logind.conf HandleLidSwitchDocked not honred

On 04/07/2015 09:25 PM, Michael Biebl wrote: and it does check for the ev.code == SW_DOCK event: http://cgit.freedesktop.org/systemd/systemd/tree/src/login/logind-button.c#n203 Is is the event you get when docking? I boot with the laptop already

Bug#782077: systemd: /etc/systemd/logind.conf HandleLidSwitchDocked not honred

On 04/07/2015 09:17 PM, Michael Biebl wrote: What's your hardware? Which graphics card hardware / drivers do you use? It's a nvidia graphic adapter with nvidia drivers. How does systemd detect the docked status?

Bug#573074: symlinks: Please update to 1.4, it fixes assertion in malloc in a use case I have

On 03/09/2010 10:18 AM, VALETTE Eric RD-MAPS-REN wrote: Something along symlinks:malloc assert failed and a absolutely unreadable formula. Note that compiling the same tree with a level link less (I now have a symlink for /scratch were previously I had a real mounted fs was working. Note

Bug#573074: symlinks: Please update to 1.4, it fixes assertion in malloc in a use case I have

On 03/09/2010 02:02 PM, Sven Joachim wrote: I will do that anyway (might take some time to find a sponsor, though), but I would also like to understand the problem. In case it isn't clear: this assertion error is very weird and might just be a symptom of a problem that has nothing to do with

Bug#573074: symlinks: Please update to 1.4, it fixes assertion in malloc in a use case I have

On 03/09/2010 02:16 PM, VALETTE Eric RD-MAPS-REN wrote: a free of an address returned by a non reentrant function could perfectly cause it (try the _r version with explicit buffer allocation) Readding only the patch, the useage of the buffer returned by get_current_dir_name may be wrong: the

Bug#573074: symlinks: Please update to 1.4, it fixes assertion in malloc in a use case I have

Package: symlinks Version: 1.2-6 Severity: normal I have a use case where using 1.2-rel6 I hit and assertion in malloc that does not happend when I use 1.4 version of symlinks. As a result, compilation of a complex source tree fails. So please package the new version or aat leasta aggrgate

Bug#567003: Confirmed here also

-- eric * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the

Bug#566228: icedove-3.0: Lost dictionnaries + Cannot re-install dictionnaries

Package: icedove-3.0 Version: 3.0.1-1 Severity: normal I ahd no more dictionnaries (and other plugins when upgrading from 3.0-rc2 to 3.0.1. Then trying to add dictionnaries back, I get an error (install script not found). BTW at intslla it complained that it cannot remove dictorries under /etc

Bug#566228: Correction: the dictionnaries are still there but I cannot install a new one or reinstall

Subject says all. --eric * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be