kblueplugd crashed with ImportError in <module>()

Bug #135893 reported by Brazilian Joe
466
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kdebluetooth (Ubuntu)
Fix Released
Medium
Anthony Mercatante
Nominated for Jaunty by Rafael Belmonte
python-defaults (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Jaunty by Rafael Belmonte

Bug Description

Binary package hint: kdebluetooth

Here is what I did:

Install feisty-amd64 from standard desktop install.
Even before doing a full update on the system, change all references on /et/apt/sources.list to gutsy
sudo apt-get dist-upgrade

After the distro upgrade, the error message appeared.

ProblemType: Crash
Architecture: amd64
Date: Thu Aug 30 14:39:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/kblueplugd
InterpreterPath: /usr/bin/python2.5
Package: kdebluetooth 1.0~beta6~r706303-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/bin/python /usr/bin/kblueplugd
ProcCwd: /home/tfreire
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/kblueplugd']
SourcePackage: kdebluetooth
Title: kblueplugd crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/kblueplugd", line 13, in <module>
     import gobject
 ImportError: No module named gobject
Uname: Linux rainforest 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux

Related branches

Revision history for this message
Brazilian Joe (tiago-freire) wrote :
Revision history for this message
Ernesto Ruge (the-infinity) wrote :

here (gutsy fresh alpha5 install) the same bug ...

Revision history for this message
einfach (freu-dich) wrote :

Why is this being installed on a computer with no bluetooth?

Revision history for this message
technogran (slarge) wrote :

I too am getting this, but in my case,,every time I go into Kubuntu tribe 5 getting a 'could not start bluetooth! error message. This is since either yesterdays updates or todays.

Revision history for this message
Jeroen Tietema (jtietema) wrote :

Same for me. I'm running gutsy tribe5. Saw the crash for the first time after updating today

Revision history for this message
zahov (zahov) wrote :

It happened after upgrade to gutsy. Happens after logon to KDE.

Revision history for this message
Thomas (cplusplus) wrote :

Same for me, just after KDE start. I have a fresh Gutsy Tribe 5 install from the alternate install cd with newes updates. Maybe the "The Process for the protocoll file was terminated" error message has something to do with it?

Revision history for this message
Chris (c-lusby-gmail) wrote :

Same bug here on gutsy tribe 5.

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote :

Same crash here on a 4 days old Tribe 5 install.
My opinion is that Ubuntu should offer an extra configuration dialog in the installer which would allow users to disable initialization of unwanted subsystems and daemons, like for example Bluetooth, though not necessarily meaning that the subsystem will not be installed and ready for later activation.

Be it as it is, Gutsy is quite good working ;).

Revision history for this message
Frank (frank-schaeffer) wrote :

Same here. Bluetooth daemon kplugd crash at kde startup since 01.09.07 update. The version before has been working as expected.
Seems that bluetooth is regularly changed from working to not working.

If bluetooth is switched on (Thinkpad Z61m) at system boot bluetooth will work and the daemon doesn't crash. In all other cases the daemon crashed and I' am not be able to start it.

Crash report is attached

Revision history for this message
Michael Mittler (launchpad-michael-mittler) wrote :

Same here directly after KDE starts.

Revision history for this message
Saurus (saurus) wrote :

Same for me, just after KDE start. I have a Gutsy Tribe 5 32bit updated. It is a problem not only of a 64bit architecture

Revision history for this message
scamp (telbert) wrote :

same here after kde start.
intel core 2 duo, santa rosa, hp compaq 6710s with bluetooth

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

I can confirm this. IBM T42 with bluetooth. Happens on KDE login.

Revision history for this message
Alex Lowe (lengau) wrote :

I can confirm this. I don't have any Bluetooth hardware attached, and it opens and crashes.

Changed in kdebluetooth:
status: New → Confirmed
Revision history for this message
Mikael Bergqvist (mikaelb) wrote :

Same for me. Happened after yesterdays updates.

Revision history for this message
Quadchris (christophe-caillet) wrote :

Same for me it crashes when KDE is starting after the login phase but when i restart it by Menu->System->Kbluetooth it works perfectly.

My Laptop is an ASUS F3SV-AK143C

Revision history for this message
Luka Renko (lure) wrote :

Last version reports:
Traceback (most recent call last):
  File "/usr/bin/kblueplugd", line 15, in <module>
    import dbus.mainloop.qt
ImportError: No module named qt

This is probably due to switch to qt4 event loop in dbus.

