@Mathieu,
Your solution looks good. Thanks for your effort.
BTW, the GRUB script is embedded in grub2-signed so only the maintainers of
grub2-signed can modify it.
We, downstream OEM projects, can not modify it because we need to support UEFI
Secure Boot.
--
You received this bug notification
GRUB should follow the UEFI's BootCurrent to find the root instead of
checking the existence of /.disk/info or /.disk/mini-info.
It looks like the followings. (pseudocode)
if ! search --disk --set=root UEFI:BootCurrent; then
if ! search --file --set=root /.disk/info; then
It seems the following commit in vivid is also needed for the better
support for trusty and utopic.
Author: Seth Forshee seth.fors...@canonical.com
AuthorDate: Fri Mar 20 11:06:52 2015 -0500
Commit: Andy Whitcroft a...@canonical.com
CommitDate: Fri Mar 27 10:44:38 2015 +
HID:
http://askubuntu.com/questions/613614/bluetooth-not-working-in-
ubuntu-15-04 also mentioned this firmware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454450
Title:
Bluetooth mouse laggy and
I noticed the following two lines.
[ 9442.157844] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will not
be loaded
[ 9442.157846] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-216f.hcd not
found
Did you try the firmware as
https://askubuntu.com/questions/617513/bluetooth-not-connecting-to-
devices-even-though-it-recognizes-them also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454450
Title:
Bluetooth mouse laggy
@cribari: What is the result?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454450
Title:
Bluetooth mouse laggy and erratic
To manage notifications about this bug go to:
https://tracker.debian.org/pkg/ifupdown has more than 200 bugs on
Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452238
Title:
Failed to upgrade system from 14.04
To manage notifications
apt-get dist-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452238
Title:
Failed to upgrade system from 14.04
To manage notifications about this bug go to:
If I upgrade ifupdown by `sudo apt-get install ifupdown` first and then
upgrade the whole system by `sudo apt-get dist-upgrade`, there is no
problem at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue is still reproducible on Ubuntu 14.04.
** Description changed:
software-center 5.2.5, Ubuntu 12.04
- software-center 5.6.0-0ubuntu2, Ubuntu 13.04
+ software-center 13.10-0ubuntu4.1, Ubuntu 14.04
When we search pcmanx-gtk2 by keyword 'pcman', we can not find pcmanx-gtk2 in
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/920377/+attachment/4390431/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920377
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/920377/+attachment/4390432/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920377
We still suffer from this issue for Ubuntu 14.04.
** Changed in: oem-priority
Status: Fix Released = Triaged
** Changed in: grub2 (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: grub2 (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: oem-priority/trusty
Regarding comment #49, the background will be repainted by Nautilus.
Trying to execute `nautilus -q` and you may see the tiled background.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382291
Title:
*** This bug is a duplicate of bug 1315221 ***
https://bugs.launchpad.net/bugs/1315221
** This bug has been marked a duplicate of bug 1315221
8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
connection/becomes unusable on Intel 7260
--
You received this bug notification
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431160
Title:
During the installation under UEFI mode, Could not open
\EFI\BOOT\fallback.efi: 14 shows after passed the BIOS
** Tags removed: kernel-bug-exists-upstream-3.19-rc7
** Tags added: kernel-bug-exists-upstream-3.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
Title:
Audio broken on 2015 XPS 13 (9343)
I have verified Linux kernel 3.16.0-31-generic and it does fix this
issue.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, there is some obscure BIOS/EC implementation that refuses to enable
I2S audio mode for Linux kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
Title:
Audio broken on 2015 XPS 13
I saw 0x10ec2088 in the latest kernel tree of
https://github.com/torvalds/linux/blob/master/sound/soc/codecs/rt286.c.
It should be included in the next v3.20 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@xnox,
If we do nothing for ubiquity-dm, the background issue will be introduced after
unity-settings-daemon is patched.
This is why the background issue is not mentioned in the beginning.
- pulling 'feh' from universe/graphics is bad if we can find out other
solution to fix the background
Since the change of http://bazaar.launchpad.net/~unity-settings-daemon-
team/unity-settings-daemon/trunk/revision/4020 and
http://bazaar.launchpad.net/~unity-settings-daemon-team/unity-settings-
daemon/14.04/revision/4020, autodetecting the scaling factor is
disabled, so many issues are hidden.
There is a patch for 0x10ec2088 but it is not included in
https://github.com/torvalds/linux/blob/v3.19/sound/soc/codecs/rt286.c.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
Title:
Audio
@redman,
My patch has been included in the upstream, and it is also in the Ubuntu 14.10.
It is also modified by other developers, so it has been a little different from
the one I made in Ubuntu 12.04.
I think the problem is that some rule is changed in UPower, but the mechanism
to detect
Yes, I hope it can be merged into v3.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
Title:
Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04
To manage notifications
@Sam,
I want to force the Linux kernel only to accept Windows 8.1 probing.
https://www.kernel.org/doc/Documentation/kernel-parameters.txt
It seems the BIOS will probe Windows 7 first and then Windows 8.1 no matter
if Windows 7 is probed or not.
And Linux kernel will accept any OS probing if it
I can see the following message when I installed Windows 8.1 in the
system storage, and then booted Ubuntu vivid live system by the USB
stick.
rt286 i2c-INT343A:00: Device with ID register 10ec2088 is not rt286
** Attachment added: dmesg.log
However 0x10ec2088 is not supported by the Linux kernel v3.19-rc7.
https://github.com/torvalds/linux/blob/v3.19-rc7/sound/soc/codecs/rt286.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
However it becomes worse.
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4312902/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I made a patch to skip checking ID register for v3.19-rc7.
** Patch added: 0001-ASoC-rt286-skip-checking-id-register-by-dmi.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4312901/+files/0001-ASoC-rt286-skip-checking-id-register-by-dmi.patch
--
You received
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided = High
** Changed in: oem-priority/trusty
Importance: Undecided = High
--
You
@redman,
My previous patch at comment #51 is mainly for bluetooth.
It is unrelated to your native-path:
/sys/devices/pci:00/:00:1d.2/usb8/8-1/8-1:1.1/0003:046D:C52F.0002.
Could you attach a screenshot for your icon?
--
You received this bug notification because you are a member of
I also found the similar error message in the kern.log of comment #17.
rt286 i2c-INT343A:00: Device with ID register is not rt286
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
After checking linux/sound/soc/codecs/rt286.c, the ID register must be
0x10ec0286.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413446
Title:
Audio broken on 2015 XPS 13 (9343) in I2S mode in
I just tested the mainline Linux kernel 3.19~rc7-vivid in Ubuntu 15.04
and the followings are the result.
$ dmesg -t | egrep (audio|rt286|INT343)
dmar: ACPI device INT3438:00 under DMAR at fed91000 as 00:13.0
Could you provide the output of `upower --dump`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input device batteries as batteries
To manage notifications about
@Bruce,
Bug #1286878 needs to be fixed with this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382291
Title:
Account creation during first boot of an OEM image needs to scale
based on
Regarding comment #18, the HiDPI support is in the xsettings plugin of
u-s-d/g-s-d, the only thing that ubiquity needs to do is waiting for the
xsettings plugin before ubiquity invokes any GTK/GDK function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
However the original mechanism for the background image doesn't support
HiDPI well, so some part of my patch is to use feh to fix the background
image problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I found there are some commits from the upstream and I am trying to merge those
commits with my patch.
However the work is not finished yet, so I put it in
lp:~fourdollars/unity-settings-daemon/add-hidpi-support temporarily.
--
You received this bug notification because you are a member of
I have verified this issue by the package in trusty-proposed, and it
does fix the issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have revised the patch to wait for the xsettings plugin of unity-
settings-daemon.
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Patch added: hidpi_support.patch
Could you provide the output of `sudo find /sys -name battery`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input device batteries as batteries
To manage
@gianluca,
It seems that you are using a preloaded Ubuntu system.
What is your hardware vendor and preloaded Ubuntu series?
Did you ever upgrade the system from Ubuntu 12.04 to Ubuntu 14.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@gianluca,
Could you also provide the list of `dkms status`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315221
Title:
8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
@gianluca,
If you are using the Linux kernel from Ubuntu 14.04, such as
3.13.0-{39,40,43}-generic, those DKMS packages should not affect your system.
You can remove them by `sudo apt-get purge oem-audio-hda-daily-lts-quantal
oem-wireless-bluetooth-intel-7260` if you think they are redundant.
** Branch unlinked: lp:~fourdollars/ubuntu/trusty/unity-greeter/1286878
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286878
Title:
Doesn't scale well on a hidpi display
To manage notifications
Public bug reported:
The video playback under HiDPI display with scale factor 2 doesn't work
well on Ubuntu 14.04.
It is easy to reproduce the problem on non-HiDPI display by the following
command.
`GDK_SCALE=2 totem /usr/share/example-content/Ubuntu_Free_Culture_Showcase/How\
fast.ogg`
There
** Bug watch added: GNOME Bug Tracker #724055
https://bugzilla.gnome.org/show_bug.cgi?id=724055
** Also affects: clutter-gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=724055
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
I found we still need to modify ubiquity for the HiDPI support.
** Patch added: ubiquity_hidpi.patch
https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4275936/+files/ubiquity_hidpi.patch
** Changed in: ubiquity (Ubuntu)
Status: Invalid = Confirmed
** Changed in:
I made this patch and it can fix the problem.
Please help to review it, thanks in advance.
** Patch added: hidpi_support.patch
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1286878/+attachment/4271918/+files/hidpi_support.patch
--
You received this bug notification because
I have verified systemd 204-5ubuntu20.9 and it does fix the problem.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339998
Hi,
I made a patch for unity-settings-daemon that can detect the HiDPI display and
change the scale factor automatically.
However the unity-greeter itself doesn't work well when the scale factor is 2.
The patch I made is for Bug #1382291 originally.
I have verified linux kernel 3.13.0-40.68 from trusty-proposed and it
does fix the audio playback too fast issue.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
A patch for unity-settings-daemon.
** Patch added: hidpi_display.patch
https://bugs.launchpad.net/oem-priority/+bug/1382291/+attachment/4254190/+files/hidpi_display.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There are some additional functions that those bitmaps relative
operations should follow up.
quote
Hi-DPI for developers
GTK+ makes hi-dpi work transparently in most places, but sometimes it
may be necessary to do some extra work for best results. Here are some
APIs to learn about the scale
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I found some information in unity-settings-
daemon-14.04.0+14.04.20140606/plugins/xsettings/gsd-xsettings-manager.c.
/* As we cannot rely on the X server giving us good DPI information, and
* that we don't want multi-monitor screens to have different DPIs (thus
* different text sizes), we'll
There is a criterion to detect HiDPI for gtk/gnome based UI.
GNOME currently enables hi-dpi support when the screen resolution is at
least 192 dpi and the screen height (in device pixels) is at least
1200. excerpt from https://wiki.gnome.org/HowDoI/HiDpi.
I made a little script at
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: oem-priority
Importance: Undecided = Critical
** Changed in: oem-priority/trusty
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386620
Title:
pcmanx-gtk2 daily build is moved to https://launchpad.net/~pcman-
bbs/+archive/dailybuild.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284447
Title:
middle click could not close the tab you
This issue doesn't exist on Ubuntu 14.10.
Please help to enable the rotation options on Ubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308515
Title:
black screen when enabling
I heard that some SSHD devices may cause this issue on current kernel of trusty.
`sudo hdparm -I /dev/sda | grep Model` can be used to get the disk model name.
Using the kernel parameter 'libata.noacpi=1' may be able to solve this problem.
--
You received this bug notification because you are a
I have verified kernel 3.13.0-37.64 from trusty-proposed and it does fix
the problem.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I found this issue is fixed in Linux kernel.
Please see
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6dda730e55f412a6dfb181cae6784822ba463847.
** Changed in: unity-settings-daemon
Status: Incomplete = Invalid
** Changed in: gnome-desktop3 (Ubuntu)
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367693
Title:
Can't select bluetooth input while on a2dp profile
To manage
** Summary changed:
- gnome-rr: Adjust the minimum brightness level when the maximum = 100.
+ gnome-rr: Normalize the minimum brightness level.
** Description changed:
- If the maximum brightness is equal to or bigger than 100, it has higher
- possibility that zero is off. So adjusting the
** Also affects: unity-settings-daemon
Importance: Undecided
Status: New
** Tags added: brightness trusty
** Tags added: broadwell haswell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
If the maximum brightness is equal to or bigger than 100, it has higher
- possibility that zero is off. So adjusting the minimum brightness to 1
- to avoid the problem.
+ possibility that zero is off. So adjusting the minimum brightness to avoid
the problem.
Quotes
I revised my patches to make the brightness minimum level more consistent than
previous implementation.
Now it needs to patch gnome-desktop3, gnome-settings-daemon and
unity-settings-daemon.
I will update my patches to the upstream bug afterward.
--
You received this bug notification because
** Bug watch added: GNOME Bug Tracker #734267
https://bugzilla.gnome.org/show_bug.cgi?id=734267
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=734267
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Description changed:
- According to RandR X protocol version 1.4.0, the minimum brightness can't be
0.
- 0 is used to turn off the backlight. The minimum brightness can only be 1.
+ Adjust the minimum brightness level when the maximum = 100.
+ Quotes from
** Description changed:
- Adjust the minimum brightness level when the maximum = 100.
+ If the maximum brightness is equal to or bigger than 100, it has higher
+ possibility that zero is off. So adjusting the minimum brightness to 1
+ to avoid the problem.
Quotes from
Public bug reported:
According to RandR X protocol version 1.4.0, the minimum brightness can't be 0.
0 is used to turn off the backlight. The minimum brightness can only be 1.
http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt
** Affects: gnome-desktop
Importance:
I have verified `jockey-text --auto-install` from precise-proposed and
it won't install bcmwl-kernel-source on linux-generic-lts-trusty.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I made a mistake.
I have verified `jockey-text --auto-install` from precise-proposed and it won't
install bcmwl-kernel-source on linux-generic-lts-saucy.
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member
@jofa,
This issue is about showing a wrong icon.
It is only about the identification of system or device batteries in UPower.
Please search other bugs or report a new bug for your problem.
BTW, Logitech wireless mouse seems to have some specific protocol to
detect the battery remaining power
In my case, I need to install linux-firmware-nonfree instead of
bcmwl-kernel-source to enable the WiFi.
http://paste.ubuntu.com/7320852/ is the output of dmesg, and it is why I know
linux-firmware-nonfree can fix my problem.
--
You received this bug notification because you are a member of
BTW, `ubuntu-drivers list` can also find linux-firmware-nonfree.
It looks like http://paste.ubuntu.com/7320967/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306928
Title:
Broadcom STA driver
I have tested nvidia-331 331.20-0ubuntu0.0.2 on precise and it works
fine.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255813
I have verified bluez 4.98-2ubuntu7.2 on precise and it works fine.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303819
$ sudo cat /var/log/upstart/cgmanager.log | sort -u
cgmanager: could not open cgroup file for [PID]
...
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
cgmanager:get_pid_cgroup_main: Could not determine the requestor cgroup
cgmanager: Invalid path
$ sudo cat /var/log/upstart/cgmanager.log | sort -u
cgmanager: could not open cgroup file for [PID]
...
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
cgmanager:get_pid_cgroup_main: Could not determine the requestor cgroup
cgmanager: Invalid path
@seb128,
I don't know if this issue has been reported upstream.
If not, I will try to report it and fix it in upstream.
@vdragon,
Please see 'Bug attachments' in the right to find 'BluetoothMenuAfter.png'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
Title:
bluetoothd crashs after resuming from Suspend to RAM.
To manage
I have verified by bluez 4.98-2ubuntu7.1 and it does fix the crash
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
Title:
bluetoothd crashs after resuming from Suspend to RAM.
To
Public bug reported:
* Reproducing Steps
1. Playing music through Bluetooth audio ouput.
2. Suspending the system.
3. Resuming the system.
4. Check Bluethooth menu's content
* Expected Result
The Bluetooth menu's content is not affected.
* Actual Result
The Bluetooth menu's content disappeared.
I uploaded two screenshots, i.e. BluetoothMenuBefore.png and
BluetoothMenuAfter.png.
You can compare them to see the problem.
** Attachment added: BluetoothMenuBefore.png
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+attachment/4071976/+files/BluetoothMenuBefore.png
--
You
** Description changed:
+ [Impact]
+
+ * It is very annoying to see Bluetooth menu's content disappeared after
suspending and resuming when playing music through Bluetooth audio output.
+ * The better user experience is still seeing Bluetooth menu's content.
+
+ [Test Case]
+
+ * Pairing
** Branch unlinked: lp:~fourdollars/ubuntu/precise/bluez/lp1300623
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
Title:
bluetoothd crashs after resuming from Suspend to RAM.
To manage
** Description changed:
+ [Impact]
+
+ * It is very annoying to see Bluetooth daemon crash after suspending and
resuming when playing music through Bluetooth audio output.
+ * The better user experience should be that Ubuntu will automatically
reconnect to the Bluetooth audio output and play
Public bug reported:
bluetoothd crashs after resuming from Suspend to RAM when it plays music
through Bluetooth audio output.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1300623/+attachment/4057371/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1300623/+attachment/4057369/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
Title:
apport information
** Tags added: apport-collected
** Description changed:
bluetoothd crashs after resuming from Suspend to RAM when it plays music
through Bluetooth audio output.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1300623/+attachment/4057367/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1300623/+attachment/4057368/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1300623/+attachment/4057366/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300623
801 - 900 of 1240 matches
Mail list logo
