[Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
** 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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945298] Re: To support goodix fp device [27C6:63BC]
** 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap
** 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 have not enough height and items overlap To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: Some external 4K monitor is not working properly
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. https://bugs.launchpad.net/bugs/1890772 Title: Some external 4K monitor is not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: Some external 4K monitor is not working properly
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 00 a0 f0 70 1f 80 30 20 35 00 55 50 21 00 00 1a 00 00 00 fc 00 50 48 4c 20 32 37 36 45 38 56 0a 20 20 00 00 00 fd 00 17 50 1e a0 3c 00 0a 20 20 20 20 20 20 01 72 02 03 33 f1 4c 90 04 03 1f 13 01 12 5d 5e 5f 60 61 23 09 07 07 83 01 00 00 6d 03 0c 00 10 00 38 78 20 00 60 01 02 03 67 d8 5d c4 01 78 80 03 e3 0f 00 0c 56 5e 00 a0 a0 a0 29 50 30 20 35 00 55 50 21 00 00 1e 02 3a 80 18 71 38 2d 40 58 2c 45 00 55 50 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 4d 6c 80 a0 70 70 3e 80 30 20 3a 00 55 50 21 00 00 1a 00 00 00 00 4e EDID version: 1.3 Manufacturer: PHL Model 49551 Serial Number 1981 Made in week 8 of 2019 Digital display Maximum image size: 60 cm x 34 cm Gamma: 2.20 DPMS levels: Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6455, 0.3339 Green: 0.3017, 0.6357 Blue: 0.1542, 0.0566 White: 0.3125, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48066.667 Hz 4:335.000 kHz 30.240 MHz (Apple) 640x48072.809 Hz 4:337.861 kHz 31.500 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60056.250 Hz 4:335.156 kHz 36.000 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60072.188 Hz 4:348.077 kHz 50.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 832x62474.551 Hz 4:349.726 kHz 57.284 MHz (Apple) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76870.069 Hz 4:356.476 kHz 75.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) Standard Timings 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) 1440x90059.887 Hz 16:10 55.935 kHz 106.500 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1280x96060.000 Hz 4:360.000 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) Detailed mode: Clock 533.250 MHz, 597 mm x 336 mm 3840 3888 3920 4000 ( 48 32 80) 2160 2163 2168 ( 3 5 54) +hsync -vsync VertFreq: 59.997 Hz, HorFreq: 133.312 kHz Detailed mode: Clock 262.750 MHz, 597 mm x 336 mm 3840 3888 3920 4000 ( 48 32 80) 2160 2163 2168 2191 ( 3 5 23) +hsync -vsync VertFreq: 29.981 Hz, HorFreq: 65.688 kHz Display Product Name: PHL 276E8V Display Range Limits Monitor ranges (GTF): 23-80 Hz V, 30-160 kHz H, max dotclock 600 MHz Has 1 extension block Checksum: 0x72 CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 47 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (VIC 93) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (VIC 94) 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (VIC 95) 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.0.0.0 DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 600 MHz Extended HDMI video details: HDMI VICs: 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (HDMI VIC 1) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (HDMI VIC 2) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (HDMI VIC 3) Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum) Version: 1 Maximum TMDS Character Rate: 600 MHz SCDC
[Bug 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
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 external Full HD that is over the hardware limitation of DELL DOCK - WD19 130W so it failed. -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841886] [NEW] Join Displays failed when using two external monitor of one Full HD and one Ultra HD
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 monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf ** Affects: oem-priority Importance: Undecided Status: New ** Affects: oem-priority/bionic Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1841034 somerville ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic
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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in 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 to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
** 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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
$ 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. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs
** 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 sysfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button does nothing
** 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 button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762385] Re: dell_wmi: Unknown key codes
** 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: Unknown key codes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
@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: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762910] [NEW] The position of audio mute icon doesn't keep alignment to audio on
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" https://bugs.launchpad.net/bugs/1762910/+attachment/5110134/+files/AudioMute.png ** Changed in: gnome-session (Ubuntu) Status: New => Invalid ** Also affects: adwaita-icon-theme (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-session (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1762910 Title: The position of audio mute icon doesn't keep alignment to audio on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1762910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756788] [NEW] Removing "Startup Applications" in "Ubuntu Software" makes the system unable to launch GDM
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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 12:54:57 2018 InstallationDate: Installed on 2018-03-15 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2018-03-19 12-44-15.png" https://bugs.launchpad.net/bugs/1756788/+attachment/5083643/+files/Screenshot%20from%202018-03-19%2012-44-15.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1756788 Title: Removing "Startup Applications" in "Ubuntu Software" makes the system unable to launch GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1756788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1593928] Re: I can't open gnome-terminal when using gcin input method after I update the system recently.
*** 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, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1593928 Title: I can't open gnome-terminal when using gcin input method after I update the system recently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1593928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480217] Re: Nautilus background handling screwed when changing scaling factor.
** 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. https://bugs.launchpad.net/bugs/1480217 Title: Nautilus background handling screwed when changing scaling factor. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1480217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480217] Re: Nautilus background handling screwed when changing scaling factor.
** 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 changing scaling factor. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1480217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480217] Re: Nautilus background handling screwed when changing scaling factor.
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 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 changing scaling factor. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1480217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480217] Re: Nautilus background handling screwed when changing scaling factor.
** 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. https://bugs.launchpad.net/bugs/1480217 Title: Nautilus background handling screwed when changing scaling factor. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1480217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480143] Re: The organized files and folders are covered by Unity Launcher.
@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. https://bugs.launchpad.net/bugs/1480143 Title: The organized files and folders are covered by Unity Launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1480143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480217] Re: Nautilus transparent background becomes a mess when changing scaling factor.
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1480217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480143] [NEW] The organized files and folders are covered by Unity Launcher.
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 folders should be covered by Unity Launcher. Actual Result: * The organized files and folders are covered by Unity Launcher. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi ** Attachment added: OrganizeDesktopHiDPI.png https://bugs.launchpad.net/bugs/1480143/+attachment/4436764/+files/OrganizeDesktopHiDPI.png -- 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/1480143 Title: The organized files and folders are covered by Unity Launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1480143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480143] Re: The organized files and folders are covered by Unity Launcher.
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1480143 Title: The organized files and folders are covered by Unity Launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1480143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480217] [NEW] Nautilus transparent background becomes a mess when changing scaling factor.
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 normally. Actual Result: * The background becomes a mess. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi ** Attachment added: Nautilus.png https://bugs.launchpad.net/bugs/1480217/+attachment/4436858/+files/Nautilus.png -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1480217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480207] [NEW] eog (a GNOME image viewer) doesn't support HiDPI display.
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 blurred. Actual Result: * The image becomes blurred. ** Affects: eog Importance: Unknown Status: Unknown ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi ** Description changed: 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 13. + 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 blurred. Actual Result: * The image becomes blurred. ** Bug watch added: GNOME Bug Tracker #740240 https://bugzilla.gnome.org/show_bug.cgi?id=740240 ** Also affects: eog via https://bugzilla.gnome.org/show_bug.cgi?id=740240 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1480207 Title: eog (a GNOME image viewer) doesn't support HiDPI display. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1480207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
** 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. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
@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 Bluetooth input devices doesn't change accordingly. So it failed. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
@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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
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 as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
** 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. https://bugs.launchpad.net/bugs/1339998 Title: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1340544] Re: gnome-rr: Normalize the minimum brightness level.
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) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1340544 Title: gnome-rr: Normalize the minimum brightness level. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1340544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.
** 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. https://bugs.launchpad.net/bugs/1340544 Title: gnome-rr: Adjust the minimum brightness level when the maximum = 100. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1340544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.
** 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 member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1340544 Title: gnome-rr: Adjust the minimum brightness level when the maximum = 100. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1340544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1340544] [NEW] gnome-rr: The minimum brightness can not be 0.
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: Unknown Status: Unknown ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #733044 https://bugzilla.gnome.org/show_bug.cgi?id=733044 ** Also affects: gnome-desktop via https://bugzilla.gnome.org/show_bug.cgi?id=733044 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1340544 Title: gnome-rr: The minimum brightness can not be 0. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1340544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
@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 information in Logitech wireless mouse. Even a non-chargeable battery has its remaining power information. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
@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. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
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 https://launchpad.net/ubuntu/+archive/primary/+files/gnome-settings-daemon_3.4.2-0ubuntu0.6.4.dsc`. -- 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/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
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 That should be the key to introduce the regression. -- 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/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069044] Re: Status indicator shows charging status of mouse battery instead of main laptop battery
*** 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 batteries as batteries -- 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/1069044 Title: Status indicator shows charging status of mouse battery instead of main laptop battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1069044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
** 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 for the users. Originally, + there is no such Bluetooth battery information until Ubuntu 12.04 brings + linux-quantal-lts and linux-raring-lts, so those linux kernels also + bring this issue. + + [Test Case] + + * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. + * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. + * If you have ever named your own Apple Wireless Mouse by UTF-8 string, you have find that the 'Model' field of Apple Wireless Mouse shows only ASCII without the correct name. + + [Regression Potential] + + * There is no obvious regression as I know. + + [Other Info] + + * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). + This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: - hci09C:B7:0D:80:71:DB + hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: - List of PLAYBACK Hardware Devices - card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of PLAYBACK Hardware Devices + card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1726 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: - Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' -Mixer name : 'Realtek ALC269VC' -Components : 'HDA:10ec0269,103c2aee,00100202' -Controls : 21 -Simple ctrls : 10 + Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' + Mixer name : 'Realtek ALC269VC' + Components : 'HDA:10ec0269,103c2aee,00100202' + Controls : 21 + Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.5.0-23-generic N/A - linux-backports-modules-3.5.0-23-generic N/A - linux-firmware1.79.1 + linux-restricted-modules-3.5.0-23-generic N/A + linux-backports-modules-3.5.0-23-generic N/A + linux-firmware1.79.1 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
** 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 the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. - * If you have ever named your own Apple Wireless Mouse by UTF-8 string, you have find that the 'Model' field of Apple Wireless Mouse shows only ASCII without the correct name. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard -- 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
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
** 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 device batteries as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
** 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 after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
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. https://bugs.launchpad.net/bugs/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as batteries
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. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads bluetooth input devices as a Battery
$ grep -r . /sys/class/power_supply/*hid* /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/type:Battery /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/control:auto /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/async:disabled /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/runtime_enabled:disabled /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/runtime_active_kids:0 /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/runtime_active_time:0 grep: /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/autosuspend_delay_ms: Input/output error /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/runtime_status:unsupported /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/runtime_usage:0 /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/power/runtime_suspended_time:0 /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/scope:Device grep: /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/capacity: Input/output error /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/online:1 /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/status:Discharging /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/model_name:“$4”的鍵盤 /sys/class/power_supply/hid-10:9A:DD:96:DA:0D-battery/present:1 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/type:Battery /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/control:auto /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/async:disabled /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/runtime_enabled:disabled /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/runtime_active_kids:0 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/runtime_active_time:0 grep: /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/autosuspend_delay_ms: Input/output error /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/runtime_status:unsupported /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/runtime_usage:0 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/power/runtime_suspended_time:0 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/scope:Device /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/capacity:61 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/online:1 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/status:Discharging /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_NAME=hid-28:CF:DA:BB:74:1B-battery /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_PRESENT=1 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_ONLINE=1 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_CAPACITY=61 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_MODEL_NAME=“$4”的滑鼠 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_STATUS=Discharging /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/uevent:POWER_SUPPLY_SCOPE=Device /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/model_name:“$4”的滑鼠 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery/present:1 -- 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 bluetooth input devices as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: Treats bluetooth input device batteries as system power supply
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 . /sys/class/power_supply/* /sys/class/bluetooth/* /tmp/out.txt 21 ** Attachment added: out.txt https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+attachment/3802450/+files/out.txt -- 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 system power supply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads bluetooth input devices as a Battery
`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: System reads bluetooth input devices as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads bluetooth input devices as a Battery
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 0 Sep 4 13:32 /sys/class/power_supply/hid-28:CF:DA:BB:74:1B-battery - ../../devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:13/0005:05AC:030D.0004/power_supply/hid-28:CF:DA:BB:74:1B-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: System reads bluetooth input devices as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads bluetooth input devices as a Battery
$ 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 /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: total 0 -r--r--r-- 1 root root 4096 Sep 4 13:38 capacity lrwxrwxrwx 1 root root0 Sep 4 13:32 device - ../../../0005:05AC:0239.0003 -r--r--r-- 1 root root 4096 Sep 4 13:38 model_name -r--r--r-- 1 root root 4096 Sep 4 13:38 online drwxr-xr-x 2 root root0 Sep 4 13:32 power lrwxrwxrwx 1 root root0 Sep 4 13:38 powers - ../../../0005:05AC:0239.0003 -r--r--r-- 1 root root 4096 Sep 4 13:38 present -r--r--r-- 1 root root 4096 Sep 4 13:32 scope -r--r--r-- 1 root root 4096 Sep 4 13:38 status lrwxrwxrwx 1 root root0 Sep 4 13:38 subsystem - ../../../../../../../../../../../../class/power_supply -r--r--r-- 1 root root 4096 Sep 4 13:32 type -rw-r--r-- 1 root root 4096 Sep 4 13:38 uevent /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/power: total 0 -rw-r--r-- 1 root root 4096 Sep 4 13:32 async -rw-r--r-- 1 root root 4096 Sep 4 13:32 autosuspend_delay_ms -rw-r--r-- 1 root root 4096 Sep 4 13:32 control -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_active_kids -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_active_time -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_enabled -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_status -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_suspended_time -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_usage $ ls -lR /sys/class/power_supply/../../devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:13/0005:05AC:030D.0004/power_supply/hid-28:CF:DA:BB:74:1B-battery /sys/class/power_supply/../../devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:13/0005:05AC:030D.0004/power_supply/hid-28:CF:DA:BB:74:1B-battery: total 0 -r--r--r-- 1 root root 4096 Sep 4 13:32 capacity lrwxrwxrwx 1 root root0 Sep 4 13:32 device - ../../../0005:05AC:030D.0004 -r--r--r-- 1 root root 4096 Sep 4 13:38 model_name -r--r--r-- 1 root root 4096 Sep 4 13:38 online drwxr-xr-x 2 root root0 Sep 4 13:32 power lrwxrwxrwx 1 root root0 Sep 4 13:38 powers - ../../../0005:05AC:030D.0004 -r--r--r-- 1 root root 4096 Sep 4 13:38 present -r--r--r-- 1 root root 4096 Sep 4 13:32 scope -r--r--r-- 1 root root 4096 Sep 4 13:38 status lrwxrwxrwx 1 root root0 Sep 4 13:32 subsystem - ../../../../../../../../../../../../class/power_supply -r--r--r-- 1 root root 4096 Sep 4 13:32 type -rw-r--r-- 1 root root 4096 Sep 4 13:38 uevent /sys/class/power_supply/../../devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:13/0005:05AC:030D.0004/power_supply/hid-28:CF:DA:BB:74:1B-battery/power: total 0 -rw-r--r-- 1 root root 4096 Sep 4 13:32 async -rw-r--r-- 1 root root 4096 Sep 4 13:32 autosuspend_delay_ms -rw-r--r-- 1 root root 4096 Sep 4 13:32 control -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_active_kids -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_active_time -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_enabled -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_status -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_suspended_time -r--r--r-- 1 root root 4096 Sep 4 13:32 runtime_usage -- 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 bluetooth input devices as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads bluetooth input devices as a 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 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 bluetooth input devices as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads Apple Magic Mouse (BT) as a Battery
** 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 Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: System reads Apple Magic Mouse (BT) as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads Apple Magic Mouse (BT) as a Battery
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 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 Mouse (BT) as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads Apple Magic Mouse (BT) as a Battery
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 https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+attachment/3755782/+files/02-try-to-work-out-if-the-device-is-powering-the-system.patch -- 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 Mouse (BT) as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads Apple Magic Mouse (BT) as a Battery
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 https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+attachment/3755785/+files/03-detect-bluetooth-keyboard-mouse.patch -- 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 Mouse (BT) as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153488] Re: System reads Apple Magic Mouse (BT) as a Battery
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 Mouse (BT) as a Battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
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 subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1041032 Title: An error occurred Location not found after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
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 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 reopen it. + 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. + Relative to Bug #1041287. -- 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 after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
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 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 after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
** 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 normally after we reopen it. + + Relative to Bug #1041287. -- 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 after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] [NEW] An error occurred Location not found after automatically installing the missing gstreamer plugins.
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 reopen it. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: totem Importance: Unknown Status: Unknown ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #681426 https://bugzilla.gnome.org/show_bug.cgi?id=681426 -- 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 after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
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 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 after automatically installing the missing gstreamer plugins. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017523] [NEW] `bzr branch lp:ubuntu/precise/gnome-terminal` fails.
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 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1017523
Title:
`bzr branch lp:ubuntu/precise/gnome-terminal` fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1017523/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 925327] Re: No brightness slider in Screen capplet in System Settings
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. https://bugs.launchpad.net/bugs/925327 Title: No brightness slider in Screen capplet in System Settings To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/925327/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 925327] [NEW] No brightness slider in Screen capplet.
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 Status: New ** Bug watch added: GNOME Bug Tracker #669193 https://bugzilla.gnome.org/show_bug.cgi?id=669193 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=669193 Importance: Unknown Status: Unknown -- 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. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/925327/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 925327] Re: No brightness slider in Screen capplet in System Settings
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/925327/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 916372] Re: gnome-fallback-mount-helper crashed with signal 7 in g_simple_async_result_complete()
** 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 g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/916372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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 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 regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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 regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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 Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/610600 Title: Serious video performance regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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. https://bugs.launchpad.net/bugs/610600 Title: Serious video performance regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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 gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/610600 Title: Serious video performance regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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 name=webcam \ webcam. ! queue ! xvimagesink \ webcam. ! queue ! theoraenc ! mux. /cmd cmd gst-launch \ autoaudiosrc ! queue ! audioconvert ! vorbisenc ! oggmux name=mux ! filesink location=webcam.ogv \ v4l2src ! videorate ! timeoverlay ! 'video/x-raw-yuv,width=640,height=480,framerate=5/1' ! tee name=webcam \ webcam. ! queue ! xvimagesink \ webcam. ! queue ! theoraenc ! mux. /cmd ** Attachment added: CPU Information of Lenovo IdeaPad S10-3 https://bugs.launchpad.net/cheese/+bug/610600/+attachment/2241919/+files/cpuinfo.txt -- 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 regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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 ! xvimagesink \ webcam. ! queue ! videorate ! theoraenc ! mux. /cmd Test on Asus EeePC 1011PX. -- 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 regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 610600] Re: Serious video performance regression in cheese (2.28.1-2.30.1)
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. https://bugs.launchpad.net/bugs/610600 Title: Serious video performance regression in cheese (2.28.1-2.30.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/610600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
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 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 routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 779639] Re: gnome screensaver activation is hindered by unobscure routine
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 routine To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 539477] Re: Video out hot key sends super + p + return on many upcoming Dell HP systems
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 https://bugs.launchpad.net/bugs/539477 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390816] Re: external monitor output is switched off when closing the laptop-lid when gnome-power-manager is set to blank screen on closing
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) {
gtk_combo_box_append_text (GTK_COMBO_BOX (widget), _(Do nothing));
g_ptr_array_add (array, GINT_TO_POINTER (policy));
}
} else {
egg_warning (Unknown action read from conf: %i, policy);
}
--
external monitor output is switched off when closing the laptop-lid when
gnome-power-manager is set to blank screen on closing
https://bugs.launchpad.net/bugs/390816
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