It seems like python-qt4-dbus does not install qt mainloop integration properly. It installs these files:
/usr/lib/python2.5/dbus/mainloop
/usr/lib/python2.5/dbus/mainloop/qt.so
/usr/lib/python2.4/dbus/mainloop
/usr/lib/python2.4/dbus/mainloop/qt.so

While glib mainloop seems to bi installed here:

/usr/share/python-support/python-dbus/dbus/mainloop
/usr/share/python-support/python-dbus/dbus/mainloop/__init__.py
/usr/share/python-support/python-dbus/dbus/mainloop/glib.py

Revision history for this message
miked (miked11) wrote :

Fresh install of Gutsy Gibbon Tribe 5 x86.iso Alt install with dist-updates and upgrades applied.
Kubuntu/Xubuntu-Desktop installed, and fluxbox/sox.
Added debugging symbols.
First successful login had libonobo crash/bug (bonobo-activation-server?).
This crash came up on second login.

Revision history for this message
miked (miked11) wrote :

crashed again after login and logout, I don't have any bluetooth stuff. I don't know where the crash reports go on the KDE side.

Revision history for this message
Frank (frank-schaeffer) wrote : Re: [Bug 135893] Re: kblueplugd crashed with ImportError in <module>()

On Monday 03 September 2007 14:36:55 miked wrote:
> crashed again after login and logout, I don't have any bluetooth stuff.
> I don't know where the crash reports go on the KDE side.

@miked
Crash reports are stored in /var/crash

Revision history for this message
miked (miked11) wrote :

Thanks

Revision history for this message
miked (miked11) wrote :
Revision history for this message
Sayers (sjsayers93) wrote :

I have a similar error but with applying changes to kopete.

Revision history for this message
vingiul (giuliani-vincenzo) wrote :

Error ID OOPS-611A851 - after a timeout error
Kubuntu Gutsy Gibbon Tribe 5 Daily Updated, Sept, 03 2007 version, Notebook ASAU A 6000 Series, a6je; lspci result attached

Revision history for this message
AndreasDK (andersen1982) wrote :

It crashes every time I boot up my IBM R50e. despite the fact that i have no
bluetooth dongle or the like attached.

2007/9/3, vingiul <email address hidden>:
>
> Error ID OOPS-611A851 - after a timeout error
> Kubuntu Gutsy Gibbon Tribe 5 Daily Updated, Sept, 03 2007 version,
> Notebook ASAU A 6000 Series, a6je; lspci result attached
>
> ** Attachment added: "lspci.txt"
> http://launchpadlibrarian.net/9101032/lspci.txt
>
> --
> kblueplugd crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/135893
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Yannick (splitsch) wrote :

I have a thinkpad R50E too, and it crashes sometimes, and sometimes not.
I run an ud-to-date Kubuntu Gutsy.

Thanks

Revision history for this message
tavella (tony-avella) wrote :

I have a Dell M1210 w/ Core 2 Duo 7200 2.0Ghz, Nvidia 7400 chipset, and Dell 355 2.0 + EDR chip and receive this error upon every boot up.

Revision history for this message
4gottenshadow (4gottenshadow) wrote :

I have a Lenovo T60p and it seems like the only time it crashes is when I'm in Konsole. I left it konsole open and it doesn't seem like it crashes when it is just opened but when I'm in a secure shell and editing something. I've also noticed it's when I'm typing and holding down the shift key.

Revision history for this message
Neal Holtz (nholtz) wrote :

Happens to me too,right after KDE login.

Gutsy tribe 4 (I think) with latest upgrades.

Started a few days ago (before Sept 1), after an upgrade.

Revision history for this message
root_san (root-san) wrote :

> ----- Original Message -----
> From: "Neal Holtz" <email address hidden>
> To: <email address hidden>
> Subject: [Bug 135893] Re: kblueplugd crashed with ImportError in <module>()
> Date: Tue, 04 Sep 2007 19:33:03 -0000
>
>
> Happens to me too,right after KDE login.
Yeap, the upgrade give some rare things.
> Gutsy tribe 4 (I think) with latest upgrades.
I happen the solution. becouse is uncomfortable
> Started a few days ago (before Sept 1), after an upgrade.
>
> --
> kblueplugd crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/135893
> You received this bug notification because you are a direct subscriber
> of the bug.

>

see you

---------------------------------------------------
Efr�n S�nchez Ju�rez
Circuito Lim�n Real No. 55 Fracc.
Los Naranjos La Estancia, CP.69005.
Huajuapan de Le�n, Oaxaca.
Cel. 9531008208
http://gulmix.ath.cx/~san/

