Hi there, is this problem still active?
** Changed in: blueproximity
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/456284
Title:
proximity.py crashed with TypeError
Could someone please check if this is still a problem with the newest version
of Kubuntu?
Thx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/269322
Title:
Daily kernel Oops kills keyboard
To manage
** Changed in: blueproximity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/313040
Title:
blueproximity calls the proximity command twice each interval
To manage noti
Hi there, I haven't written a line of code for many years now but I wasn't
aware there are still that many users out there using it.
Is this problem still existing? Since there has not been any code change I
guess there is a problem in the way bp calls the external commands for
detection. It has
@jsalvata:
could you explain what the patch modifies and for which reason? I may recheck
the patch then so I might include it upstream. I am at work now, so I don't
have my development environment here with me.
--
blueproximity calls the proximity command twice each interval
https://bugs.launch
@jsalvata:
oh, and could you tell me in what environment this error popped up? were you
checking presence of multiple devices? I'd like to reproduce that bug later at
home.
--
blueproximity calls the proximity command twice each interval
https://bugs.launchpad.net/bugs/313040
You received this
Hi Michael, Chris,
sorry to step into this conversation way too late. I changed my job last year's
summer and bought a house too. So it's no wonder I had little time afterwards
to move back to development on blueproximity.
It is true that I use LP now to track things like this.
I can confirm the
Thanks for marking it invalid but this is more a general question. Would
it be necessary to remove installation parts of upstream manuals? I
believe the user that actually reads that information is already clever
enough to skip that part by himself but that are just my two cents - so
is there a gen
Isn't this a thing for the packager? I one did that myself but now I
think we just sync the debian package.
The manual is the same for all distributions so it should be ok to have
the reference to the "old" feisty release. This part of the manual can
be safely ignored since one already managed to
Isn't this a thing for the packager? I one did that myself but now I
think we just sync the debian package.
The manual is the same for all distributions so it should be ok to have
the reference to the "old" feisty release. This part of the manual can
be safely ignored since one already managed to
Hi,
Sorry I catch on this bug so late, is it still there?
Is only scanning affected or even the whole communication?
Do you have (I cannot see that in dmesg but ask for it anyway) another
bluetooth device connected? Could you post the output of the hciconfig
command please?
What is the output of
Hi,
1. I was asked by persia to help with migration. I believe that GTK1.2 support
is to be dropped soon (it will still be in hardy but not in intrepid)
2. I am not so sure about that one but I removed the build dependency because
it's either GTK2 including it differently now or it's e16menuedit
Sorry, here is an actually working new patch. Don't know why there was a
problem with the old patch, I didn't touch the line patch tells to be malformed
:-)
Anyhow, it is fixed now, patch does not complain anymore.
** Attachment added: "Debdiff for cccd_0.3beta4-6ubuntu1"
http://launchpadlibr
Here's the modified patch. Thanks for the hints, RainCT. I shamelessly
used your changelog example :-)
** Attachment added: "Debdiff for cccd_0.3beta4-6ubuntu1"
http://launchpadlibrarian.net/12386924/cccd_0.3beta4-6build2.debdiff
--
patch for use of gtk2.0
https://bugs.launchpad.net/bugs/197
Converted to a sync request.
--
[Sync request] Sync glotski (0.2-6) from Debian unstable (main)
https://bugs.launchpad.net/bugs/197507
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Summary changed:
- ported from obsolete GTK1.2 to GTK2
+ [Sync request] Sync glotski (0.2-6) from Debian unstable (main)
** Changed in: glotski (Ubuntu)
Assignee: Lars Friedrichs (l-friedrichs) => (unassigned)
Status: In Progress => New
--
[Sync request] Sync glotski
Ok, after working a bit on this one I wanted to post it to upstream but
have found that debians BTS files this issue with a patch already under
bug 460768. The patches are almost identical so my changes should be
safe. Next upstream version will be ok anyway.
--
ported from obsolete GTK1.2 to GTK
** Attachment added: "Debdiff for glotski_0.2-5ubuntu1"
http://launchpadlibrarian.net/12346549/glotski_0.2-5ubuntu1.debdiff
** Changed in: glotski (Ubuntu)
Status: New => Confirmed
--
ported from obsolete GTK1.2 to GTK2
https://bugs.launchpad.net/bugs/197507
You received this bug noti
Public bug reported:
I am not so sure about the debian/substvars changes and if all build-
deps are now correct. It has built on my system though (almost virgin
pbuilder env). The package installs with no problems on a hardy livecd.
I am not very deep into package creation so I decided no to inte
Public bug reported:
debdiff attached - please drop me a line if you expect more info here...
** Affects: e16menuedit (Ubuntu)
Importance: Undecided
Status: Confirmed
--
ported from obsolete GTK1.2 to GTK2
https://bugs.launchpad.net/bugs/197478
You received this bug notification b
** Attachment added: "Debdiff for e16menuedit_0.1.3-3ubuntu1"
http://launchpadlibrarian.net/12345748/e16menuedit_0.1.3-3ubuntu1.debdiff
** Changed in: e16menuedit (Ubuntu)
Status: New => Confirmed
--
ported from obsolete GTK1.2 to GTK2
https://bugs.launchpad.net/bugs/197478
You receiv
** Changed in: cccd (Ubuntu)
Status: New => Confirmed
--
patch for use of gtk2.0
https://bugs.launchpad.net/bugs/197358
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
** Attachment added: "Debdiff"
http://launchpadlibrarian.net/12342864/cccd_0.3beta4-6build2.debdiff
--
patch for use of gtk2.0
https://bugs.launchpad.net/bugs/197358
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Public bug reported:
As persia mentioned we need to upgrade packages from gtk1.2 to gtk2.0 this is
it. took few source changes.
I updated debian/control and debian/changelog too
** Affects: cccd (Ubuntu)
Importance: Undecided
Status: Confirmed
--
patch for use of gtk2.0
https://b
** Changed in: ubuntu
Status: In Progress => Fix Released
--
[needs-packaging] BlueProximity
https://bugs.launchpad.net/bugs/137339
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Hi,
I tried to backport the patch to feisty. I hope everything is correct as this
is my first security fix.
Please let me know if things are allright.
Bye
Lars
** Attachment added: "Feisty Patch"
http://launchpadlibrarian.net/11902652/python-cherrypy_2.2.1-3ubuntu1.1.debdiff
--
[python-ch
Public bug reported:
in the docs
/usr/share/doc/python-bluez/bluetooth.html
is the only html file but it refers to several others. These files are missing
in the build. It should be rebuilded withthe complete docs or without the above
file.
** Affects: pybluez (Ubuntu)
Importance: Undecide
** Changed in: ubuntu
Assignee: (unassigned) => Lars Friedrichs (l-friedrichs)
Status: New => In Progress
--
[needs-packaging] BlueProximity
https://bugs.launchpad.net/bugs/137339
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
Hi Claudiu,
thanks for your effort to include my package into the official repositories. I
am a strong supporter of this idea :-).
Just as a side note to decision makers: Version 1.2 is quite stable and gives a
good user feedback. I alrady packaged it on my own and there is another
packaged ver
29 matches
Mail list logo
