[Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
Issue has been verified on one Dell platform. Tried open/close lid to suspend and resume for more than 20 times, cannot re-produce the issue. Since the HW has not yet been shipped, more details please see https://bugs.launchpad.net/somerville/+bug/1466441/comments/53 -- 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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
As lp:1432910 is closed, no longer affect oem-priority ** No longer affects: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1456455] [NEW] Fail to install KH OSP1 base image
Public bug reported: Fail to install OSP1 base image on Miramar [Steps to re-produce] 1. Boot the system with live USB Expected result: Can boot and start installation Actual result: First, it shows errors of i915_bpo followed by a lot of CPU stuck errors. ** Affects: ubuntu Importance: Undecided Status: Invalid ** Changed in: ubuntu Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1456455 Title: Fail to install KH OSP1 base image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1456455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354459] Re: kernel crash power 8 bare metal
please retest with neihu 140919-1 or later image which uses kernel 3.13.0-36.63+hwe3 ** Tags added: bdw-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354459 Title: kernel crash power 8 bare metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] [NEW] [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
Public bug reported: Running the proprietary nvidia drivers in an Optimus config works (Intel+NVIDIA) can discover two issues: 1. Cannot adjust brightness in the guest session (private bug #1290694) [Test Case] * Switch to guest session and adjust brightness from settings or hotkey or command line - Expected: Can adjust the brightness - Bad behavior: Cannot adjust brightness 2. Black screen while changing the resolution (private bug #1285062) but switching to the guest session results in a black screen. [Test Case] * Go to display setting, set rotation to counterclockwise/clockwise/180 degrees and click apply - Expected results: Can switch display rotation successfully - Actual results: Black screen when switching display rotation ** Affects: nvidia Importance: Undecided Status: New ** Affects: oem-priority Importance: High Assignee: OEM Priority Team (oem-priority) Status: New ** Affects: xorg-server-lts-saucy (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/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
The package mentioned in comment #1 ** Attachment added: nvidia-prime_0.5~hybrid0.0.3stella1_amd64.deb https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-saucy/+bug/1326257/+attachment/4125161/+files/nvidia-prime_0.5%7Ehybrid0.0.3stella1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
Alberto has provided a fix in nvidia-prime to change xorg*.template from Driver modesetting to Driver intel and add Option AccelMethod UXA The modified testing package is attached. With the update of xorg-server for bug #1322212, this nvidia-prime package can pass all OEM QA tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: nvidia Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) = OEM Priority Team (oem-priority) ** 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/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676166] Re: Unity Launcher corruption when resuming from suspend/hibernate
For the symptom I mentioned in comment #104, it is found a Nvidia issue. Please check https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331/+bug/1210077 Close oem-priority task ** No longer affects: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676166 Title: Unity Launcher corruption when resuming from suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/676166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676166] Re: Unity Launcher corruption when resuming from suspend/hibernate
The issue can still be re-produced with Nvidia prime driver 331.20, private bug reported as lp:1278294, corresponding to Nvidia bug #1464852. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676166 Title: Unity Launcher corruption when resuming from suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/676166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676166] Re: Unity Launcher corruption when resuming from suspend/hibernate
$uname -r Linux u-HP-ENVY-15-Notebook-PC 3.11.0-17-generic #31~precise1-Ubuntu SMP Tue Feb 4 21:25:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $dpkg -l | grep unity ii unity 5.20.0-0ubuntu3 $lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05) 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05) 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5) 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5) 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5) 00:1c.6 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 [8086:8c1c] (rev d5) 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05) 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller [8086:8c4b] (rev 05) 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05) 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05) 01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1391] (rev a2) 07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter [10ec:8179] (rev 01) 09:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5227] (rev 01) 0f:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676166 Title: Unity Launcher corruption when resuming from suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/676166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282796] Re: prime-xconfig can write an invalid BusID string
Apply the patch (attach the testing package) and it works on Mondavi machine (BusID 0a:00.0 Nvidia GT840M is used). ** Attachment added: nvidia-prime_0.5~hybrid0.0.2ubuntu1_amd64.deb https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+attachment/3989149/+files/nvidia-prime_0.5%7Ehybrid0.0.2ubuntu1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282796 Title: prime-xconfig can write an invalid BusID string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273924] Re: [Dell Precision T1700] CRITICAL / HIGH failures found in fwts report
The status Invalid was wrongly set by a script, sorry for any inconvenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273924 Title: [Dell Precision T1700] CRITICAL / HIGH failures found in fwts report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1273924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273924] Re: [Dell Precision T1700] CRITICAL / HIGH failures found in fwts report
** Changed in: linux-lts-raring (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273924 Title: [Dell Precision T1700] CRITICAL / HIGH failures found in fwts report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1273924/+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
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = High ** Changed in: oem-priority/precise 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/1055874 Title: Automatic sleep settings are not followed precisely To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1055874/+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
@Ara, No, I didn't found alt-f1 has a relationship with this bug. Before I touch the screen, everything is normal, alt-f1 can be used, moving cursor to the left side can reveal the launcher. After I touch the screen, alt-f1 can still be used to reveal the launcher. However, moving cursor to the left side no longer works. This is consistent to what we found at the beginning, the launcher can reveal via hotkeys but not via touchpad. -- 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 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
@Stephen, Many thanks for your reply. Sorry my description maybe a bit mis-leading, this is not a single-touch bug, but a possible Unity bug that touchpad cannot reveal launcher if a left-click event happens via touch-screen. Some more information for your reference: 1. This does not happen under Unity2D but only Unity3D 2. Windows hotkey still works, so the launcher can be called via hotkey 3. When issue occurs, unity --replace or compiz --replace cannot recover it. I only found restart lightdm (restart X) can recover the issue 4. No error occurs from $export UNITY_LOG_SEVERITY==DEBUG;nux=DEBUG $unity --replace 5. If I touch the screen before setting launcher to auso-hide mode, touchpad or external mouse still cannot reveal the launcher after autohide is selected. Extra information which may not relate to this issue directly: The position of touchpad pointer and touch screen pointer do not sync with each other. For example, if I move the pointer to place A via touchpad, then touch place B on the screen, then tried to move pointer via touchpad, the pointer appears at place A instead of place B. -- 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 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
We are using Precise 12.04.2 with unity 5.20.0-0ubuntu2 unity-2d 5.14.0-0ubuntu1 compiz 1:0.9.7.12-0ubuntu2 and kernel 3.5.0-40-generic -- 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 1223739] [NEW] Launcher - unable to reveal Launcher under autohide after using the touch screen
Public bug reported: To Reproduce: 1. Set the Launcher to autohide 2. On any system (have tried on some Dell systems and some HP systems) which supports single touch 3. Touch the screen and try to move cursor to show launcher Expected result: Launcher can reveal Actual result: Launcher cannot reveal Additional information: 1. When the issue happens, can press window key to show dash and launcher, but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover ** Affects: unity (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/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/ubuntu/+source/unity/+bug/1223739/+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
Private bug #1220990 is a duplicate of this one. -- 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 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
Attach kern.log, syslog, Xorg.0.log, dmesg Nothing has changes in these logs after the issue occurs. Nothing has been observed in .xsession-errors, too ** Attachment added: after_make_touch.tar.gz https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1223739/+attachment/3814767/+files/after_make_touch.tar.gz ** 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/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 1198846] Re: [efi boot to unexpected media] plug in live usb and DVD at the same time, try to boot from DVD but it comes to usb
@Phillip, Sorry, the original description might be a little bit misleading. Yes, we were taling about an old release on the recovery partition and a new release in the dvd. What we found is, user can never boot into the new release in the dvd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198846 Title: [efi boot to unexpected media] plug in live usb and DVD at the same time, try to boot from DVD but it comes to usb To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1198846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198846] Re: [efi boot to unexpected media] plug in live usb and DVD at the same time, try to boot from DVD but it comes to usb
@Phillip, This actually affects users when there is a partition on hard driver with install image (for recovery use for example). If deleting this partition is not an option, user can never boot into CDROM. I think it will be great if efi grub application can be able to know which partition/media it is on (maybe from BIOS information) and find the grub.cfg on the same partition to avoid doing search. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198846 Title: [efi boot to unexpected media] plug in live usb and DVD at the same time, try to boot from DVD but it comes to usb To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1198846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198846] Re: [efi boot to unexpected media] plug in live usb and DVD at the same time, try to boot from DVD but it comes to usb
Private bug which affects Ubuntu-recovery : bug #1185375 ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise 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/1198846 Title: [efi boot to unexpected media] plug in live usb and DVD at the same time, try to boot from DVD but it comes to usb To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1198846/+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
@Sebastien, thanks for your reply. I have tried the patch; it works good as expected and I have no issue with it. The reason I tried dbus-launch gsettings set org.gnome.desktop.lockdown disable-lock-screen true was because you commented on our private bug and ask us to try dbus-launch. Therefore, I assumed you still expected my reply. Your patch works perfectly on the machine I tested, but I still hope to understand the reason why dbus-launch gsettings does not work for you. In the old guest-account, it does the following su $USER EOF gconftool-2 --set --type bool /desktop/gnome/lockdown/disable_lock_screen True EOF Since it su to guest user, it is reasonable to me that the gsetting can be set properly for guest user, and that is also what I see when I made tests to use dbus-launch gsettings. I will be very happy to know what kind of difference causes dbus-launch gsettings not function in your side but my side. -- 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
Yep, that answers my question and I totally agree the final approach is more reliable! Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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
@Sebastien, what do you mean it doesn't work in guest-account script? I did add it into guest-account script to replace gconf command. The dbus-launch will create a session bus and set disable-lock-screen properly for guest user. I am curious why it doesn't work for you? -- 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
add dbus-launch gsettings set org.gnome.desktop.lockdown disable-lock- screen true works to disable lock-screen option in the menu. -- 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
As Tyson mentioned in comment #28, this is a timing issue that gsettings-data-convert.desktop is executed before gconf value is set for guest session. One of workaround to use gsettings is to put a prefs.sh in /etc/guest- session which does: echo [Desktop Entry]\nType=Application\nName=Disable Lock Screen in Guest Session\nOnlyShowIn=GNOME;Unity;\n\ X-GNOME-Autostart-Phase=Initialization\nTerminal=false\n\ Exec=gsettings set org.gnome.desktop.lockdown disable-lock-screen true\nNoDisplay=true \ $HOME/.config/autostart/disable-lock-screen.desktop chown $USER:$USER $HOME/.config/autostart/* This will make sure the gsettings value of disable-lock-screen can always be true for guest session. ** Attachment added: prefs.sh https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/951000/+attachment/3707106/+files/prefs.sh -- 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
I think gconftool-2 --set --type bool /desktop/gnome/lockdown/disable_lock_screen True in guest-account can be replaced by the script attached in comment #31 or something similar since gconf should be replaced by gsettings. -- 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
** Also affects: lightdm Importance: Undecided Status: New ** No longer affects: lightdm ** Also affects: oem-priority Importance: Undecided Status: New ** 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/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
When the issue happens, I tried to trun gsettings-data-convert --verbose --dry-run, it says Directory '/usr/share/GCong/gsettings' all uptodate, nothing to do However, gconftool-2 --get /desktop/gnome/lockdown/disable_lock_screen (true) and gsettings get org.gnome.desktop.lockdown disable-lock-screen are not consistent (false) are not consistent. -- 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 1080514] Re: Click-and-drag in eye of gnome crashes X
tjaalton tammy: the public bug suggests catalyst 13.2 beta works a16g 13.3 at http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx -- 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 1137247] [NEW] apt-get build-dep removes xserver-xorg-lts-quantal
Public bug reported: The issues occures while trying to install build dependency of fglrx by doing #apt-get build-dep fglrx or #apt-get build-dep fglrx-installer The build dependency of fglrx-installer contains xserver-xorg-dev and it removes xserver-xorg-lts-quantal. This results in black screen during the next boot. If one issue X, then it complains with the following message The program 'X' is currently not installed. You can install it by typing: apt-get install xserver-xorg ProblemType: Package DistroRelease: Ubuntu 12.04.2 Package: fglrx-installer ProcVersionSignature: Ubuntu 3.5.0-25.38~precose1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 Architecture: amd64 Date: Fri Mar 1 01:58:48 EST 2013 DkmsStatus: alsa-hda-lts-quantal, 0.201302210020~precise1, 3.5.0-25-generic, x86_64: installed fglrx, 12.100, 3.5.0-25-generic, x86_64: installed oem-ethernet-r8168-1099650, 1stella3, 3.5.0-25-generic, x86_64: installed oem-input-synapticsled-1098063, 1.0stella2, 3.5.0-25-generic, x86_64: installed rts5229, 1.4stella4, 3.5.0-25-generic, x86_64: installed wmi-kobe, 1.0stella1, 3.5.0-25-generic, x86_64: installed ErrorMessage: The following packages will be REMOVED: libegl1-mesa-drivers-lts-quantal libegl1-mesa-lts-quantal libgbm1-lts-quantal libgl1-mesa-dri-lts-quantal libgl1-mesa-glx-lts-quantal libglapi-mesa-lts-quantal libgles1-mesa-lts-quantal libgles2-mesa-lts-quantal libopenvg1-mesa-lts-quantal libxatracker1-lts-quantal ubuntu-desktop x11-xserver-utils-lts-quantal xorg xserver-common-lts-quantal xserver-xorg-core-lts-quantal xserver-xorg-input-all-lts-quantal xserver-xorg-input-evdev-lts-quantal xserver-xorg-input-mouse-lts-quantal xserver-xorg-input-synaptics-lts-quantal xserver-xorg-input-vmmouse-lts-quantal xserver-xorg-input-wacom-lts-quantal xserver-xorg-lts-quantal xserver-xorg-video-all-lts-quantal xserver-xorg-video-ati-lts-quantal xserver-xorg-video-cirrus-lts-quantal xserver-xorg-video-fbdev-lts-quantal xserver-xorg-video-intel-lts-quantal xserver-xorg-video-mach64-lts-quantal xserver-xorg-video-mga-lts-quantal xserver-xorg-video-modesetting-lts-quantal xserver-xorg-video-neomagic-lts-quantal xserver-xorg-video-nouveau-lts-quantal xserver-xorg-video-openchrome-lts-quantal xserver-xorg-video-r128-lts-quantal xserver-xorg-video-radeon-lts-quantal xserver-xorg-video-s3-lts-quantal xserver-xorg-video-savage-lts-quantal xserver-xorg-video-siliconmotion-lts-quantal xserver-xorg-video-sis-lts-quantal xserver-xorg-video-sisusb-lts-quantal xserver-xorg-video-tdfx-lts-quantal xserver-xorg-video-trident-lts-quantal xserver-xorg-video-vesa-lts-quantal InstallationMedia: Ubuntu 12.04.2 Desktop amd64 MachineType: System manufacturer System Product Name PackageVersion: 2:12.100-0ubuntu1 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=ec503fe6-b48e-4308-b1b1-f67f593c8aca ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer ** Affects: fglrx-installer (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/1137247 Title: apt-get build-dep removes xserver-xorg-lts-quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1137247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
We made some further checks. When OOBE ends and lightdm starts, the gnome-setting-daemon is invoked via lightdm, and soon crashed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
@ ebastien Bacher, the timestamp was after OOBE. No manually stop/restart was done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
Sorry, the previous message was for Sebastien Bacher (S of the first name was missing). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
After installing the package in -proposed, the same error box still pop up in first boot due to gnome-settings-daemon Steps to reproduce: 1. Boot from USB installer and install system on a Cedar Trail machine 2. Complete OOBE and boot into system 3. Wait for 5-10 minutes and observe ./kern.log:Jun 5 10:18:41 ubuntu-desktop kernel: [ 362.707513] gnome- settings-[24692]: segfault at 6 ip b47b76b3 sp bfd25760 error 4 in libxsettings.so[b47b2000+9000] ** Attachment added: /var/crash/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.104.crash https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/948347/+attachment/3176114/+files/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.104.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
Tried gnome-settings-daemon (3.4.2-0ubuntu2) from precise-proposed on a HP cedar-trail model, the error message remains. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/948347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950160] Re: Keyboard function key to switch between monitors no more works
Test g-s-d 3.4.1-0ubuntu1.1kengyu2 in https://launchpad.net/~lexical/+archive/gsd/ PPA on a HP model. Fn+F4 is expected to switch between monitors and it didn't work. Fn+F4 works after installing g-s-d 3.4.1-0ubuntu1.1kengyu2 with the patch Kent-Yu provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950160 Title: Keyboard function key to switch between monitors no more works To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/950160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