=
Globe Term Life Insurance
$1 Buys $50,000 Life Insurance. No Medical Exam, No Waiting Period.
http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=942040759ff92044ff9e7060048ccf5c

--
Powered by Outblaze

Revision history for this message
Ram (ram-balaraman) wrote :

Happens right after KDE login

Revision history for this message
filippo colombo (thelion85) wrote :

Kbluplugd crashed in kubuntu gusty cd tribe 5.

Revision history for this message
kiloxxx (kiloxxx) wrote :

Here the same problem, immediately after KDE login (with Gutsy 5, after enabling extra repositories and updating bluetooth related packages). However, after the crash, I could start bluetooth server manually and it works.

Revision history for this message
Dennis Edmonds (dennis-edmonds) wrote :

Still crashing for me after this mornings kde update, with or without usb bluetooth adapter.

Linux 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux.

kdebluetooth 1.0~beta6~r707240-0ubuntu1

Revision history for this message
Christopher B. Wright (wrightc) wrote :

I have found that it is possible to load kbluetooth immediately after it crashes, and it will function normally afterwards. It will always crash when I log in, though.

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote :

It must be that kbluetooth fails to start because some required module fails
to load or is not loaded at that stage.
Could be a loading order problem.

On 9/5/07, Christopher B. Wright <email address hidden> wrote:
>
> I have found that it is possible to load kbluetooth immediately after it
> crashes, and it will function normally afterwards. It will always crash
> when I log in, though.
>
> --
> kblueplugd crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/135893
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
[Thorns]
Tessa IM at OL - http://obsidianlake.com/
My blog - http://obsidianlake.blogspot.com/
My host - http://www.aquawebsolutions.com/

Revision history for this message
Luka Renko (lure) wrote :

As a temporary workaround for this problem you can create this symbolic link by running this command from Konsole:

sudo ln -s /usr/lib/python2.5/dbus/mainloop/qt.so /var/lib/python-support/python2.5/dbus/mainloop/qt.so

Revision history for this message
Luka Renko (lure) wrote :

This has to be properly fixed before Beta.

Changed in kdebluetooth:
importance: Undecided → Medium
Matthias Klose (doko)
Changed in kdebluetooth:
assignee: nobody → doko
status: Confirmed → In Progress
Revision history for this message
Matthias Klose (doko) wrote :

fixed with the recent python-qt4 upload.

Changed in kdebluetooth:
status: In Progress → Fix Released
Revision history for this message
"Kosmonaut" Bernd Müller (bernado-tornado) wrote :

confirming this bug

Revision history for this message
Quadchris (christophe-caillet) wrote :

my system is up to date but bug is still here ... perhaps it is due to resume state of my laptop.
This issue occured after i restarted my laptop which was in hibernate state and restart the X server.

description: updated
description: updated
description: updated
description: updated
Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote :
Download full text (5.1 KiB)

I think the fix worked for me, I didn't get any crash notice today. So I'm
confirming the fix.

