https://code.launchpad.net/~hugh712/ubiquity/+git/ubiquity/+merge/380808
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868701
Title:
need to implement a reboot mechanism before oobe
To manage
Public bug reported:
Some oem projects preload workaround(configuration/dkms/firmware) in
the image, and it need a reboot to take effect in OOBE(oem-config)
stage, but current ubiquity doesn't support this feature..
https://code.launchpad.net/~hugh712/ubiquity/+git/ubiquity/+merge/380808
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338363/+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/1867909
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338364/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338367/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338366/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338371/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338362/+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/1867909
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338368/+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/1867909
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338370/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338360/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338369/+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-v.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338365/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "EtcDefaultGrub.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338361/+files/EtcDefaultGrub.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected focal
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown on the screen.
But since 20.04, due to the using of
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown on the screen.
But since 20.04, due to the using of
Public bug reported:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown on the screen.
But since 20.04, due to the using of
even in build ubiquity it will failed in :
(run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon
theme.
This may indicate that pixbuf loaders or the mime database could not be found.
Exception in GTK frontend (invoking crash handler):
Traceback (most recent call last):
even in building ubiquity it will fail in :
(run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon
theme.
This may indicate that pixbuf loaders or the mime database could not be found.
Exception in GTK frontend (invoking crash handler):
Traceback (most recent call last):
" lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
"apt-cache policy gir1.2-rsvg-2.0
gir1.2-rsvg-2.0:
Installed: 2.48.0-1
Candidate: 2.48.0-1
Version table:
*** 2.48.0-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64
Public bug reported:
[Summary]
Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to
2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.
[Steps to reproduce]
1. Boot with OEM mode,
2. Finish the 1st stage
3. Reboot
4. Boot into OOBE(oem-config)
** Changed in: oem-priority
Status: Triaged => Fix Released
** Changed in: oem-priority/bionic
Status: Triaged => 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/1853584
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[SRU]Not able to adjust Audio input UI volume after
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a LG Thin
Client[0], can fix this issue
[0] https://www.lg.com/global/business/monitor/monitor-products/lg-
CK500W
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp Small Form
Factor PC[0], can fix this issue
[0] https://www8.hp.com/us/en/desktops/product-details/21353680
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp desktop
mini machine[0], can fix this issue
[0] http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=c06339658
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a built-in
speaker/microphone laptop[0], still works well, didn't find any
Regression potential.
[0] https://support.hp.com/ro-en/document/c05994943
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
[ Impact ]
Not able to adjust Audio input UI volume if this device doesn't have a
internal mic, the volume bar will be gray.
[ Test Case ]
1. Boot ubuntu without any external headset connected.
2. Launch gnome-control-center and switch to Sound->Input
hanged in: oem-priority/bionic
Importance: Undecided => Critical
** Changed in: oem-priority/bionic
Status: New => Triaged
** Changed in: oem-priority/bionic
Assignee: (unassigned) => hugh chao (hugh712)
--
You received this bug notification because you are a member of Ubu
** Description changed:
[ Impact ]
Not able to adjust Audio input UI volume if this device doesn't have a
internal mic, the volume bar will be gray.
[ Test Case ]
1. Boot ubuntu without any external headset connected.
2. Launch gnome-control-center and switch to Sound->Input
** Description changed:
[ Impact ]
Not able to adjust Audio input UI volume if this device doesn't have a
internal mic, the volume bar will be gray.
[ Test Case ]
1. Boot ubuntu without any external headset connected.
2. Launch gnome-control-center and switch to Sound->Input
** Tags added: oem-priority stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851773
Title:
[SRU] Need rtl8821ce in Bionic
To manage notifications about this bug go to:
** Patch added: "check_input_treeview.patch"
https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+attachment/5315268/+files/check_input_treeview.patch
** Summary changed:
- [18.04]Not able to adjust Audio input UI volume after connecting headset
+ [SRU]Not able to adjust Audio input
** Description changed:
[ Impact ]
Not able to adjust Audio input UI volume if this device doesn't have a
internal mic, the volume bar will be gray.
[ Test Case ]
1. Boot ubuntu without any external headset connected.
2. Launch gnome-control-center and switch to Sound->Input
tried "HP ProOne 400 G5 All-in-One Business PC"[0] with this 8821ce dkms,
works well, there isn't any issue on this machine
[0] https://support.hp.com/in-en/document/c06409794#AbT11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after connecting
headset
To manage notifications about this bug
** Description changed:
[ Impact ]
Not able to adjust Audio input UI volume if this device doesn't have a
internal mic, the volume bar will be gray.
[ Test Case ]
- 1. Boot ubuntu without any external microphone connected.
+ 1. Boot ubuntu without any external headset connected.
** Description changed:
+ [ Impact ]
+
+ Not able to adjust Audio input UI volume if this device doesn't have a
+ internal mic, the volume bar will be gray.
+
+ [ Test Case ]
+
+ 1. Boot ubuntu without any external microphone connected.
+ 2. Launch gnome-control-center and switch to
** Description changed:
Summary:Not able to adjust Audio input UI volume, it's gray
Steps to reproduce:
1. Plug 3 ring earphone with mic to appropriate jack
Expected result:
System can be recording audio from external mic
Actual result:
Not able to adjust Audio input UI
** Tags added: originate-from-1806835
** Tags added: stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after connecting
headset
@Sebastien,
Would you please help to backport there two commits in #15, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after
@Robert,
Is there any chance you can review this mp in #15? many thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/641
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after connecting
@Robert,
Is this the right branch?
https://gitlab.gnome.org/GNOME/gnome-control-center/tree/gnome-3-28/panels/sound
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to
@Sebastien,
No, it's not from upstream, due to the code is quite different from
upstream.
If there is only one input device with only one input port, and this
input port is active_port, e.g. there is no internal mic, just a mic
jack on the machine, this issue will happen.
For this kind of
@Sebastien,
please take a look of this patch
** Patch added: "check_input_treeview.patch"
https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+attachment/5307971/+files/check_input_treeview.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Sebastien
Yes, What I meant was gnome-control-center
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after connecting
headset
To
pavucontrol works good, I will try to backport this package to bionic,
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after
** Summary changed:
- [18.04]Not able to adjust Audio input UI volume after connecting headset in
"input tab"
+ [18.04]Not able to adjust Audio input UI volume after connecting headset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1. Still can reproduce this issue in 18.04.3
2. can not reproduce this issue in 19.04 and 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI
Public bug reported:
Summary:Not able to adjust Audio input UI volume, it's gray
Steps to reproduce:
1. Plug 3 ring earphone with mic to appropriate jack
Expected result:
System can be recording audio from external mic
Actual result:
Not able to adjust Audio input UI volume, it's gray, and no
sorry I forgot to attach the file...
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1804786/+attachment/5267033/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Doug,
please find attached the "lspcik.txt",
and I didn't see anything on terminal after running below command:
yelp help:gnome-help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804786
Title:
@Daniel,
Sure I will provide the log tomorrow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804786
Title:
Garbage occurred when Playing the video in the Ubuntu Desktop Guide
To manage
haven't tried cosmic but I did try disco, still can reproduce 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/1772811
Title:
different behaviors for switch display mode between xenial and
seems not only one oem platform can reproduced this issue due to Bug
539477
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772811
Title:
different behaviors for switch display mode between xenial
** Tags added: stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772811
Title:
different behaviors for switch display mode between xenial and bionic
To manage notifications about this bug go
Public bug reported:
Garbage occurred when Playing the video in the Ubuntu Desktop Guide.
Reproduce step
1. Ubuntu 18.04.1.
2. ubuntu-docs 18.04.4
3. Playing the video(Launch applications) from Help-->Getting started with
GNOME.
4. Garbage occurred after the video repeat about 3 times==> issue.
upload video which this issue was happening
** Attachment added: "O1684740_Garbage.mp4"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1804786/+attachment/5215566/+files/O1684740_Garbage.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello Bob,
I am sorry that reported an unrelated problem here, I can't delete them after I
realised my stupied behavior.
I am so sorry.
Best wishes,
Chao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "ubuntu_input_method_bug.PNG"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1802900/+attachment/5211825/+files/ubuntu_input_method_bug.PNG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello guys,
I meet a bug when using input method, I drag the input method dialog onto the
top bar of GNOME, and then I can't drag it anymore.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
Hello guys,
I meet a bug when using input method, I drag the input method dialog onto the
top bar of GNOME, and then I can't drag it anymore; please see the attached
screenshot ubuntu_input_method_bug.PNG
Sorry that I report a bug here, but I really can't find a place to
report a bug, I am
** Also affects: python-troveclient
Importance: Undecided
Status: New
** Changed in: python-troveclient
Importance: Undecided => Medium
** Changed in: python-troveclient
Status: New => In Progress
** Changed in: python-troveclient
Assignee: (unassigned) =>
To me,
1. This is for sure to go. Noto serif has large glyph coverage and better font
(hinting) quality. I think it should go first in the alias.
2. Some old software like adobe flash / youtube (flash must die...) has
hard-coded font name in the program. I recall UMing and UKai do some tweaks to
Hinting options are rather font dependent. The old free fonts for CJK
usually do not have proper hinting embedded so certain specific tweaks
(ex. auto hint) are needed to avoid faint strokes. The draw backs are
the spaces between strokes may be significantly changed for small size
glyphs. It would
Would that be a hinting configuration issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581160
Title:
Switch to Noto Sans as default font for Japanese and/or Korean?
To manage notifications
It was fixed in evince 3.18.2. Tested with xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472792
Title:
evince does not open with broadway backend
To manage notifications about this bug go
waiting for the reporter to add the name of package,
change the status to incomplete.
** Changed in: ubuntu
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/1172494
Bugs without a package
Sometimes bugs will be reported just using the "Ubuntu" package. This is not
the best place for the bug though and we should encourage bug reporters to
report the bug against the correct package by pointing them at some
documentation. Keep in mind PKGNAME is a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
Thank you for your suggestion. However, the changes you are requesting
aren't really a bug and require more discussion, which should be done on
an appropriate mailing list or forum.
http://www.ubuntu.com/support/community/mailinglists might be a good
start for determining which mailing list to
Workaround is still needed and works on Xenial 16.04 for my MBA 6,2
(2013).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245081
Title:
macbook keyboard layout maps the tilde key to something else
I re-do the update again and libreoffice-help-ja 1:3.5.7-0ubuntu12 is
installed correctly. It seems to be either a broken mirror or even a
broken package according to the log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Update manager failed to install this package.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libreoffice-help-ja 1:3.5.7-0ubuntu10
ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion:
My understand is that Noto Sans is not the default fonts for Japanese locale
yet. This problem
has been reported. Please refer to #1581160.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/491157
This bug is still present in lubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1428967
Title:
Inkscape0.91 crashes under interface using Chinese/Taiwan(zh-tw)
To manage notifications
** Tags added: xenial
** Package changed: gtk+3.0 (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472792
Title:
evince does not open with broadway backend
To manage
For Noto Sans font, it's just for the Sans Serif family. Still for Serif
fonts, we still rely on other local font sets. The fallback settings in
those fontconfig files should still be needed.
Japanese uses Chinese characters but with some variates. That's why a
local font is preferred. Noto Sans
On 2016-05-04, Gunnar Hjalmarsson (gunnarhj) wrote:
> Yeah, indeed. And it indicates that the bug resides in the "super" OTC file.
I thought the problem is on google-chrome as Firefox and other applications
handles super OTC well?
--
You received this bug notification because you are a member
** Attachment added: "ja_JP.UTF-8"
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1468027/+attachment/4616866/+files/Screenshot_xenial_firefox_jp.png
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-meta in
> May I ask: Is "Regular" picked up first with a ja_JP or zh_TW
> locale?
Yes, (only tested with live env) according to fc-match "Regular" is picked up
over "DemiLight" in both zh_TW and zh_CN. TakaoPGothic is the default for ja_JP.
However, for Firefox, this hack in
** Attachment added: "zh_CN.UTF-8"
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1468027/+attachment/4616864/+files/Screenshot_xenial_firefox_sc.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "zh_TW.UTF-8"
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1468027/+attachment/4616865/+files/Screenshot_xenial_firefox_tc.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From the latest 16.04 beta2 release, I tested the font display with
firefox. Still according to the inspection tool, Noto Sans DemiLight is
picked up first for TC and JP contents. (EN locale in live env.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> BTW, may this be a related bug?
> https://bugs.launchpad.net/ubuntu-translations/+bug/1540063
It looks like some (traditional?) Chinese font (kai?) is picked up instead of
the "Takao Pゴシック" Japanese font requested. Due to the lack of the glyphs, it's
further fallbacked to other(?) "ゴシック"
** Also affects: ubuntu
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/1362044
Title:
在Dash中输入中文，输入的文字提示条位置不正确
To manage notifications about this bug go
Same problem found for fcitx in ubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454200
Title:
qimpanel window position wrong on high-dpi screen
To manage notifications about this bug
For the prepend list, separated conf. for TC and SC is needed as
different localized glyphs now supported by Noto sans. It would be nice
if suitable "real" mono space EN fonts are prepended.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am trying to enable subpixel rendering on poppler and I found my
rendering result is suboptimal. After gdbing into cairo, I am surprise
that cairo is still using the legacy filter as the "default". To the
the situation even worse, cairo removed the interfaces to set the
lcdfiler
I am trying to enable subpixel rendering on poppler and I found my
rendering result is suboptimal. After gdbing into cairo, I am surprise
that cairo is still using the legacy filter as the "default". To the
the situation even worse, cairo removed the interfaces to set the
lcdfiler
Comparing with WenQuanYi Micro Hei, Noto Sans is surely a better choice
to me. For low-DPI display, a proper hinting configuration is needed.
(if not using embedded bitmap font) This should not be a show stopper
here?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Wouldn't it be better to patch file-roller to support encoding settings?
Otherwise it still breaks if you get zipped file with different encoding
from the default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that "legacy turbo" patch doesn't work for me either.
Using that patch with ck-kernel, my system still freezes under high CPU-
load frequently. The last kernel works for me is the 3.18.x branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is from one of my machine running LUbuntu:
$ export |grep LANG
declare -x LANG=en_US.UTF-8
$ export |grep LC
declare -x LC_ADDRESS=en_US.UTF-8
declare -x LC_IDENTIFICATION=en_US.UTF-8
declare -x LC_MEASUREMENT=en_US.UTF-8
declare -x LC_MONETARY=en_US.UTF-8
declare -x LC_NAME=en_US.UTF-8
Dear @Nobuto,
I appreciate the patch work very much, but it simply doesn't fit my use case.
Quite frequently, I get
zip files with CJK file names from zh_CN and ja_JP. (my environment is either
zh_TW or en_US, the
later which is for office desktop PC) Changing LC_CTYPE to something other than
Well, without this trick, the filenames could be recovered with
'convmv'. But with this trick, it would be scrambled further... Still I
personally prefer an auto-detect plus this fallback or an option in the
GUI, like file-roller.
--
You received this bug notification because you are a member
It would be nice to have some auto-detect mechanism on top of this
locale fallback. For my personal case, most zip files that need to
specify the encoding is not the same as my corresponding locale setting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm the same issue still exist on wine 1.4 on Ubuntu 12.04.5
LST. This causes utau external program file processing failures as the
result wav files need to be combined with copy /b.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
201 - 300 of 353 matches
Mail list logo
