** Also affects: xubuntu-default-settings (Ubuntu)
Importance: Undecided
Status: New
--
[9.04 beta] no way to access screensaver enable/disable or timer settings like
pre-beta 9.04
https://bugs.launchpad.net/bugs/350962
You received this bug notification because you are a member of
** Changed in: xubuntu-default-settings (Ubuntu)
Status: New = Confirmed
** Also affects: mythbuntu-default-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mythbuntu-default-settings (Ubuntu)
Status: New = Confirmed
** Changed in:
** Also affects: xfce4-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xfce4-utils (Ubuntu)
Status: New = Confirmed
** Changed in: xfce4-utils (Ubuntu)
Milestone: None = ubuntu-9.04
--
[9.04 beta] no way to access screensaver enable/disable or timer
setting to High on Mythbuntu task as mythtv-setup uses zenity and can
cause weird behaviors when setting up a box otherwise.
** Also affects: mythbuntu
Importance: Undecided
Status: New
** Changed in: mythbuntu
Importance: Undecided = High
** Changed in: mythbuntu
Status:
Fixed in mythbuntu daily disks starting april 12, closing mythbuntu task
** Changed in: mythbuntu
Status: Confirmed = Fix Released
--
[9.04 beta] no way to access screensaver enable/disable or timer settings like
pre-beta 9.04
https://bugs.launchpad.net/bugs/350962
You received this bug
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mythbuntu-control-centre (Ubuntu)
Status: New = Won't Fix
--
MCC Segmentation Fault
https://bugs.launchpad.net/bugs/273159
You received this bug notification because you are a member of Ubuntu
Anyone have any workarounds in the glade xml? I'd prefer to make my
apps warning free, and this is all i'm down to.
--
could not find a parent that handles internal children
https://bugs.launchpad.net/bugs/273233
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: mythplugins (Ubuntu)
Status: New = Invalid
--
Merge libdvdread 4.x from Debian unstable
https://bugs.launchpad.net/bugs/330684
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in ubuntu.
--
** Changed in: gnome-control-center (Ubuntu)
Assignee: Mario Limonciello (superm1) = Sebastien Bacher (seb128)
--
Notification window is not translatable
https://bugs.launchpad.net/bugs/331818
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Hi guys:
I've submitted a few patches upstream that got accepted to 1.1.2 that
should hopefully fix this problem. Can people who are running into it
try running version 1.1.2-0ubuntu1 on Ubuntu Jaunty?
Thanks,
--
nautilus-sendto doesn't support Obex Push file transfer since intrepid
** Changed in: nautilus-sendto (Ubuntu)
Status: Triaged = Fix Released
--
nautilus-sendto doesn't support Obex Push file transfer since intrepid
https://bugs.launchpad.net/bugs/282325
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/23077977/Screenshot.png
--
Eject notification doesn't use new notification framework
https://bugs.launchpad.net/bugs/333997
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
Binary package hint: gnome-settings-daemon
The new notification elements work wonderfully, except it seems that
eject doesn't take advantage of them. See attached screenshot.
gnome-settings-daemon 2.25.90-0ubuntu4
** Affects: gnome-settings-daemon (Ubuntu)
to use this for educational
purposes :).
--
Notification window is not translatable
https://bugs.launchpad.net/bugs/331818
You received this bug notification because you are a bug assignee.
--
Mario Limonciello
supe...@gmail.com
--
Notification window is not translatable
https
marking fixed in Dell project. a workaround is posted at
http://linux.dell.com/wiki/index.php/Ubuntu_8.10/Issues/Resolution_Tool_Crash
until users upgrade to jaunty.
** Changed in: dell
Status: Confirmed = Fix Released
** Bug watch added: GNOME Bug Tracker #571214
Closing ubiquity task:
ubiquity (1.11.8) jaunty; urgency=low
* Make the timezone map only use PNGs to avoid a dependency on
python-gnome2-desktop and because we want to optimze for speed rather
than image quality.
* Automatic update of included source packages: partman-auto
There's actually a bzr branch attached for working around this issue and
a merge request filed for evaluating it.
** Changed in: gnome-settings-daemon
Status: New = Invalid
--
[Studio XPS 13, Inspiron 531, Studio 16] gnome-settings-daemon crash
https://bugs.launchpad.net/bugs/319725
You
So I think I've got some more information about this.
1) There are two types of SDP records for OBEX, 0x1105 and 0x1106. If
your phone supports 0x1106, then version 1.1.1 might just work for you.
If it supports 0x1105 you'll probably need another patch to add support
for it.
2) Not all phones
This is a much bigger issue now, ubiquity depends on rsvg for it's
timezone map. That means the current ubiquity in Jaunty won't work with
Xfce unless:
The following extra packages will be installed:
gnome-media gnome-media-common gstreamer0.10-alsa
gstreamer0.10-plugins-base
adding a ubiquity task. the depends will need to be adjusted once this
is fixed.
--
wnck and rsvg should be provided in seperate packages not requiring gnome
https://bugs.launchpad.net/bugs/223671
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Bug watch added: Debian Bug tracker #400651
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400651
** Also affects: gnome-python-desktop (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400651
Importance: Unknown
Status: Unknown
--
wnck and rsvg should be
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
[Studio XPS 13, Inspiron 531, Studio 16] gnome-settings-daemon crash
https://bugs.launchpad.net/bugs/319725
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
closing gnome desktop task. it was fixed in version 1:2.25.5-0ubuntu1
** Changed in: gnome-desktop (Ubuntu)
Status: In Progress = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because
*** This bug is a duplicate of bug 261721 ***
https://bugs.launchpad.net/bugs/261721
** This bug is no longer a duplicate of bug 285323
[Intrepid] Losing keyboard and mouse control when changing screen brightness
with fn + arrow (Dell)
** This bug has been marked a duplicate of bug
** Also affects: xfce4-session (Ubuntu)
Importance: Undecided
Status: New
--
gnome-keyring-daemon causes xfce4 startup to hang
https://bugs.launchpad.net/bugs/316222
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
** Bug watch added: Xfce Bugzilla #4803
http://bugzilla.xfce.org/show_bug.cgi?id=4803
** Also affects: xfce4-session via
http://bugzilla.xfce.org/show_bug.cgi?id=4803
Importance: Unknown
Status: Unknown
--
gnome-keyring-daemon causes xfce4 startup to hang
...@ubuntu.com wrote:
the issue seems similar to bug #316070
--
gnome-keyring-daemon causes xfce4 startup to hang
https://bugs.launchpad.net/bugs/316222
You received this bug notification because you are a member of
Mythbuntu, which is a direct subscriber.
--
Mario Limonciello
supe
I'm not sure it's necessarily an upstream bug. This started being included
which may have triggered it:
* debian/gnome-keyring.install:
- inclusion of
debian/tmp/usr/share/gnome/autostart/gnome-keyring-daemon.desktop.
--
gnome-keyring-daemon causes xfce4 startup to hang
** Bug watch added: GNOME Bug Tracker #567517
http://bugzilla.gnome.org/show_bug.cgi?id=567517
** Also affects: gnome-keyring via
http://bugzilla.gnome.org/show_bug.cgi?id=567517
Importance: Unknown
Status: Unknown
--
gnome-keyring-daemon causes xfce4 startup to hang
Public bug reported:
Binary package hint: gnome-keyring
WIthin the last few days, the mythbuntu daily live disk started to boot
up to a black screen. It looks like something in gnome-keyring-daemon
is causing problems.
You can still press alt-f2 to bring up the xfce start application
dialog.
** Attachment added: xsession-errors output
http://launchpadlibrarian.net/21113621/xsession-errors
--
gnome-keyring-daemon causes mythbuntu startup to hang
https://bugs.launchpad.net/bugs/316222
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Summary changed:
- gnome-keyring-daemon causes mythbuntu startup to hang
+ gnome-keyring-daemon causes xfce4 startup to hang
** Description changed:
Binary package hint: gnome-keyring
- WIthin the last few days, the mythbuntu daily live disk started to boot
- up to a black screen. It
I don't forsee any method to stop the BIOS from adjusting brightness
whtn the FN brightness keys are pressed. On Dell laptops, the xrandr
controls should simply not be used I say.
Mario Limonciello
Dell | Linux Engineering
mario_limoncie...@dell.com
-Original Message-
From: boun
a input.x11_driver property.
What do you think? Could you think of any issues with doing something
like that?
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a direct subscriber
of the bug.
--
Mario
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: acpi-support = gnome-power-manager
** Summary changed:
- Fn+F1 (XF86Standby) on Inspiron 1420 does not trigger hibernate or sleep
+ XF86Standby does not trigger hibernate or sleep
** Description changed:
- [Splitting this out from
Here's the dbus-monitor --system log.
** Attachment added: log
http://launchpadlibrarian.net/21013296/log
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
if you get HAL signals for any other
hotkeys, or is it just the battery key?
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a direct subscriber
of the bug.
--
Mario Limonciello
supe
Chris:
Thanks for helping to root cause this so quickly. It looks like this is
a pretty easy issue to fix for this release, but future gnome power
manager releases are going to have it, so i've filed a bug to see what
upstream can do about it (maybe a compile time switch to ./configure to
If you grab the kernel from proposed and it fixes it, you've got a
duplicate of bug 261721
--
Gnome brightness keybinding OSD locks interface
https://bugs.launchpad.net/bugs/314404
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Attachment added: log.txt
http://launchpadlibrarian.net/20986321/log.txt
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I've killed gnome-power-manager, and without it running, I only see a
single keypress and single keyrelease event for XF86Battery in xev.
That should rule out the kernel and xorg.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = New
--
notification daemon shows two
whoops, that was actually me, just on the wrong launchpad login :)
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = New
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a
Public bug reported:
Binary package hint: notification-daemon
I'm running a Jaunty daily from Jan 6.
notification-daemon 0.4.0-0ubuntu2.
Pressing fn-f3 normally pops up one popup of battery status. Pressing
it showsing two popups. Pressing it again shows another two popups.
** Affects:
** Attachment added: popups.png
http://launchpadlibrarian.net/20963123/popups.png
--
notification daemon shows two popups for fn-f3 event
https://bugs.launchpad.net/bugs/314547
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Binary package hint: gnome-settings-daemon
Hi:
I'm using a Jaunty daily from Jan 6 2009.
gnome-settings-daemon 2.25.3-0ubuntu1
metacity 1:2.25.34-0ubuntu1
Pressing the print screen key causes an error dialog No command 33 has
been defined. Going into
** Attachment added: screenshot.png
http://launchpadlibrarian.net/20963166/screenshot.png
** Tags added: regression
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
--
Pressing print screen causes No command 33 has been defined
Hi Andy:
After you restart gnome-power-manager, the XF86Battery keysym should be
sucked up by it. XF86Suspend is another story, and I'm not sure it's
current status.
Mario Limonciello
Dell | Linux Engineering
mario_limoncie...@dell.com
-Original Message-
From: boun...@canonical.com
*** This bug is a duplicate of bug 281134 ***
https://bugs.launchpad.net/bugs/281134
** This bug has been marked a duplicate of bug 281134
Battery key (Fn+F8) on hpnx6110 not handled in X with evdev
--
Fn+Battery doesn't work anymore on XPS M1330
https://bugs.launchpad.net/bugs/290283
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: xserver-xorg-input-evdev = gnome-power-manager
Status: Incomplete = Confirmed
** Summary changed:
- Battery key (Fn+F8) on hpnx6110 not handled in X with evdev
+ Intrepid regression: XF86Battery hotkey doesn't work
**
** Bug watch added: freedesktop.org Bugzilla #18854
https://bugs.freedesktop.org/show_bug.cgi?id=18854
** Also affects: xkeyboard-config via
https://bugs.freedesktop.org/show_bug.cgi?id=18854
Importance: Unknown
Status: Unknown
--
Intrepid regression: XF86Battery hotkey doesn't
** Description changed:
- Binary package hint: gnome-power-manager
-
Currently, several Dell laptops contain Intel graphics cards. The Intel
driver reports that it is able to change the display brightness, however
it also reports the number of levels supported is zero.
In cases such
** Description changed:
- While on earlier releases of ubuntu all hotkeys on my hpnx6110 were
- working as expected, in intrepid the battery key is not handled anymore
- when using X. When I switch to console and press the key-combination and
- then I switch back to X-session, the battery info is
Public bug reported:
Binary package hint: gnome-power-manager
Currently, several Dell laptops contain Intel graphics cards. The Intel
driver reports that it is able to change the display brightness, however
it also reports the number of levels supported is zero.
In cases such as these, gnome
** Bug watch added: GNOME Bug Tracker #562900
http://bugzilla.gnome.org/show_bug.cgi?id=562900
** Also affects: gnome-power via
http://bugzilla.gnome.org/show_bug.cgi?id=562900
Importance: Unknown
Status: Unknown
** Also affects: gnome-shutdown
Importance: Undecided
Since we haven't gotten much good data from other users yet, here's what
I've found testing with the package from -proposed:
* This fixes the Eject key on two unreleased Studio laptops
* This has no effect (no regressions nor improvements) on the following
platforms:
+ Studio 1535
+ Studio
Since we haven't gotten much good data from other users yet, here's what
I've found testing with the package from -proposed:
* This fixes the Eject key on two unreleased Studio laptops
* This has no effect (no regressions nor improvements) on the following
platforms:
+ Studio 1535
+ Studio
Nick:
That's not the new package. The new package is 2.24.0-0ubuntu3.3
Can you do an apt-get update and try again?
--
eject key doesn't work when disks are mounted
https://bugs.launchpad.net/bugs/299194
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
did you make sure you logged out/in or at least restarted gnome-
settings-daemon?
--
eject key doesn't work when disks are mounted
https://bugs.launchpad.net/bugs/299194
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
superm1 can you run xev and try to press the key?
superm1 see if it's caught there still?
foxbuntu nothing
superm1 that means gnome is probably grabbing it still...
superm1 if you kill gnome-settings-daemon, does it catch the key?
foxbuntu nope
superm1 okay then you have a different problem with
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: New = Triaged
--
eject key doesn't work when disks are mounted
https://bugs.launchpad.net/bugs/299194
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
** Description changed:
Binary package hint: gnome-settings-daemon
It appears that machines that have a software eject key are not able to
eject disks from gnome. In evaluating the cause of the problem, a lot
- of possible indicators show up. At a first glance it seems to be an X
- bug
*** This bug is a duplicate of bug 299194 ***
https://bugs.launchpad.net/bugs/299194
** This bug has been marked a duplicate of bug 299194
eject key doesn't work when disks are mounted
--
eject hotkey doesn't work
https://bugs.launchpad.net/bugs/258520
You received this bug notification
Public bug reported:
Binary package hint: gnome-settings-daemon
It appears that machines that have a software eject key are not able to
eject disks from gnome. In evaluating the cause of the problem, a lot
of possible indicators show up. At a first glance it seems to be an X
bug because
** Bug watch added: GNOME Bug Tracker #561275
http://bugzilla.gnome.org/show_bug.cgi?id=561275
** Also affects: gnome-settings-daemon via
http://bugzilla.gnome.org/show_bug.cgi?id=561275
Importance: Unknown
Status: Unknown
--
eject key doesn't work when disks are mounted
** Visibility changed to: Public
--
Fn+Battery doesn't work anymore on XPS M1330
https://bugs.launchpad.net/bugs/290283
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
Doesn't appear to happen with latest updates. Probably a temporary
inconsistency.
** Changed in: gdm (Ubuntu)
Status: Incomplete = Invalid
--
Setting up automatic login causes wrong soundset
https://bugs.launchpad.net/bugs/276057
You received this bug notification because you are a
I want to say this bug is at a different level in the stack than
directly at bluez. It should be reproducible with touchpads and and USB
mice too likely.
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
intrepid: bluetooth mouse settings lost
*** This bug is a duplicate of bug 261721 ***
https://bugs.launchpad.net/bugs/261721
This bug was mismarked as a duplicate of the wrong bug. Reassigning it
to the proper one.
** This bug is no longer a duplicate of bug 207473
Screen brightness double level changes
** This bug has been
that.
--
nautilus-sendto doesn't support Obex Push file transfer anymore
https://bugs.launchpad.net/bugs/282325
You received this bug notification because you are a direct subscriber
of the bug.
--
Sent from my mobile device
Mario Limonciello
[EMAIL PROTECTED]
--
nautilus-sendto doesn't
totem (2.24.1-0ubuntu4) intrepid; urgency=low
* No-change rebuild for libbluetooth2 - libbluetooth3 transistion.
-- Steve Kowalik [EMAIL PROTECTED] Wed, 08 Oct 2008 14:16:16
+1100
** Changed in: totem (Ubuntu)
Status: Fix Committed = Fix Released
--
Rebuild for libbluetooth2 -
Yes, Baptiste Mille-Mathias tested it (as commented in bug 274950).
I'll sponsor it.
--
Update to version 1.1.0
https://bugs.launchpad.net/bugs/278694
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus-sendto in ubuntu.
--
after 4.12 release.
It should help with some sco headset issues.
* debian/control:
- Update different packages per upstream's recommendations.
- Update conflicts/replaces for earlier packages.
- Add a transitional bluez-utils package to help with the transition.
-- Mario
*** This bug is a duplicate of bug 274950 ***
https://bugs.launchpad.net/bugs/274950
I've marked this as a duplicate, because once all the tasks in bug
274950 are finished this is resolved. If it does end up to persist
AFTER all those tasks are closed, reopen this bug.
** This bug has been
Christoph:
Your issue about trusted devices should be addressed in bluez-gnome
1.8-0ubuntu1~ppa2 which was uploaded to the PPA this morning. It will only
affect newly paired devices however.
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug
because you are a direct subscriber
of the bug.
--
Mario Limonciello
[EMAIL PROTECTED]
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
desktop
and daemons
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a direct subscriber
of the bug.
--
Mario Limonciello
[EMAIL PROTECTED]
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received
are a direct subscriber
of the bug.
--
Mario Limonciello
[EMAIL PROTECTED]
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
desktop-bugs
Public bug reported:
Binary package hint: anyremote
This bug is directly related to bug 274950. If that bug is going to
happen, all of the tasks on this bug will need to be rebuilt. Some of
these will require source changes, others need just a changelog bump.
The bug is a work in progress.
I'm marking gnome-bluetooth won't fix. It's functionality is available
in obex-data-server and it didn't survive the transition. See bug
276353 for this.
** Changed in: gnome-bluetooth (Ubuntu)
Status: New = Won't Fix
** Description changed:
Binary package hint: anyremote
This
** Changed in: bluemon (Ubuntu)
Status: New = Fix Committed
--
Rebuild for libbluetooth2 - libbluetooth3 transition
https://bugs.launchpad.net/bugs/276343
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.
--
** Changed in: pilot-link (Ubuntu)
Status: New = Fix Committed
** Changed in: bluez-btsco (Ubuntu)
Status: New = Fix Committed
** Changed in: bluez-hcidump (Ubuntu)
Status: New = Fix Committed
** Changed in: gammu (Ubuntu)
Status: New = Fix Committed
** Changed in:
** Changed in: bluetooth-alsa (Ubuntu)
Status: New = Fix Committed
** Changed in: libpam-blue (Ubuntu)
Status: Fix Committed = New
** Changed in: libwiimote (Ubuntu)
Status: Fix Committed = New
--
Rebuild for libbluetooth2 - libbluetooth3 transition
OK: I've uploaded bluez_4.9-0ubuntu1~ppa3 to the PPA. This returns the
init script back to bluetooth.
Also: this switches the binary package names back to what we had before
(bluez-utils and bluez-audio). The stuff that was in bluez-gstreamer
and bluez-alsa is now part of bluez-audio. The
After some discussion in #ubuntu-motu, we've realize that we haven't
been in sync with Debian since about hoary. During Jaunty, we'll try to
get them to adapt our packaging scheme.
I've reverted the last commit and we are now using the packaging scheme
that upstream recommended. Additionally,
Pilot link's debdiff needs to be updated. Here's the better fix for it.
** Attachment added: pilot_link.debdiff
http://launchpadlibrarian.net/18094432/pilot_link.debdiff
--
Rebuild for libbluetooth2 - libbluetooth3 transition
https://bugs.launchpad.net/bugs/276343
You received this bug
Once pilot link is updated, evolution nicely compiles against it. It's
an indirect dependency of it.
** Changed in: libbtctl (Ubuntu)
Status: New = Fix Committed
** Attachment added: evolution.debdiff
http://launchpadlibrarian.net/18094663/evolution.debdiff
** Changed in: evolution
Also, once pilot link is updated, sylpheed works against it. Explicit
dependency.
** Attachment added: sylpheed.debdiff
http://launchpadlibrarian.net/18094732/sylpheed.debdiff
** Changed in: sylpheed (Ubuntu)
Status: New = Fix Committed
--
Rebuild for libbluetooth2 - libbluetooth3
Also, once pilot link is updated, multisync works against it. Explicit
dependency.
** Attachment added: multisync.debdiff
http://launchpadlibrarian.net/18095331/multisync.debdiff
** Changed in: multisync (Ubuntu)
Status: New = Fix Committed
--
Rebuild for libbluetooth2 -
** Description changed:
Binary package hint: anyremote
This bug is directly related to bug 274950. If that bug is going to
happen, all of the tasks on this bug will need to be rebuilt. Some of
these will require source changes, others need just a changelog bump.
The bug is a
One libbtctl is updated, gnome-phone-manager works against it. Explicit
dependency.
** Attachment added: gnome-phone-manager.debdiff
http://launchpadlibrarian.net/18095659/gnome-phone-manager.debdiff
** Changed in: gnome-phone-manager (Ubuntu)
Status: New = Fix Committed
**
Here's the debdiff for cwiid. Had to work around the API change.
** Attachment added: cwiid.debdiff
http://launchpadlibrarian.net/18095875/cwiid.debdiff
** Changed in: cwiid (Ubuntu)
Status: New = Fix Committed
--
Rebuild for libbluetooth2 - libbluetooth3 transition
Here's the debdiff for freej. Had to work around the API change.
** Attachment added: freej.debdiff
http://launchpadlibrarian.net/18095938/freej.debdiff
** Changed in: freej (Ubuntu)
Status: New = Fix Committed
** Description changed:
Binary package hint: anyremote
This bug
- libbluetooth3 transition
https://bugs.launchpad.net/bugs/276343
You received this bug notification because you are a direct subscriber
of the bug.
--
Mario Limonciello
[EMAIL PROTECTED]
--
Rebuild for libbluetooth2 - libbluetooth3 transition
https://bugs.launchpad.net/bugs/276343
You
** Description changed:
BlueZ 4.x resolves two regressions that are seen in the 3.x stack on
Intrepid.
Regressions solved
---
* Keyboards aren't able to pair in the UI.
- Reverting to an earlier release of bluez-utils is not a good solution as
a lot of bugs were fixed
Public bug reported:
Binary package hint: gdm
On a fully up to date copy of Intrepid (sept 29th), if Automatic login is
configured, the wrong set of sounds plays on startup.
The default Freedesktop theme is used instead.
Ubiquity OEM Config for intrepid both support setting up automatic
in: alsa-lib (Ubuntu)
Assignee: (unassigned) = Mario Limonciello (superm1)
Status: New = In Progress
** Description changed:
BlueZ 4.x resolves two regressions that are seen in the 3.x stack on
Intrepid.
Regressions solved
---
* Keyboards aren't able to pair in the UI
Hi Matti:
You need to setup gnome-user-share to do that. That behavior isn't in
bluez anymore as I understand. That's an interesting upgrade problem
regarding bluez-utils since they share the same init scripts but bluez-
utils isn't a package anymore. I'll think about it.
--
Look into
Matti:
Thanks for catching that case, the bluez 4.7-0ubuntu1~ppa7 version should
gracefully handle that.
--
Look into switching to bluez 4.x
https://bugs.launchpad.net/bugs/274950
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
** Description changed:
BlueZ 4.x resolves two regressions that are seen in the 3.x stack on
Intrepid.
Regressions solved
---
* Keyboards aren't able to pair in the UI.
- The combination of bluez-utils 3.36 and the btusb kernel module seems to
be causing problems when
** Description changed:
BlueZ 4.x resolves two regressions that are seen in the 3.x stack on
Intrepid.
Regressions solved
---
* Keyboards aren't able to pair in the UI.
-- The combination of bluez-utils 3.36 and the btusb kernel module seems to
be causing problems when
201 - 300 of 409 matches
Mail list logo