On 9/7/07, Stéphane Graber <email address hidden> wrote:
>
> ** Description changed:
>
> Binary package hint: kdebluetooth
>
> Here is what I did:
>
> Install feisty-amd64 from standard desktop install.
> Even before doing a full update on the system, change all references on
> /et/apt/sources.list to gutsy
> sudo apt-get dist-upgrade
>
> After the distro upgrade, the error message appeared.
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 30 14:39:29 2007
> DistroRelease: Ubuntu 7.10
> ExecutablePath: /usr/bin/kblueplugd
> InterpreterPath: /usr/bin/python2.5
> Package: kdebluetooth 1.0~beta6~r706303-0ubuntu2
> PackageArchitecture: amd64
> ProcCmdline: /usr/bin/python /usr/bin/kblueplugd
> ProcCwd: /home/tfreire
> ProcEnviron:
> -
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> - LANG=en_US.UTF-8
> - SHELL=/bin/bash
>
> + PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + LANG=en_US.UTF-8
> + SHELL=/bin/bash
> PythonArgs: ['/usr/bin/kblueplugd']
> SourcePackage: kdebluetooth
> Title: kblueplugd crashed with ImportError in <module>()
> Traceback:
> - Traceback (most recent call last):
> - File "/usr/bin/kblueplugd", line 13, in <module>
> - import gobject
> - ImportError: No module named gobject
> + Traceback (most recent call last):
> + File "/usr/bin/kblueplugd", line 13, in <module>
> + import gobject
> + ImportError: No module named gobject
> Uname: Linux rainforest 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT
> 2007 x86_64 GNU/Linux
>
> ** Tags removed: iso-testing
>
> ** Description changed:
>
> Binary package hint: kdebluetooth
>
> Here is what I did:
>
> Install feisty-amd64 from standard desktop install.
> Even before doing a full update on the system, change all references on
> /et/apt/sources.list to gutsy
> sudo apt-get dist-upgrade
>
> After the distro upgrade, the error message appeared.
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 30 14:39:29 2007
> DistroRelease: Ubuntu 7.10
> ExecutablePath: /usr/bin/kblueplugd
> InterpreterPath: /usr/bin/python2.5
> Package: kdebluetooth 1.0~beta6~r706303-0ubuntu2
> PackageArchitecture: amd64
> ProcCmdline: /usr/bin/python /usr/bin/kblueplugd
> ProcCwd: /home/tfreire
> ProcEnviron:
>
> - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> - LANG=en_US.UTF-8
> - SHELL=/bin/bash
> +
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + LANG=en_US.UTF-8
> + SHELL=/bin/bash
> PythonArgs: ['/usr/bin/kblueplugd']
> SourcePackage: kdebluetooth
> Title: kblueplugd crashed with ImportError in <module>()
> Traceback:
> - Traceback (most recent call last):
> - File "/usr/bin/kblueplugd", line 13, in <module>
> - import gobject
> - ImportError: No module named gobject
> + Traceback (most recent call last):
> + File "/usr/bin/kblueplugd", line 13, in <module>
> + import gobject
> + ImportError: No module named gobject
> Uname: Linux rainforest 2.6.22-1...

Read more...

Revision history for this message
MartinoRob (martinorob) wrote :

The fix worked for me too, but now i cant receive any file from my phone.. How I can do to fix this?

Revision history for this message
Urs Fleisch (ufleisch) wrote :

It crashes on my system (gutsy up-to-date, /etc/rc2.d/S25bluetooth removed) when logging into KDE. The symbolic link mentioned above did already exist but does not help.

Revision history for this message
AndreasDK (andersen1982) wrote :

Can someone please tell me how to enable the auto info about updates?

I have to manually update in the console?

2007/9/20, Urs Fleisch <email address hidden>:
> It crashes on my system (gutsy up-to-date, /etc/rc2.d/S25bluetooth
> removed) when logging into KDE. The symbolic link mentioned above did
> already exist but does not help.
>
> --
> kblueplugd crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/135893
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Urs Fleisch (ufleisch) wrote :

As I have no bluethooth device, I have removed /etc/rc2.d/S25bluetooth and kblueplugd crashes every time I start up. So I had a look at the problem and found the following bug:

/usr/bin/python /usr/bin/kblueplugd
line 34, in <module>
if len(manager.ListAdapters()):
NameError: name 'manager' is not defined

kblueplugd crashed with NameError in <module>()

The bluez dbus object is not found, but the program continues because the line with "exit" does not behave as expected (it does not call exit() because of the missing parentheses), so it should be fixed like this:

--- /usr/bin/kblueplugd.orig 2007-09-23 09:37:24.000000000 +0200
+++ /usr/bin/kblueplugd 2007-09-23 09:44:59.000000000 +0200
@@ -29,7 +29,7 @@
         manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')
 except:
         print "Unable to connect to bluez."
- exit
+ sys.exit(1)

 if len(manager.ListAdapters()):
         print "# of devices at startup:", len(manager.ListAdapters())

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

Upgraded from Feisty using 'apt-get dist-upgrade', kubuntu-desktop always installed.

I experience the crash whether or not my Bluetooth adaptor is plugged in.
Subsequently, kbluetoothd doesn't detect any devices, even if my adaptor is plugged in.

The 'bluetooth' package was not installed during the upgrade.
Installing it manually, and then starting it, resulted in kbluetoothd working.

However, during installation 'bluetooth' isn't set to start by default at runlevel 2.
Running 'System Services' and setting it to start at boot made kblueplugd stop crashing.

Revision history for this message
Luka Renko (lure) wrote :

Reopening as at least two issues are still there.

Changed in kdebluetooth:
assignee: doko → tonio
status: Fix Released → Confirmed
Revision history for this message
Kees Cook (kees) wrote :

This bug is closed. The new bug you're seeing is bug 136307.

