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
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
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:
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
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
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
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
** 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
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
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
$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
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
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
** 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
** 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
@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
@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
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:
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
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
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
@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
@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
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,
@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,
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
@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
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:
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
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
** 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
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
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
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
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:
@ 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
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
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
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]:
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
40 matches
Mail list logo
