I can not reproduce this issue on wily right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480138
Title:
The background image becomes titled for a while during the logout
process.
To manage
No, it is not for wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
To manage notifications about this bug go to:
https://bugs.laun
BTW, no one verified the patch for wily on the real device and the patch
is just accepted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded mode
@Bin,
Could you help to change the status from "Fix Released" of this bug?
It confuses people and I don't have the permission to change it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Titl
The original modemmanager 1.4.10-1 can work for Sierra DW5809e (EM7305).
The mobile broadband connection behavior on wily works differently from trusty.
Trusty uses wwan0 and it needs the gateway for some ISPs.
Wily setups ppp0 and it doesn't need the gateway.
--
You received this bug notificatio
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: oem-priority
Status: Incomplete => In Progress
** Changed in: oem-priority/trusty
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
: New
** Changed in: libmbim (Ubuntu)
Status: New => Confirmed
** Changed in: libmbim (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: libmbim (Ubuntu Trusty)
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
** Changed in: libmbim (Ubuntu)
Assignee: (u
@Bin,
That is the PIN number. Every SIM card has its own PIN number.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
To manage notific
** Tags added: trusty wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
To manage notifications about this bug go to:
https://bugs.l
Created attachment 118426
Increase the retry interval to 5 seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
To manage notificat
Created attachment 118427
Increase the retry interval to 5 seconds.
Sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded modems
To manage no
I have verified the patch of comment #11.
It works fine and is better than the previous one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve probing for Dell branded mo
Yes, I can help to verify it once I have the ISO image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097570
Title:
grub2-signed can not find the right device when there are two
filesystems conta
In fact, I have tried
https://github.com/rhinstaller/efibootmgr/commit/301c0628f7fa7333791d2b5d79eb8e02fc848ee7
and it doesn't work for this issue.
I think my fix is the right way to fix this problem so I also made a pull
request at https://github.com/rhinstaller/efibootmgr/pull/32 about this.
I
Public bug reported:
Please sync gcin 2.7.2+dfsg-1 (universe) from Debian unstable (main)
All changelog entries:
gcin (2.7.2+dfsg-1) unstable; urgency=low
[ Yao Wei (魏銘廷) ]
* Reupload to Debian. (Closes: #658449)
* Imported Upstream version 2.7.2
* Removed Dayi input method for DFSG com
** Changed in: oem-priority
Status: Triaged => Fix Released
** Changed in: oem-priority/trusty
Status: In Progress => Fix Released
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-vivid
** Tags added: verification-failed-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456443
Title:
Skip eMMC device's boot0, boot1 and rpmb partitions
** Tags removed: verification-done-vivid
** Tags added: verification-failed-vivid
** Tags added: verification-done-wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502772
Title:
Linux kernel in
** No longer affects: debian-installer (Ubuntu Vivid)
** Tags removed: verification-failed-vivid vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502772
Title:
Linux kernel in Ubuntu doesn't pr
** No longer affects: partman-base (Ubuntu Vivid)
** Tags removed: verification-failed-vivid
** Tags removed: vivid
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456443
Title:
I have verified gnome-desktop3/3.8.4-0ubuntu3.2 by trusty-proposed and
it does fix this 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.
https://bugs.launchpa
It is not necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381625
Title:
Adjust brightness to lowest value caused screen whole black
To manage notifications about this bug go to:
https://b
There is no such issue for trusty, vivid, wily and xenial.
We only need to fix this issue for precise.
** Changed in: live-build (Ubuntu)
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
** Tags added: precise
--
You received this bug notification because you are a member of Ubu
** Changed in: live-build (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961166
Title:
lb_binary_disk doesn't check compression of the initramfs
To man
fi
--
1.9.1
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => In Progress
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) =>
e it can be lzma and bzip2, build process will fail if
one of those two compression methods are used. This is fixed upstream by
commits 1940 and 2105. Patch is attached.
** Changed in: live-build (Ubuntu)
Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)
** Changed in: oem-priority
** Description changed:
[Impact]
* Canonical OEM IBS still uses Ubuntu 12.04 to build Ubuntu OEM images for
trusty, wily and the following xenial.
* Without this fix, Canonical OEM IBS can not generate Ubuntu OEM
images for wily and xenial.
[Test Case]
* Please use
In xenial, 71ubuntu1 overwrote my patch in 62ubuntu3.
** Changed in: partman-efi (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512589
Title:
partman-efi
** Changed in: oem-priority/trusty
Status: In Progress => Fix Released
** Changed in: oem-priority
Status: In Progress => Fix Released
** Changed in: gnome-desktop3 (Ubuntu Trusty)
Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)
** Changed in: unity-settin
I have verified https://launchpad.net/ubuntu/+source/live-
build/3.0~a24-1ubuntu32.7 and it has no problem for live-build.tar.xz.
** Attachment added: "live-build.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/961166/+attachment/4572020/+files/live-build.tar.xz
** Tags remo
** Changed in: oem-priority/precise
Status: New => Fix Released
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961166
Title:
lb_
I have verified
https://launchpad.net/ubuntu/+source/partman-efi/25ubuntu6.14.04.2 and it does
fix this issue.
Please also upgrade partman-efi in ubiquity for trusty.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a m
I have verified https://launchpad.net/ubuntu/+source/partman-
efi/62ubuntu2.1 and it does fix this 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.
https://bu
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.
https://bugs.lau
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 selec
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
https://githu
** 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.
https://bugs.launchpad.net/bugs
** 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:
There are some additional functions that those bitmaps relative
operations should follow up.
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 factor:
g
** 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.
https://bugs.launchpad.net/bugs
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 h
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.
https://bugs.launchpad.net/
** 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) in
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 su
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.
https://bugs.launchpad.net/
@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 res
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 this
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
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 Ubun
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
Title:
@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 Ubuntu
** 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 rec
@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 Ubu
@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
connection/
@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.
`un
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 Ubun
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: ubiq
** 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 ab
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 of
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 y
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 t
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.
https://bugs.launchpad.ne
@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
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"
https://bugs.launchpad.net/ubuntu/+source/linux
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
Titl
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 ab
@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 Blueto
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 br
@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 iss
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.
--
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 (93
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.
https://bugs.launch
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 notificat
The fonts that follow Taiwan standard are fonts-arphic-uming,
fonts-arphic-ukai, fonts-moe-standard-kai, fonts-moe-standard-song
fonts-cns11643-kai and fonts-cns11643-sung.
I think we should avoid using other fonts in 69-language-selector-zh-tw.conf.
For more information, please see the followin
@zerng07: I think CJKUnifonts does want to follow Taiwan's standard (CNS11643),
China's standard (GB18030), and other countries' standard also.
However this project seema to stop the development since 2010
(http://www.freedesktop.org/wiki/Software/CJKUnifonts/).
CJKUnifonts is a truely open sour
BTW, there are other fonts: fonts-cwtex-* following Taiwan standard and
licensed by GPL-2+.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173571
Title:
please change wenquanyi micro hei back with 6
** 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
** 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 notif
** 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 no
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 manag
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 Bl
@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 su
@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 info
** 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
http://cgit.freedesktop.org/xorg
** 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
http://cgit.freedeskt
** 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.
https://bugs.launchpad.net/bugs/1340
** 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 yo
** 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 a
** 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 mini
$ 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 /run/cgmanager/fs/none,n
** Patch added: "0001-Add-subsystem-ID-support-for-LP-1255813.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1255813/+attachment/4028073/+files/0001-Add-subsystem-ID-support-for-LP-1255813.patch
--
You received this bug notification because you are a member
I suggest to use the fonts as the following order.
Ubuntu, AR PL, cwTeX, MOE, and then CNS11643.
Pro: Better looking in English and better following of Taiwan standard.
Con: The programs that don't have font-config suppprt will be not able to see
Chinese characters.
If we find the programs don't s
How about to find another English font to replace Ubuntu font in serif
style?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173571
Title:
please change wenquanyi micro hei back with 69-language-sel
Yes, it is better to use Western serif font listed before AR PL UMing for serif
font family if we want to have a better looking for Western characters.
In short, my point is to use those fonts in better compliance with Taiwan's
standard instead of those are not.
I am not willing to have better Ch
There is another way to fix this problem.
That is make another Droid Sans Taiwanese font just like the way that Droid
Sans Japanese font does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173571
Ti
@Eduard (e-valchukovski) :
Would you mind to open another bug and provide more information of your
bluetooth device?
--
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 in
701 - 800 of 1572 matches
Mail list logo