Changed in kdebluetooth:
status: Confirmed → Fix Released
Revision history for this message
Anthony Mercatante (tonio-kubuntu-x) wrote :

kdebluetooth (1.0~beta8-0ubuntu2) gutsy; urgency=low

  * Fixed debian/control, kdebluetooth depends on python-qt4
    Fixes LP: #135893

 -- Anthony Mercatante <tonio@kubuntu> Mon, 24 Sep 2007 16:36:37 +0200

Revision history for this message
NeoFax (neofax99) wrote :

Still a problem on Jaunty Alpha 5

Revision history for this message
salpiche (salpiche) wrote : Re: [Bug 135893] Re: kblueplugd crashed with ImportError in <module>()

Thanks

On Fri, Mar 6, 2009 at 9:47 PM, NeoFax <email address hidden> wrote:
> Still a problem on Jaunty Alpha 5
>
> --
> kblueplugd crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/135893
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Rafael Belmonte (eaglescreen) wrote :

I have obtained this report from Apport today in Kubuntu 9.04 beta.
I think this bug may be a duplicate of Bug #26857.
Many python applications crash when python packages are updated.

Changed in kdebluetooth:
status: Fix Released → New
Revision history for this message
Rafael Belmonte (eaglescreen) wrote :

This may be a duplicate of Bug #268574. NOT 26857, sorry.

Revision history for this message
kuser (nuca-nunca) wrote :

same here, apport report on kubuntu 9.04 alpha...

Revision history for this message
Xosé (ubuntu-galizaweb) wrote :

Same here - and no bluetooth devices!

Revision history for this message
Brian Murray (brian-murray) wrote :

If apport presented you with a crash report where is your apport crash information? Is it in a new bug report? How did you end up at this bug?

Changed in kdebluetooth (Ubuntu):
milestone: tribe-6 → none
status: New → Incomplete
Revision history for this message
s_aldinger (scott-aldinger) wrote :

This bug message popped up on first boot of a fresh install of the amd64
beta of jaunty. It has *not* appeared since.
As to why there is no apport crash info.. I don't know.

.

On Thu, Apr 16, 2009 at 9:07 AM, Brian Murray <email address hidden> wrote:

> If apport presented you with a crash report where is your apport crash
> information? Is it in a new bug report? How did you end up at this
> bug?
>
> ** Changed in: kdebluetooth (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: kdebluetooth (Ubuntu)
> Milestone: tribe-6 => None
>
> --
> kblueplugd crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/135893
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kdebluetooth” source package in Ubuntu: Incomplete
> Status in “python-defaults” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: kdebluetooth
>
> Here is what I did:
>
> Install feisty-amd64 from standard desktop install.
> Even before doing a full update on the system, change all references on
> /et/apt/sources.list to gutsy
> sudo apt-get dist-upgrade
>
> After the distro upgrade, the error message appeared.
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Aug 30 14:39:29 2007
> DistroRelease: Ubuntu 7.10
> ExecutablePath: /usr/bin/kblueplugd
> InterpreterPath: /usr/bin/python2.5
> Package: kdebluetooth 1.0~beta6~r706303-0ubuntu2
> PackageArchitecture: amd64
> ProcCmdline: /usr/bin/python /usr/bin/kblueplugd
> ProcCwd: /home/tfreire
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> PythonArgs: ['/usr/bin/kblueplugd']
> SourcePackage: kdebluetooth
> Title: kblueplugd crashed with ImportError in <module>()
> Traceback:
> Traceback (most recent call last):
> File "/usr/bin/kblueplugd", line 13, in <module>
> import gobject
> ImportError: No module named gobject
> Uname: Linux rainforest 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT
> 2007 x86_64 GNU/Linux
>

--
C'est magnifique, mais ce n'est pas la guerre!
       [It is magnificent, but it is not war]
               -- Pierre Bosquet, witnessing the charge of the Light Brigade

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

The new bug is bug 348704. I'm closing this one as this was fixed in 2007. (Same symptoms, different bug)

Changed in kdebluetooth (Ubuntu):
status: Incomplete → Fix Released
Changed in python-defaults (Ubuntu):
status: New → Invalid
Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote : Paul-Sebastian Manole wants to stay in touch on LinkedIn

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Paul-Sebastian Manole

Confirm that you know Paul-Sebastian Manole
https://www.linkedin.com/e/isd/1040409546/jonnzdJN/

------
(c) 2010, LinkedIn Corporation

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.