** Also affects: gnome-shell (Ubuntu Kinetic)
Importance: Undecided
Assignee: Yao Wei (medicalwei)
Status: In Progress
** Also affects: gnome-shell (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1945298
Title:
To support goodix fp device [27C6:63BC]
To manage
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1873184
Title:
Wired and wireless connection details
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1905825
Title:
[SRU] Disable CRTCs when system becomes headless
To
Regaring comment #26, I am using PX UH-1.2MX HDMI 2.0 certified Premium
High Speed cable so the cable's quality should not be a problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
My monitor is EDID 1.3 and it has the same problem.
edid-decode (hex):
00 ff ff ff ff ff ff 00 41 0c 8f c1 bd 07 00 00
08 1d 01 03 80 3c 22 78 2a 67 a1 a5 55 4d a2 27
0e 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40
81 c0 01 01 01 01 4d d0 00 a0 f0 70 3e 80 30 20
35 00 55 50 21 00 00 1a a3 66
It doesn't look like https://gitlab.gnome.org/GNOME/mutter/issues/728.
It is about the hardware limitation that DELL DOCK - WD19 130W only supports
two external Full HD at the same time.
However mutter doesn't know the hardware limitation.
I guest mutter will try to set up external Ultra HD and
Public bug reported:
[Summary] Join Displays failed when using two external monitor of one
Full HD and one Ultra HD
[Reproduce Steps]
1. Boot into the desktop environment with DELL DOCK - WD19 130W [1].
2. Connect one Ultra HD (3840x2160) external monitor and one Full HD
(1920x1080) external
https://gitlab.gnome.org/GNOME/mutter/issues/281 involved the fixes for
mutter and gnome-shell so
https://gitlab.gnome.org/GNOME/mutter/merge_requests/213 and
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/208 are both
needed to fix this issue.
--
You received this bug notification
** Patch added: "mutter_3.28.3-2~ubuntu18.04.2.debdiff"
https://bugs.launchpad.net/oem-priority/+bug/1730211/+attachment/5201433/+files/mutter_3.28.3-2~ubuntu18.04.2.debdiff
** Also affects: oem-priority/bionic
Importance: Undecided
Status: New
--
You received this bug
$ git tag --contains 85284acb000ddc70afcf716b6c198b4b5bf5741e
3.29.92
3.30.0
3.30.1
Cosmic is using 3.30.1-1 so it has contained the commit mentioned in
comment #8.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1760106
Title:
FFe: Enable configuring resume offset via
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715602
Title:
ubiquity-dm / Install Ubuntu - Power
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-bug-1769562
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1762385
Title:
dell_wmi:
@Taihsiang,
Have you checked Ubuntu 16.04.0 and 16.04.1?
If not, could you check if they have the similar issues?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1766890
Title:
Public bug reported:
Please check the attached screenshots.
Compare the difference between AudioMute.png and AudioOn.png.
** Affects: adwaita-icon-theme (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic
** Attachment added: "AudioMute.png"
Public bug reported:
Removing "Startup Applications" in "Ubuntu Software" makes the system
unable to launch GDM
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session-bin 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
*** This bug is a duplicate of bug 1617505 ***
https://bugs.launchpad.net/bugs/1617505
** This bug has been marked a duplicate of bug 1617505
gcin didnt work in gnome-terminal after updating ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: oem-priority/trusty
Status: Fix Committed => Fix Released
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Tags removed: verification-done
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1480217
Title:
Nautilus background handling screwed when
I have verified nautilus/1:3.10.1-0ubuntu9.11 and it works.
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: oem-priority
Status: New => Fix Committed
** Changed in: oem-priority/trusty
Status: New => Fix Committed
--
You received this bug
** 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
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
@seb128,
GNOME doesn't use the Unity launcher so GNOME has no problem at all.
This issue is for Unity desktop environment only.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Tags added: trusty vivid wily
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1480217
Title:
Nautilus transparent background becomes a mess when changing scaling
factor.
To
Public bug reported:
Ubuntu 14.04.2
Reproducible Steps:
1. Login Unity desktop environment.
2. Change the scale factor to 2 in Displays of Settings.
3. Create some files and folders on the desktop.
4. Right click to select Organize Desktop by Name.
Expected Result:
* The organized files and
** Attachment added: OrganizeDesktop.png
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1480143/+attachment/4436765/+files/OrganizeDesktop.png
** Tags added: hidpi
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus
Public bug reported:
Ubuntu 14.04.2
Reproducible Steps:
1. Login to Unity desktop environment.
2. Change the scale factor to 2 in Displays of System Settings.
3. Logout and login again
3. Change the scale factor to 1 in Displays of System Settings.
Expected Result:
* The background will work
Public bug reported:
Ubuntu 14.04.2
Reproducible Steps:
1. Login Unity desktop environment.
2. Change the scale factor to 2 in Displays of System Settings.
3. Open any image by eog with 1:1 mode on HiDPI display, such Dell new XPS
(2015) 13 9343.
Expected Result:
* The image won't become
** Changed in: ubiquity (Ubuntu)
Status: Invalid = Confirmed
** Changed in: ubiquity (Ubuntu Trusty)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu.
@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
@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
Could you provide the output of `upower --dump`?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input device batteries as batteries
To
Could you provide the output of `sudo find /sys -name battery`?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input device batteries
** 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
Desktop Bugs, which is subscribed to systemd in 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: 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
Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu.
** 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
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:
@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
@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
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
I have tested upower 0.9.15-3git1ubuntu0.1 on precise with linux kernel 3.2 and
3.5, and they both work fine.
I have tested upower 0.9.20-1ubuntu0.1 on raring with linux kernel 3.8 and it
works fine.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this
** Tags added: quantal raring
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input device batteries as batteries
To manage
Ritesh Khadgaray,
Your patch has been reverted because of Bug #1236752.
So you need to generate the patch based on gnome-settings-daemon
(3.4.2-0ubuntu0.6.4) again.
You can get the Debian source package by `dget -x -u
Hi,
I think the fix in gnome-settings-daemon 3.4.2-0ubuntu0.6.3 is OK except
we should not change the following default value.
+ key name=default-monitors-setup
enum=org.gnome.settings-daemon.GsdXrandrBootBehaviour
+- default'do-nothing'/default
++ default'follow-lid'/default
*** This bug is a duplicate of bug 1153488 ***
https://bugs.launchpad.net/bugs/1153488
** This bug is no longer a duplicate of bug 1066208
power indicator shows a mouse battery as a laptop battery
** This bug has been marked a duplicate of bug 1153488
Treats bluetooth input device
** Description changed:
+ [Impact]
+
+ * There are many Bluetooth devices with battery information inside.
+ When they are treated as system battery, it will make the system
+ poweroff/suspend/hibernate when some Bluetooth device is with critical
+ low battery. It is a very annoying behavior
** Description changed:
[Impact]
* There are many Bluetooth devices with battery information inside.
When they are treated as system battery, it will make the system
poweroff/suspend/hibernate when some Bluetooth device has critical low
battery. It is a very annoying behavior for
** Changed in: gnome-power-manager (Ubuntu Precise)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input
** No longer affects: oem-priority
** No longer affects: oem-priority/precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1041032
Title:
An error occurred Location not found
gnome-settings-daemon 3.4.2-0ubuntu0.6.3 works fine on precise.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Hi,
This bug is reported against Ubuntu 12.04.
Could we also apply this patch on Ubuntu 12.04? (Maybe on 12.10 and 13.04 too?)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
$ grep -r . /sys/class/power_supply/*hid*
/sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/type:Battery
export LC_ALL=C
ls -lR /sys/class/power_supply/* /tmp/out.txt 21
echo /tmp/out.txt
ls -lR /sys/class/bluetooth/* /tmp/out.txt 21
echo /tmp/out.txt
udevadm info --export-db /tmp/out.txt 21
echo /tmp/out.txt
grep -r .
`grep -r . /sys/class/power_supply/*hid*` seems to run forever.
Is there other command that can run sooner?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
ls -lR /sys/class/power_supply/*hid*
lrwxrwxrwx 1 root root 0 Sep 4 13:32
/sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery -
../../devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/0005:05AC:0239.0003/power_supply/hid-10:9A:DD:96:DA:0D-battery
lrwxrwxrwx 1 root root
$ ls -lR
/sys/class/power_supply/../../devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/0005:05AC:0239.0003/power_supply/hid-10:9A:DD:96:DA:0D-battery
@pitti,
I can run `grep -r . /sys/class/power_supply/*hid*` in Ubuntu 13.04 without any
problem.
But when I run it in Ubuntu 12.04, it shows some messages like grep: warning:
...: recursive directory loop.
It seems to be another bug of grep in Ubuntu 12.04. :P
--
You received this bug
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upower (Ubuntu)
Status: New = Confirmed
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
I revised the previous patch to prevent from potential memory leak.
** Patch added: 03-detect-bluetooth-keyboard-mouse.patch
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1153488/+attachment/3757908/+files/03-detect-bluetooth-keyboard-mouse.patch
--
You received this bug
Hi,
I made a patch to fix this issue.
The root cause is in upower instead of gnome-power-manager.
Please help to review it.
** Patch added: 02-try-to-work-out-if-the-device-is-powering-the-system.patch
However the battery type is still recognized as a laptop battery.
So I made another patch to fix the battery type issue.
** Patch added: 03-detect-bluetooth-keyboard-mouse.patch
I made some Debian packages at
http://people.canonical.com/~sylee/1153488/ .
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
System reads Apple Magic
Reproduce steps:
1. Remove gstreamer0.10-plugins-ugly if it is installed.
2. Download Wildlife.wmv from
http://archive.org/details/Windows7WildlifeSampleVideo
3. Open Wildlife.wmv by totem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Revised reproduce steps:
1. Remove gstreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly if they are
installed.
2. Download Wildlife.wmv from
http://archive.org/details/Windows7WildlifeSampleVideo
3. Open Wildlife.wmv by totem.
** Description changed:
Ubuntu: 12.04
totem: 3.0.1-0ubuntu21
Hi Iain,
I don't know why my previous patch doesn't work now.
But I have another idea to fix this problem.
The idea is to add a new signal in bacon, such as 'codecs-sync', to re-open the
same media source again.
After I make this patch and verify it, I will attach it here.
--
You received this
** Description changed:
Ubuntu: 12.04
totem: 3.0.1-0ubuntu21
There is a feature of totem that it can detect the missing gstreamer plugins
and install them automatically.
It will pop out this message after it finished the installation of gstreamer
plugins.
However totem will work
Public bug reported:
Ubuntu: 12.04
totem: 3.0.1-0ubuntu21
There is a feature of totem that it can detect the missing gstreamer plugins
and install them automatically.
It will pop out this message after it finished the installation of gstreamer
plugins.
However totem will work normally after we
This is the bug report at upstream
https://bugzilla.gnome.org/show_bug.cgi?id=681426 .
** Also affects: totem via
https://bugzilla.gnome.org/show_bug.cgi?id=681426
Importance: Unknown
Status: Unknown
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You
Public bug reported:
$ bzr branch lp:ubuntu/precise/gnome-terminal
bzr: ERROR: Revision
{package-imp...@ubuntu.com-20111215150734-sizp9ugqesip4swb} not present in
Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)],
[].
** Affects: gnome-terminal
Because upstream's code base is changed.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Public bug reported:
In an ASUS all-in-one machine with ATI HD7470M, the brightness slider is
not shown in the Screen capplet.
** Affects: gnome-settings-daemon
Importance: Unknown
Status: Unknown
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/925327
Title:
No brightness slider in Screen capplet in System Settings
To
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/916372
Title:
gnome-fallback-mount-helper crashed with signal 7 in
bzr commit -m Checking Intel ATOM CPU to determine video frame rate. (LP:
#610600) --fixes lp:610600 # Committed revision 61.
bzr push lp:~fourdollars/cheese/bug-610600/ # Pushed up to revision 61.
dput ppa:fourdollars/cheese cheese_2.32.0-0ubuntu2.1~natty3_source.changes
--
You received this
http://paste.ubuntu.com/688909/ check_atom_cpu() can be used to check
Intel ATOM CPU.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/610600
Title:
Serious video performance
Comment #22 can also get acceptable result on Asus EeePC 1011PX.
** Attachment added: CPU Information of Asus EeePC 1011PX
https://bugs.launchpad.net/oem-priority/+bug/610600/+attachment/2249031/+files/cpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Comment #22 can also get acceptable result.
If I can integrate Comment #20 and Comment #22, it should fix cheese
performance issue on Atom CPUs.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
Although reducing video frame rate can get acceptable result on Atom
CPUs, it also affects the quality of video recording on other CPUs that
they can get better quality originally.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Test on Lenovo IdeaPad S10-3.
cmd
gst-launch \
autoaudiosrc ! queue ! audioconvert ! vorbisenc !
oggmux name=mux ! filesink location=webcam.ogv \
v4l2src ! videorate ! timeoverlay !
'video/x-raw-yuv,width=320,height=240,framerate=15/1' ! tee
To lower video frame rate can get acceptable result.
cmd
gst-launch \
autoaudiosrc ! queue ! audioconvert ! vorbisenc ! oggmux name=mux !
filesink location=webcam.ogv \
v4l2src ! 'video/x-raw-yuv,width=640,height=480,framerate=5/1' ! tee
name=webcam \
webcam. ! queue ! timeoverlay !
I have some patch for cheese on natty.
https://launchpad.net/~fourdollars/+archive/cheese
https://code.launchpad.net/~fourdollars/cheese/bug-610600
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
This patch can help to fix this issue.
** Patch added: 19_fix_invalid_screensaver.patch
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/779639/+attachment/2167988/+files/19_fix_invalid_screensaver.patch
--
You received this bug notification because you are a member of
I also prepare ppa:fourdollars/gnome-screensaver.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/779639
Title:
gnome screensaver activation is hindered by unobscure
Here is another workaround I found.
/apps/metacity/keybinding_commands/command_1 gnome-terminal --geometry 0x0
--hide-menubar -x xdotool key XF86Display
/apps/metacity/global_keybindings/run_command_1 Mod4p
--
Video out hot key sends super + p + return on many upcoming Dell HP systems
I see the following in gnome-power-manager-2.30.0/src/gpm-prefs-core.c
line 382
} else if (policy == GPM_ACTION_POLICY_NOTHING) {
/* we only add do nothing in the GUI if the user has explicitly specified
this in GConf */
if (value == GPM_ACTION_POLICY_NOTHING) {
85 matches
Mail list logo
