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 n
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 Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/815996
Title:
Desktop occasionally freezes/loc
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
$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
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 Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.
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
** 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 r
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 Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/951000
Title:
disable guest session
@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
@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
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 Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/95100
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 L
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 Deskt
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-sc
** 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 memb
tammy: the public bug suggests catalyst 13.2 beta works
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 Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/b
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 scr
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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net
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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/948347
Title:
[xsettings]: gnome-s
@ ebastien Bacher, the timestamp was after OOBE.
No manually stop/restart was done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/948347
Title:
[xsettings]: gnome-setti
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:Ju
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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/9483
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
23 matches
Mail list logo
