[Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Gabriel Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as well. linux-image-generic-hwe-20.04 5.11.0.27.29~20.04.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869641] [NEW] Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0
Public bug reported: Description:Ubuntu Focal Fossa (development branch) Release:20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: focal gnome-shell ibus wayland ** Tags added: focal gnome-shell ibus wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869641 Title: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
** Description changed: + [Impact] + Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, + + [Test Case] To reproduce on any Ubuntu 16.04 classic (Xenial): #apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. + [Regression Potential] + + Only affected fwupd in Ubuntu 16.04. + + + [Additional Info] + === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
** Patch added: "Raise-the-metadata-limit-to-10Mb.debdiff" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+attachment/5265504/+files/Raise-the-metadata-limit-to-10Mb.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
@Mario Thanks for the quick resolution, will follow up on this and find sponsor on the Xenial SRU. As for UC16, I've verified the fix and published uefi-fw-tools snap in beta channel with the fix, will make internally verified, update gated snap and release to stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
** Description changed: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): - #sudo apt install fwupd + #apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
** Description changed: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): + #sudo apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
** Description changed: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) - #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc + + The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
** Description changed: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, - To reproduce on any Ubuntu 16.04 classic: + To reproduce on any Ubuntu 16.04 classic (Xenial): #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. + + This is worked in Ubuntu 18.04 (bionic) + + + #fwupdmgr refresh + Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz + Downloading… [***] + Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] [NEW] fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
Public bug reported: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic: #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. === Distributor ID: Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536871] Re: [MIR] fwupd
@Mario For #23, does this affect system without gnupg2 installed ? What will happen if system only has gnupg 1.x ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536871 Title: [MIR] fwupd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1536871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
I've verified trusty unity-control- center14.04.3+14.04.20140922-0ubuntu1.1 from trusty-proposed archive, verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
@Alberto It was originally a quick workaround for the possible race condition so could you help to modify the code with what Iain had suggested? Totally agree that making it asynchronous, adding more verbose log and finding out the root cause are better ways to fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471708 Title: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1471708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471708] [NEW] For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
Public bug reported:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via Lid
Close
Summary:
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to tty1.
Failure rate ~ 1/5
Steps:
1. install Ubuntu 14.04.2 3.19+ kernel and boot to OS
2. Close the lid
3. Open the lid
4. check the display status
Expected results: System should resume to the log in screen when open
the lid
Actual results:
System sometimes fails to resume back to the log in screen but blackscreen
instead.
(Failure rate~ 1/5)
Details:
unity-settings-deamon will call xinput --map-to-output 11 eDP1 at background,
and it's being blocked so only cursor will show on screen.
1. Switch to tty1 when this happen
2. Login with user account on tty1.
3. Use DISPLAY=:0 xrandr on commandline you'll see it's being blocked.
Since xinput is being blocked for some unknown reason (in gdb it shows
polling on xcb_connect_to_fd() in XOpenDisplay() ),
a possible workaround is to set a timeout for xinput in u-s-d.
=== modified file 'plugins/xrandr/gsd-xrandr-manager.c'
--- plugins/xrandr/gsd-xrandr-manager.c 2014-06-05 11:56:15 +
+++ plugins/xrandr/gsd-xrandr-manager.c 2015-07-01 08:59:56 +
@@ -2199,7 +2199,7 @@
if (gnome_rr_output_info_is_active(output)) {
g_debug (Mapping touchscreen %d onto output %s,
device_id, name);
- sprintf (command, xinput --map-to-output %d %s,
+ sprintf (command, timeout 3s xinput --map-to-output %d %s,
device_id, name);
status = system (command);
}
** Affects: oem-priority
Importance: Critical
Status: New
** Affects: oem-priority/trusty
Importance: Critical
Status: New
** Affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided = Critical
** Changed in: oem-priority/trusty
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
For skylake system, u-s-d cause a black screen when resume from S3 via
Lid Close
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1471708/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382404] Re: 10ec:b723 Realtek Bluetooth on 8723BE not working
Please help to test this DKMS , the package is tested on 3.16 utopic kernel and I'll feedback to realtek that it's not working on the current Ubuntu and mainline kernel. ** Attachment added: oem-realtek-bluetooth-1391408-dkms_2.11.20140423oem6_all.deb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+attachment/4413646/+files/oem-realtek-bluetooth-1391408-dkms_2.11.20140423oem6_all.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382404 Title: 10ec:b723 Realtek Bluetooth on 8723BE not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi has an issue
Please help to test this DKMS and I'll feedback to realtek that it's not working on the current Ubuntu and mainline kernel. ** Attachment added: realtek-rtlwifi-dkms_0020.1030.2014V676.P1_all.deb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+attachment/4413645/+files/realtek-rtlwifi-dkms_0020.1030.2014V676.P1_all.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Realtek Wifi card rtl8723be [10ec:b723] WiFi has an issue To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411923/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411922/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack)
Changed to mainline ppa kernel 4.0.5 , same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411918/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411921/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411915/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411914/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411924/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack)
apport information ** Tags added: apport-collected trusty ** Description changed: In https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940, several users report rtl8723be still have problem on recent version of Ubuntu , https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940/comments/82 suggested open a new bug, the utopic LTS enablement stack (HWE), including 3.16 kernel. uname -a looked like this: Linux buchanan-probook-455 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux - Also, with utopic kernel and module, some user report adding ips=N and - fwlps=N does not help. + Also, with utopic kernel and module, some user report adding ips=N and fwlps=N does not help. + --- + ApportVersion: 2.14.1-0ubuntu3.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: u 1785 F pulseaudio + /dev/snd/controlC0: u 1785 F pulseaudio + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=c2a5715c-c92c-47fa-9aa2-c6f6e03f21bf + InstallationDate: Installed on 2015-06-09 (0 days ago) + InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) + MachineType: Hewlett-Packard HP 455 G2 + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=97d2645a-a2be-49ec-b1bd-37c43ab4eeb1 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.16.0-30-generic N/A + linux-backports-modules-3.16.0-30-generic N/A + linux-firmware 1.127.11 + Tags: trusty + Uname: Linux 3.16.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/25/2014 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: M75 Ver. 01.06 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 2235 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: KBC Version 66.19 + dmi.chassis.asset.tag: 73612P10CU + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvrM75Ver.01.06:bd07/25/2014:svnHewlett-Packard:pnHP455G2:pvrA3009CD10002:rvnHewlett-Packard:rn2235:rvrKBCVersion66.19:cvnHewlett-Packard:ct10:cvr: + dmi.product.name: HP 455 G2 + dmi.product.version: A3009CD10002 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411912/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411916/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411926/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411917/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411913/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411925/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411920/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1461174/+attachment/4411919/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461174] [NEW] Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack)
Public bug reported: In https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940, several users report rtl8723be still have problem on recent version of Ubuntu , https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940/comments/82 suggested open a new bug, the utopic LTS enablement stack (HWE), including 3.16 kernel. uname -a looked like this: Linux buchanan-probook-455 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Also, with utopic kernel and module, some user report adding ips=N and fwlps=N does not help. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461174 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] for 14.04.2 (utopic LTS HWE stack) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240940] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723]
Hi all, As https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240940/comments/82 suggested, I open a new bug on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461174, please move the discussions there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240940 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1240940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
#15 failed. I set intscripts as Pre-Depends (for ifupdown) but still not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
ifupdown depends on initscripts initscripts depends on upstart upstart depends on initscripts and ifupdown The error messages stats that dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. Upstart try to pull in ifupdown and initscripts, however, initscripts is already half-installed (because of other depenency), and ifupdown claim it depends on initscripts, so the apt broke at that stage. I think if we set initscripts as ifupdown's pre-depends, it could solve the problem. I'll try to verify this solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/937196 it could be a similar bug like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
if upgrade ifupdown itself or using following commands there's no such issue #apt-get install --only-upgrade dpkg coreutils sysv-rc sysvinit-utils initscripts udev libudev1 ifupdown libc-bin upstart The failure during dist-upgrade/updrade by apt-get dist-upgrade is pretty weird. ** Attachment added: apt-success.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1452238/+attachment/4396603/+files/apt-success.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
** Attachment added: aptitude.log https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1452238/+attachment/4396142/+files/aptitude.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
Package: udev Source: systemd Version: 204-5ubuntu20kittyhawk1 Architecture: amd64 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Installed-Size: 5143 Depends: libacl1 (= 2.2.51-8), libblkid1 (= 2.19.1), libc6 (= 2.17), libcgmanager0, libdbus-1-3 (= 1.0.2), libkmod2 (= 5~), libnih-dbus1 (= 1.0.0), libnih1 (= 1.0.0), libselinux1 (= 2.0.65), libudev1 (= 204-5ubuntu20kittyhawk1), sysv-rc (= 2.88dsf-24) | file-rc (= 0.8.16), lsb-base (= 3.0-6), util-linux (= 2.16), procps Replaces: systemd-services ( 202-0ubuntu6) Section: admin Priority: important Multi-Arch: foreign not sure why but seems udev only depends on libc6, however libc6-dbg and libc6-dev depends on a old version of libc6, so it seems a loop dependency to me but I'm not sure why libc6-dbg and libc6-dev didn't get upgrade in the same time... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
@4$ which command did you run at firsttime in https://pastebin.canonical.com/130750/ ? apt-get dist-upgrade or apt-get upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452238] Re: Failed to upgrade system from 14.04
@Bin could we use #apt-get dist-upgrade instead? since that's what update-manager would do~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448900] [NEW] systemd-importd not found, breaks functionality of machinectl
Public bug reported: Steps to reproduce: Follow the example of MACHINECTL(1): #machinectl pull-tar https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz Failed pull image: The name org.freedesktop.import1 was not provided by any .service files running on systemd 219-7ubuntu3 with vivid. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448900 Title: systemd-importd not found, breaks functionality of machinectl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035431] Re: bluetooth-wizard failed to connect to a keyboard(logitech)
HP Bluetooth Keyboard K4000 worked fine with packages in trusty- proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooth-wizard failed to connect to a keyboard(logitech) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Description changed: + Trusty (and Utopic) SRU Request: + + [Impact] + + * Set higher priority of glxinfo's result then Xorg's log for Details + - Overview - Graphics info in Unity Control Center. + + [Test Case] + + * System with glxinfo installed (in mesa-utils) will show glxinfo's + result first for Details - Overview - Graphics info in Unity + Control Center. + + * System without glxinfo will still parse Xorg's log for Details - + Overview - Graphics info in Unity Control Center. + + [Regression Potential] + + * Should be minimal, the info showed in glxinfo is more accurate. + + [Original Bug Info] + In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted at https://code.launchpad.net/~timchen119 /unity-control-center/unity-control-center.lp1417034/+merge/248220 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417034] [NEW] Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
Public bug reported: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. A private bug is filed at: https://bugs.launchpad.net/bugs/1369859 A merge proposal is submitted. ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1417034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Description changed: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. - A private bug is filed at: https://bugs.launchpad.net/bugs/1369859 + Private bugs were filed at: + https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted. ** Description changed: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: - https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 - A merge proposal is submitted. + A merge proposal is submitted at https://code.launchpad.net/~timchen119 + /unity-control-center/unity-control-center.lp1417034/+merge/248220 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308515] Re: black screen when enabling rotation on a gpu screen
https://bugs.launchpad.net/bugs/1386620 this issue is fixed by Maarten Lankhorst (mlankhorst) and the option will be re-enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308515 Title: black screen when enabling rotation on a gpu screen To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312349] Re: Microsoft bluetooth mobile keyboard 6000 cannot be used
verified work on utopic gnome-bluetooth 3.8.2.1-0ubuntu9 with MS bluetooth keyboard 6000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312349 Title: Microsoft bluetooth mobile keyboard 6000 cannot be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1312349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312349] Re: Microsoft bluetooth mobile keyboard 6000 cannot be used
verified work on trusty gnome-bluetooth 3.8.2.1-0ubuntu4.1 with MS bluetooth keyboard 6000 ** Tags removed: verification-failed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312349 Title: Microsoft bluetooth mobile keyboard 6000 cannot be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1312349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
@Scott, Hi, thanks for the testing and feedback, that was because gnome bluetooth wizard is waiting the SSP callback event from the agent (and it may have different timing for different devices), currently it will briefly shows the usual PIN code page and switch to the SSP page when it recieve the callback event. I will try to get some time to see how to fix this more properly and not broke gnome bluetooth wizard's current structure since this indeed affect user experience, but the current patch should be enough to fix the original SSP paring issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
@Scott, or anyone has K810/K760 Can you also help me to check: export G_MESSAGES_DEBUG=all ; bluetooth-wizard and paste the message ** (bluetooth-wizard:27420): DEBUG: Getting pincode for device XXX ** (bluetooth-wizard:27420): DEBUG: Got pin XXX on the LP? thanks a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322406] Re: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly
*** This bug is a duplicate of bug 1322407 *** https://bugs.launchpad.net/bugs/1322407 ** Tags added: stella-oem-highlight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322406 Title: NFS kernel server creates a kworker with 100% CPU usage, then hangs randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131964] Re: search for files.. entry in gnome-menu should launch tracker-search-tool
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/131964 Title: search for files.. entry in gnome-menu should launch tracker-search- tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/131964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131964] Re: search for files.. entry in gnome-menu should launch tracker-search-tool
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/131964 Title: search for files.. entry in gnome-menu should launch tracker-search- tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/131964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219560] Re: Can't pair Logitech K810 using GUI
Hi, For people who has this keyboard (logitech K810 or logitech K760 ), can you help me to test the packages mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- bluetooth/+bug/1035431/comments/27 I've got an HP keyboard has the same issue and provided a fix, if the result is positive I'll send an SRU to Trusty. (Ubuntu 14.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219560 Title: Can't pair Logitech K810 using GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1219560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
Hi, Recent I got a HP bluetooth keyboard which has the exactly same issue, after some analysis it's a problem between the dbus interface with gnome-bluetooth and bluez agent, and I've backport some commits from bluez5 and fix some issues in gnome-bluetooth, Can anyone who has this keyboard help me test the packages here: https://launchpad.net/~timchen119/+archive/bluez4-ssp instructions: #sudo add-apt-repository -y ppa:timchen119/bluez4-ssp apt-get update apt-get install gnome-bluetooth bluez the source code is locate at the Related branches in this bug. If the result is positive I'll send the merge and prepare an SRU to sponsor. I've upload Trusty, Utopic and Precise packages to my ppa, due to the bluez package is too old in Precise I've only port basic UI support and not as fancy as Trusty or Utopic but should still be usable. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1035431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1035431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310518] [NEW] Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Public bug reported: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6 [slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11 [slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press super on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1310518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
** Description changed: + Touch screen and touchpad lost click function after quickly tapped dash - home repeatly by touch screen + home repeatly by touch screen, Installed 14.04, still have same issue. + + Quickly tapped dash home more than three times by touch screen.Found + touch screen and touchpad lost click function. + + Note: + 1.When this issue occured, cursor still can be moved by touch screen/touchpad. + 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. + + Steps to Reproduce: + 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. + 2.Quickly tapped dash home more than three times by touch screen. + 3.Found touch screen and touchpad lost click function. + + This bug is reported from private OEM project, also check + https://launchpad.net/bugs/1297067 + + == + + using xinput --query-state can actually see the button press event + + ⎡ Virtual core pointer id=2 [master pointer (3)] + ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] + ⎜ ↳ syntp id=6[slave pointer (2)] + ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] + + #xinput --query-state 11 + 2 classes : + ButtonClass + button[1]=up + button[2]=up + button[3]=up + button[4]=up + button[5]=up + ValuatorClass Mode=Absolute Proximity=In + valuator[0]=398 + valuator[1]=1652 + valuator[2]=5 + valuator[3]=3 + valuator[4]=0 + valuator[5]=399 + valuator[6]=1653 + + #xinput --query-state 6 + 2 classes : + ButtonClass + button[1]=down + button[2]=up + button[3]=up + button[4]=up + button[5]=up + button[6]=up + button[7]=up + button[8]=up + ValuatorClass Mode=Relative Proximity=In + valuator[0]=1 + valuator[1]=394 + + touchpad's button and touchpanel's + valuator[2] and valuator[3] will changed after we press the button (or monitor) + + Also I found press super on keyboard will recover the + touchscreen/touchpad loss. + ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-stella-daan2-precise-amd64-20140416-1 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: - LANGUAGE=en_US: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High ** Changed in: oem-priority/trusty Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
I can not reproduce this in trusty daily build today. I think it already fixed in trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and garbled after resume from suspend
it also can reproduce in Unity 2D + 331.20 driver + nvidia-prime on 12.04 + Saucy LTS HWE stack. (3.11 kernel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and garbled after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1210077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
good to me test on notify-osd-icons/0.8~precise on Precise. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
works fine to me with notify-osd/0.9.34-0ubuntu2.1 on Precise. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236233] Re: BIOS that SMIBIOS is not fuly supported by dmidecode causes image autmatic installation fail
Could we backport the saucy's (or trusty's ) dmidecode to Precise? I try to find the bzr branch but lp:dmidecode seems a bit outdated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236233 Title: BIOS that SMIBIOS is not fuly supported by dmidecode causes image autmatic installation fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1236233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
** Description changed: + 12.04 Precise SRU info: + + [Impact] + The package provide new notify-osd-icons for Radio enable/disable and Display switch. + + This is related to https://bugs.launchpad.net/ubuntu/+source/notify- + osd/+bug/404658 to be used in OEM projects. + + [Test Case] + + The package should be install/upgrade correctly. + + [Regression Potential] + + No known risk right now. + + [Other Info] + 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
https://code.launchpad.net/~timchen119/ubuntu/precise/notify-osd-icons /notify-osd-icons-precise-1253591/+merge/199619 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244065] Re: Add more options to the power settings menu
works fine to me with gnome-control-center/1:3.4.2-0ubuntu0.13.1 on Precise. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1244065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011423] Re: [Feature] Intel Bluetooth on Wilkins Peak wireless adapter
Both 7260 and 3160 bluetooth works on precise-proposed/linux-firmware 1.79.9. Test kernel was precise-updates/linux-image-generic-lts- saucy/3.11.0-13-generic kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011423 Title: [Feature] Intel Bluetooth on Wilkins Peak wireless adapter To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1011423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253591] [NEW] Display switch and Radio enable/disable hotkey icons
Public bug reported: 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea ** Affects: oem-priority Importance: Undecided Status: New ** Affects: notify-osd-icons (Ubuntu) Importance: Undecided Status: New ** Attachment added: NotifyOSD-icons.zip https://bugs.launchpad.net/bugs/1253591/+attachment/3913992/+files/NotifyOSD-icons.zip ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
Radio enable/disable ** Attachment added: MOV_1319.mp4 https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+attachment/3914784/+files/MOV_1319.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
Switch display ** Attachment added: MOV_1325.mp4 https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+attachment/3914783/+files/MOV_1325.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239605] Re: Combo audio jack support (what did you plug in?-dialog)
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239605 Title: Combo audio jack support (what did you plug in?-dialog) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1239605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055874] Re: Automatic sleep settings are not followed precisely
** Description changed: + [Impact] + + * User can choose the suspend time and blank time in the gnome control + center (system settings). + +Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. + (which the value user can not adjust in the default UI but only using the CLI) + +This two categories of values (dim time/suspendblank time) should + not be related at all, however,the current Ubuntu Precise (12.04)'s + gnome settings daemon (3.4.2) it actually suspend or blank the screen on + user set time plus the dim time, which added additional 30 secs by + default. + +In some OEM projects, in order to fulfill the OEM requests for Energy + Star standard, the dim time is set to 5 minutes default (instead of 30 + secs), and this make the suspend time and screen blank time very + inaccurate, because user will have additional 5 minutes to wait before + the screen blank or system suspend. (Inactive time to suspend is about 5 + minutes more than setting.) + + * The User do not need modify anything for this patch. + + [Test Case] + + * Please use Ubuntu Precise (12.04) to test, this issue is already fixed + in Ubuntu Raring (13.04) + + * Set idle-dim-time to 300 first (5 minutes), it's much easier to find out this issue. + (the default is 30 secs and it's somehow not as easy to observe, but the result should be same.) + Command: + #gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time 300 + + *In settings: + Turn screen off: 10 minutes + Suspend: 10 minutes on battery power, 30 minutes when plugged in. + + Actual: + On battery: Screen turned off after 10 minutes, suspend after about 5 more minutes(15 minutes total). + When plugged in: Screen turned off after 10 minutes, suspend after about 25 more minutes(35 minutes total). + + Steps: + 1. Check power settings and brightness settings + 2. Leave the system inactive + + Expected results: Inactive time to suspend is same as setting + + Actual results: Inactive time to suspend is about 5 minutes more than + setting + + [Regression Potential] + + * This do not need to modify any user settings. + + * The impact should be minimal for an inaccurate timing of + suspend/blanking. + + [Other Info] + + Original bug description: + When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) ** Description changed: [Impact] - * User can choose the suspend time and blank time in the gnome control + * User can choose the suspend time and blank time in the gnome control center (system settings). -Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. + Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. (which the value user can not adjust in the default UI but only using the CLI) -This two categories of values (dim time/suspendblank time) should + This two categories of values (dim time/suspendblank time) should not be related at all, however,the current Ubuntu Precise (12.04)'s gnome settings daemon (3.4.2) it actually suspend or blank the screen on user set time plus the dim time, which added additional 30 secs by default. -In some OEM projects, in order to fulfill the OEM requests for Energy + In some OEM projects, in order to fulfill the OEM requests for Energy Star standard, the dim time is set to 5 minutes default
[Bug 1055874] Re: Automatic sleep settings are not followed precisely
** Description changed: [Impact] - * User can choose the suspend time and blank time in the gnome control - center (system settings). + According to the current design in Ubuntu Precise, users can choose the + suspend time and blank time in the gnome control center (system + settings). However, there's another gsetting called org.gnome.settings- + daemon.plugins.power idle-dim-time which controls the screen dim time. + The default value of idle-dim-time in Ubuntu is 30 secs and this makes + the screen dim after idle for 30 secs. This part (idle-dim-time) is not + accessible to users in the default UI but can only be accessed by using + the CLI. - Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. - (which the value user can not adjust in the default UI but only using the CLI) - - This two categories of values (dim time/suspendblank time) should - not be related at all, however,the current Ubuntu Precise (12.04)'s +This two categories of values (dim time/suspendblank time) should + not be related at all, however, the current Ubuntu Precise (12.04)'s gnome settings daemon (3.4.2) it actually suspend or blank the screen on user set time plus the dim time, which added additional 30 secs by - default. + default. Since dim time is not accessible by users in default UI, this + confusing users why extra 30 secs is added to the total time on top of + the selected suspend/blank time. - In some OEM projects, in order to fulfill the OEM requests for Energy +In some OEM projects, in order to fulfill the OEM requests for Energy Star standard, the dim time is set to 5 minutes default (instead of 30 secs), and this make the suspend time and screen blank time very inaccurate, because user will have additional 5 minutes to wait before the screen blank or system suspend. (Inactive time to suspend is about 5 minutes more than setting.) * User do not need modify anything for this patch. [Test Case] * Please use Ubuntu Precise (12.04) to test, this issue is already fixed in Ubuntu Raring (13.04) * Set idle-dim-time to 300 first (5 minutes), it's much easier to find out this issue. (the default is 30 secs and it's somehow not as easy to observe, but the result should be same.) Command: #gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time 300 *In settings: Turn screen off: 10 minutes Suspend: 10 minutes on battery power, 30 minutes when plugged in. Actual: On battery: Screen turned off after 10 minutes, suspend after about 5 more minutes(15 minutes total). When plugged in: Screen turned off after 10 minutes, suspend after about 25 more minutes(35 minutes total). Steps: 1. Check power settings and brightness settings 2. Leave the system inactive Expected results: Inactive time to suspend is same as setting Actual results: Inactive time to suspend is about 5 minutes more than setting [Regression Potential] * This do not need to modify any user settings. * The impact should be minimal for an inaccurate timing of suspend/blanking. [Other Info] Original bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely To manage notifications about this bug go to:
[Bug 1172692] Re: Please implement in-kernel suspend to both
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172692 Title: Please implement in-kernel suspend to both To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1172692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
** Description changed: + + Precise SRU info: + + [Impact] + + * The patch provide a fix to provide the x-canonical-private- + synchronous to work with notifications different with + LAYOUT_ICON_INDICATOR layout. Currently the x-canonical-private- + synchronous interface only provide this layout to support brightness + and volume control. + + [Test Case] + + * This patch make following command behave correctly. + + #notify-send -h string:x-canonical-private-synchronous:1 wireless + disable -i notification-network-wireless-none ; sleep 1 ; notify-send + -h string:x-canonical-private-synchronous:1 bluetooth enable -i + bluetooth + + In current implementation, both Summary and Body text didn't get + updated. + + [Regression Potential] + + * The risk should be minimal, the patch should only affect x + -canonical-private-synchronous interface. This interface is only used + in brightness and volume hotkey, and layout is different. + + * The patch is already tested in OEM projects. + + [Other Info] + + *** Original bug description: + When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. - As an example: - while true; do - notify-send first title first subtitle -i dialog-info -h string:x-canonical-private-synchronous:test - sleep 1 - notify-send second title second subtitle -i dialog-error -h string:x-canonical-private-synchronous:test - sleep 1 + notify-send first title first subtitle -i dialog-info -h string:x-canonical-private-synchronous:test + sleep 1 + notify-send second title second subtitle -i dialog-error -h string:x-canonical-private-synchronous:test + sleep 1 done - If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain - DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION=Ubuntu 9.04 - Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon - A library that sends desktop notifications to a notification daemon, as - defined in the Desktop Notifications spec. These notifications can be - used to inform the user about an event or display some form of - information without getting in the user's way. - . - This package contains the binary which sends the notification. + A library that sends desktop notifications to a notification daemon, as + defined in the Desktop Notifications spec. These notifications can be + used to inform the user about an event or display some form of + information without getting in the user's way. + . + This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244065] Re: Add more options to the power settings menu
** Description changed: - Some Canonical OEM partners have requested additional options be added - to the power option system sleep settings menu. + [Impact] + + * Currently, the power option system sleep settings menu in Ubuntu precise has the following options: +5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. + +The plan is to add an option for 20 minutes and 2 hours options to + give the user morefine-grained controls. + + This request came from OEM projects, requested additional options to be + add in the power option system sleep settings menu. + + [Test Case] + + * Under the session-indicator choose System Settings +-- Power + + * For the Susend when inactive for question, +this patch will add two 20 minutes and 2 hours items + + * The strings in this patch is being translated automatically. + + [Regression Potential] + + * This patch will not change the user's originall settings, only add additional options when user want to choose different suspend time. + * This patch is already tested on some OEM projects. + * The patch now submitted in Trusty (14.04) bzr devel branch. + + [Other Info] https://launchpad.net/bugs/1238727 - - Currently, the power option system sleep settings menu has the following options: - 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. - - The plan is to add an option for 20 minutes and 2 hours options to give - the user more fine-grained controls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1244065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244065] [NEW] Add more options to the power settings menu
Public bug reported: Some Canonical OEM partners have requested additional options be added to the power option system sleep settings menu. https://launchpad.net/bugs/1238727 Currently, the power option system sleep settings menu has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user more fine-grained controls. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244065] Re: Add more options to the power settings menu
** Patch added: oem-power-suspend-options.patch https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+attachment/3889368/+files/oem-power-suspend-options.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
** Changed in: notify-osd (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
Patch included, the patch provide a fix to provide the x-canonical-private-synchronous to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the x-canonical-private-synchronous interface only provide this layout to support brightness and volume control. This patch make following command behave correctly. #notify-send RF-status enabled -h string:x-canonical-private-synchronous:1 -h string:image_path:/tmp/test.jpg Canonical OEM projects need this function to * enable OSD for enable/disable WiFi or bluetooth with a hotkey * enable OSD for display switching with a hotkey For more details, see: https://bugs.launchpad.net/bugs/1213507 https://bugs.launchpad.net/bugs/1213508 ** Patch added: notify-osd-lp404658.patch https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+attachment/3889403/+files/notify-osd-lp404658.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244065] Re: Add more options to the power settings menu
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1244065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404658] Re: notification summary doesn't change for synchronous messages
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951000] Re: disable guest session screen lock using gsettings
Since gconf is deprecated, could we just modify /usr/sbin/guest-account , add an autostart script in the guest $HOME/.config/autostart/ and let gsettings set the correct default value for disable-lock-screen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951000] Re: disable guest session screen lock using gsettings
And also set X-GNOME-Autostart-Phase=Initialization so the menu will not have the entry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156888] Re: [Lenovo E330, b580, b90]: Accelerometer is not working
** Tags added: lexington-lab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156888 Title: [Lenovo E330, b580, b90]: Accelerometer is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1151381] Re: HP Mini 200 - system hangs booting installer
** Tags removed: taipie-lab ** Tags added: taipei-lab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1151381 Title: HP Mini 200 - system hangs booting installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1132683] Re: Asus X201E unable to boot 12.04.2 installer
** Tags added: taipei-lab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1132683 Title: Asus X201E unable to boot 12.04.2 installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1132683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075050] Re: [Dell E6530] Precise installer can't boot to desktop without nomodeset
** Tags added: 201201-10339 taipei-lab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075050 Title: [Dell E6530] Precise installer can't boot to desktop without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1075050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154457] Re: No display after Precise installation finished.
Hi Robert, kern.log is attached. ** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154457/+attachment/3597887/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154457 Title: No display after Precise installation finished. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080514] Re: Click-and-drag in eye of gnome crashes X
check with fglrx 13.3 beta didn't fix the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1080514 Title: Click-and-drag in eye of gnome crashes X To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1080514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152484] Re: system fails suspend_30_cycles
As confirmed by Ivan, removing blocks-hwcert tags. ** Tags removed: blocks-hwcert blocks-hwcert-enablement -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152484 Title: system fails suspend_30_cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153930] Re: fwts reports high failure: Out of range string index 0x06 while accessing entry 'Portable Battery'
** Tags added: 201209-11786 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153930 Title: fwts reports high failure: Out of range string index 0x06 while accessing entry 'Portable Battery' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1134195] Re: System fails to resume from suspend ONLY when suspended by closing lid
This bug is fixed with fglrx-experimental-12.100-0ubuntu0.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134195 Title: System fails to resume from suspend ONLY when suspended by closing lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1134195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158125] [NEW] fwts_test reports high falures
Public bug reported: fwts_results.log is attached. 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: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1553 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49' Mixer name : 'IDT 92HD93BXX' Components : 'HDA:111d76df,1028053f,00100203' Controls : 20 Simple ctrls : 10 Date: Wed Mar 20 22:53:53 2013 HibernationDevice: RESUME=UUID=d764ac7b-d914-4ca3-804c-47b3fd11c5f5 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Precision M6700 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=28ea201f-e1b7-497c-afd1-0406dc3b4e97 ro quiet splash initcall_debug 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 011BL2 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/03/2012:svnDellInc.:pnPrecisionM6700:pvr01:rvnDellInc.:rn011BL2:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M6700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Firmware Test Suite Bug Team (firmware-bug-team) Status: New ** Tags: 201205-114042 amd64 apport-bug precise qa-kernel-lts-testing running-unity taipei-lab ** Attachment added: fwts_results.log https://bugs.launchpad.net/bugs/1158125/+attachment/3587270/+files/fwts_results.log ** Changed in: linux (Ubuntu) Assignee: Daniel Malcher (firmware) = (unassigned) ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Firmware Test Suite Bug Team (firmware-bug-team) ** Tags added: 201205-114042 taipei-lab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158125 Title: fwts_test reports high falures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158129] [NEW] fwts_test reports high falures for hibernation/suspend test
Public bug reported: hibernate_30_cycles.log is attached. 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: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1553 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49' Mixer name : 'IDT 92HD93BXX' Components : 'HDA:111d76df,1028053f,00100203' Controls : 20 Simple ctrls : 10 Date: Thu Mar 21 01:40:07 2013 HibernationDevice: RESUME=UUID=d764ac7b-d914-4ca3-804c-47b3fd11c5f5 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Dell Inc. Precision M6700 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=28ea201f-e1b7-497c-afd1-0406dc3b4e97 ro quiet splash initcall_debug 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 011BL2 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/03/2012:svnDellInc.:pnPrecisionM6700:pvr01:rvnDellInc.:rn011BL2:rvrX03:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M6700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Firmware Test Suite Bug Team (firmware-bug-team) Status: New ** Tags: 201205-11042 amd64 apport-bug precise qa-kernel-lts-testing running-unity taipei-lab ** Attachment added: hibernate_30_cycles.log https://bugs.launchpad.net/bugs/1158129/+attachment/3587315/+files/hibernate_30_cycles.log ** Summary changed: - fwts_test reports high falures for hibernation test + fwts_test reports high falures for hibernation/suspend test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158129 Title: fwts_test reports high falures for hibernation/suspend test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158129] Re: fwts_test reports high falures for hibernation/suspend test
** Attachment added: suspend_30_cycles.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158129/+attachment/3587350/+files/suspend_30_cycles.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158129 Title: fwts_test reports high falures for hibernation/suspend test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
