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 restart services if some have been upgraded. On the copmmand line, you are prompted to select or acknowledfge services that should be restarted. So you need to enter some keyboard input for at-get (dist-)upgrade to finish. Plasma disco\xe7ver does not cope with this. On PackageKit frontends, all transactions should be noninteractive, so they shouldn't interrupt the process to ask for stuff. One exception that we allow for compatibility is Debconf questions. So, if needrestart uses Debconf, this is a bug in plasma-discover and Discover should implement the Debconf frontend properly. If however needrestart doesn't use Debconf, this issue is "won't fix". From a quick look at the code, the former appears to be the case. Visually it looks like debconf questions with selectable list and grey and blue layout. But I did not look at the code. BTW : the fcat that by default it select packages as dist-upgrade would is also problematic. Can this be configured? -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Could not load plugin for core backend "" : "The shared library was not found." Loaded backend plugin: "pmsfdiskbackendplugin" "Connection \":1.112\" is not allowed to own the service \"org.kde.kpmcore.applicationinterface\" due to security policies in the configuration file" QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.79 (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8), LANGUAGE=en_US: en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages partitionmanager depends on: ii kio 5.62.1-2 ii libc6 2.29-2 ii libkf5configcore5 5.62.0-1 ii libkf5configgui5 5.62.0-1 ii libkf5configwidgets5 5.62.0-1 ii libkf5coreaddons5 5.62.0-1 ii libkf5crash5 5.62.0-1 ii libkf5dbusaddons5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libkf5iconthemes5 5.62.0-1 ii libkf5jobwidgets5 5.62.0-1 ii libkf5kiocore5 5.62.1-2 ii libkf5kiowidgets5 5.62.1-2 ii libkf5widgetsaddons5 5.62.0-1 ii libkf5xmlgui5 5.62.0-1 ii libkpmcore8 4.0.1-1 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5widgets5 5.11.3+dfsg1-4 ii libstdc++6 9.2.1-9 partitionmanager recommends no packages. Versions of packages partitionmanager suggests: pn btrfs-progs ii dosfstools 4.1-2 pn hfsplus pn hfsutils ii jfsutils 1.1.15-4 ii ntfs-3g 1:2017.3.23AR.4-1 pn reiser4progs pn reiserfsprogs ii xfsprogs 5.0.0-1+b1 -- no debconf information _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 is not present in sddm but in the nvidia driver, triggered by sddm by trying to use composite on the video output as is left by the X driver initialization. The bug is not only in the video driver as kdm works... El 2016-10-10 a las 11:01 +0200, eric2.vale...@orange.com escribió: 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. What happens if you use the maui sddm theme? To test this you'll need to install sddm-theme-maui, and create/modify your /etc/sddm.conf to include: [Theme] Current=maui The breeze theme starts sddm in composite mode, which might not be correctly initialized for your video card by default in your particular setup. Will try and report. This kind of disclaimers are useless in public mails, please avoid adding them. Consider using a different mail account if you can't remove it. It is automaically inserted fater I send the mail I cannot do anyting agains it. Will try another mail account. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 Severity: grave Justification: renders package unusable I understand that this is very frustrating for you, but there is an easy workaround, changing the font through the menu, thus I'm downgrading the bug severity. Once you figure out, this is "only" a "display" problem... Been hunting it for a while, started other shells, ... And if I post the bug, it is not for me but for others. But fine with the severity downgrade. In my konsole profile, I was using droid fonts that juts habe veen removed. So I started my konsole, got the screen but nothing was displayed at all. It should at least use a default (backup) font and print something to help user fixing the problem. To reprodure : define a profile witha font, then remove the font and restart. I've forwarded your bug report upstream, please, if possible, subscribe to the upstream bug, so if it needs to be followed up you can give the requested feedback. The upstream bug can be seen here: https://bugs.kde.org/show_bug.cgi?id=359669 Ok. Will do. But must be home to get a hand on my kde account credentials... -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 before. Or is it juts a leftover of kdm being started and then "suspended? via the login to konsole menu? Once done, the session did start correctly. After making the urgent work, I decided to retry login via kdm and bingo it worked again too. Did not try with sddm instead of kdm yet. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
Re: Bug#797519: kwin-x11: After upgrade : uanble to start sddm, login via kdm fails, and startx fails except for root
Nope. I have them already. I'm on unstable not testing btw. Thanks anyway for trying helping. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 log /var/log/sddm.log empty, nothing in xsession-errors... -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 denied ls -ld /var/lib/sddm/ drwxr-x--- 5 sddm sddm 4096 Sep 3 09:45 /var/lib/sddm/ Again kdm works, no log /var/log/sddm.log empty, nothing in xsession-errors... Does journalctl -b | grep sddm show anything interesting? Konsole output journalctl -b | grep sddm Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Control process exited, code=exited status=1 Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Unit entered failed state. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Failed with result 'exit-code'. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off time over, scheduling restart. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Control process exited, code=exited status=1 Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Unit entered failed state. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Failed with result 'exit-code'. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off time over, scheduling restart. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Control process exited, code=exited status=1 Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Unit entered failed state. Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Failed with result 'exit-code'. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off time over, scheduling restart. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Control process exited, code=exited status=1 Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Unit entered failed state. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Failed with result 'exit-code'. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off time over, scheduling restart. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Control process exited, code=exited status=1 Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Unit entered failed state. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Failed with result 'exit-code'. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off time over, scheduling restart. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Start request repeated too quickly. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Unit entered failed state. Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Failed with result 'start-limit'. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 in/var/log/sddm.log Note its a docked laptop, with external monitor used, lid closed and laptop monitor automatically desactivated. Are you by any chance running plymouth? If so, could this be a duplicate of #793637? 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. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 it was a specific case but now only this docked laptop remains broken. --eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 chipset with nvidia proprietary drivers like four others among the six that are non docked were sddm correcly works. -- eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
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 working with sddm and found the problem. Keyboard is connected via USB. I couldn't reproduce the issue testing sddm from snapshots version 0.11.0-3 that correspond to the date this issue was reported nor with the current version in unstable (0.12.0-2), so I'm downgrading the bug severity. Can you still reproduce the problem? Happy hacking, Yes on all the boxes. You swutch to a terminal, do service sddm stop and then service sddm start, an try to login. Tested this morning again... -- Eric Valette Orange Lab Product and Services Homebox Etudes Architecture et Développement Architecte Livebox et Set Top Box tél : (+33) 2 99 12 45 71 mél : _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
