Bug#708209: [Pkg-libvirt-maintainers] Bug#708209: virt-manager: unable to connect viewer

2013-05-21 Thread Laurent Léonard
Hi Dmitry,

I need the XML configuration file of the virtual machine, you can find it in 
/etc/libvirt/qemu if you use QEMU or KVM.

Please also specify the method you use to connect to the remote server.

Thank you,
-- 
Laurent Léonard


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



Bug#708209: [Pkg-libvirt-maintainers] Bug#708209: virt-manager: unable to connect viewer

2013-05-20 Thread Laurent Léonard
Hi Dmitry,

We are unable to reproduce the problem you describe. Could you please add the 
domain XML configuration file to this bug report?

Thank you,
-- 
Laurent Léonard


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



Bug#629128: [Pkg-libvirt-maintainers] Bug#629128: Bug#629128: regression in 0.8.8 reopens security issue

2011-06-03 Thread Laurent Léonard
Le vendredi 3 juin 2011 21:06:16, Guido Günther a écrit :
 On Fri, Jun 03, 2011 at 08:14:12PM +0200, Thijs Kinkhorst wrote:
  Package: libvirt
  Version: 0.8.8-1
  Severity: serious
  Tags: patch
  
  Hi,
  
  Version 0.8.8 introduced a regression which reopens a security issue.
  Please see:
  https://bugzilla.redhat.com/show_bug.cgi?id=709769
  https://www.redhat.com/archives/libvir-list/2011-May/msg01935.html
  
  Can you ensure that unstable and testing are fixed? Please reference
  CVE-2011-2178 in you changelog when you fix this issue.
 
 I won't be able to handle this during the next days so an NMU would be
 welcome. This affects testing, sid and squeeze-backports.

I will handle it.

-- 
Laurent Léonard



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



Bug#515507: kio-ftps FTBFS for KDE 4.2

2009-04-06 Thread Laurent Léonard
Le lundi 06 avril 2009 à 22:55, Sune Vuorela a écrit :
 Hi!

 This rc bug is now more than a month old with no comments from maintainer.
 Did you loose interest or ?

 /Sune

I was waiting for the KDE 4.2 release in sid to build the package... I will 
now fix the problem.

-- 
Laurent Léonard


signature.asc
Description: This is a digitally signed message part.


Bug#505240: [opensync-plugin-kdepim] Unable to sync KDE PIM with a mobile device

2008-11-26 Thread Laurent Léonard
Le mercredi 26 novembre 2008 à 16:09, Michael Banck a écrit :
 OK, sorry I missed that.  Can you try to filter out the note object type
 in msynctool, provided you don't want to sync notes (if you want to,
 please try it as well and tell me whether it works).

 This comand should do this:

 $ msynctool --sync Nokia E61i --filter-objtype note

It works ! And if I disable the Notes checkbox in the Kitchensync GUI it 
seems to work too. 

-- 
Laurent Léonard


signature.asc
Description: This is a digitally signed message part.


Bug#505240: [opensync-plugin-kdepim] Unable to sync KDE PIM with a mobile device

2008-11-10 Thread Laurent Léonard
Package: opensync-plugin-kdepim
Version: 0.22-3
Severity: serious

--- Please enter the report below this line. ---
When I try to synchronize KDE PIM with my Nokia E61i, I get this when I am 
using msynctool : 

[EMAIL PROTECTED]:~$ msynctool --sync Nokia E61i
Synchronizing group Nokia E61i
The previous synchronization was unclean. Slow-syncing
received event dsession
received contact dsession
received note dsession
Member 2 of type syncml-obex-client just connected
Member 1 of type kdepim-sync had an error while connecting: Kontact is 
running. Please finish it

Same problem with kitchensync. 

And if I try to close Kontact before the synchronization, Kontact is 
automatically launched when the synchronization begins. 

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.26-1-686

Debian Release: lenny/sid
 1001 testing security.debian.org 
 1001 testing ftp.fr.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-==
kdelibs4c2a  (= 4:3.5.8.dfsg.1-5) | 4:3.5.9.dfsg.1-6
libc6   (= 2.7-1) | 2.7-15
libgcc1| 1:4.3.2-1
libkcal2b (= 4:3.5.8) | 4:3.5.9-5
libopensync0 (= 0.22) | 0.22-2
libstdc++6   (= 4.1.1-21) | 4.3.2-1

-- 
Laurent Léonard


signature.asc
Description: This is a digitally signed message part.


Bug#505240: [opensync-plugin-kdepim] Unable to sync KDE PIM with a mobile device

2008-11-10 Thread Laurent Léonard
Le mardi 11 novembre 2008 à 01:27, Michael Banck a écrit :
 On Tue, Nov 11, 2008 at 01:13:59AM +0100, Laurent Léonard wrote:
  Package: opensync-plugin-kdepim
  Version: 0.22-3
  Severity: serious
 
  Member 1 of type kdepim-sync had an error while connecting: Kontact is
  running. Please finish it
 
  Same problem with kitchensync.
 
  And if I try to close Kontact before the synchronization, Kontact is
  automatically launched when the synchronization begins.

 Make sure kontact is not running still by inspecting the process list,
 please.


 Michael

Before I launch the sync process, Kontact is not running, ps -fe | grep 
kontact returns nothing. But when I launch the sync process, it launch 
Kontact but complains about its running state... 

-- 
Laurent Léonard


signature.asc
Description: This is a digitally signed message part.


Bug#475011: Impossible to launch guidance-power-manager

2008-04-08 Thread Laurent Léonard
Package: kde-guidance-powermanager
Version: 0.8.0-2.1
Severity: critical
Tags: patch

--- Please enter the report below this line. ---
Crash at the launch time : 
Traceback (most recent call last):
  File /usr/share/guidance/python/guidance-power-manager.py, line 1079, in ?
mainWindow = PowermanagerApp(None, main window)
  File /usr/share/guidance/python/guidance-power-manager.py, line 1016, in 
__init__
self.pmwidget = PowerManager(self,name)
  File /usr/share/guidance/python/guidance-power-manager.py, line 98, in 
__init__
self.powermanager = PowerManage()
  File /usr/share/guidance/python/powermanage.py, line 109, in __init__
self._checkSuspend()
  File /usr/share/guidance/python/powermanage.py, line 256, in _checkSuspend
self.canSuspend = properties[power_management.can_suspend_to_ram]
KeyError: 'power_management.can_suspend_to_ram'

I suppose HAL properties recently changed... I replaced those 2 lines 
in /usr/share/guidance/python/powermanage.py (line #255 and #256) : 
self.canSuspend = properties[power_management.can_suspend_to_ram]
self.canHibernate = properties[power_management.can_suspend_to_disk]
by
self.canSuspend = properties[power_management.can_suspend]
self.canHibernate = properties[power_management.can_hibernate]

Now it works again. 

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.24-1-amd64

Debian Release: lenny/sid
  500 unstableftp.fr.debian.org 
  500 stable  security.debian.org 
  500 stable  ftp.fr.debian.org 
 1000 testing www.emdebian.org 
 1000 testing security.debian.org 
 1000 testing ftp.fr.debian.org 
1 experimentalftp.fr.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-===
hal   | 0.5.11~rc2-1
kde-guidance  | 0.8.0-2.1
python| 2.4.4-6
python-dbus   | 0.82.4-2
python-kde3   | 3.16.1-1
python-support (= 0.7.1) | 0.7.7



signature.asc
Description: This is a digitally signed message part.