Not an issue here on my optimus laptop (slightly aged as latest laptop
is nvidia only
$ uname -a && xrandr --verbose |grep PRIME && sudo cat
/sys/module/nvidia_drm/parameters/modeset
Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep
10 12:50:22 UTC 2020 x86_64 x86_6
Unfortunately the HWE deal doesn't include libva or the vaapi driver.
Users will have to acquire themselves or from a ppa.
Why no idea, maybe saves 'resources'
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https:/
Public bug reported:
There are 4 possibly problem points, placement, names, tooltips, help.
The 1st 3 are somewhat linked.
The new profile, NVIDIA On-Demand is currently placed between the 2 previous &
historical ones of NVIDIA.. & Intel..
The placement and name could lead one to believe that it
ii screen-resolution-extra0.17.4 all Extension for the
GNOME screen resolution applet
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA settings won't
What one would see from terminal (pkexec ls works fine)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in
activate_name_owner
return self.get_name_owner(bus_name)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owne
Public bug reported:
Test case:
Fresh 19.04 daily current image, updated
Log in to a wayland session, open a single tesxt file in gedit
Move cursor out of gedit window or close gedit
What happens:
get busy cursor forever. Only way to stop is to either logout or open 2 files
(tabs) in gedit
Pro
The ubuntu package doesn't include needed patch, i.e
0004-Check-the-interface-from-libva-first.patch
Apply that and it'll work fine..
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1
Is a newer intel-vaapi-driver package planed?
(- currently in Debian Sid & does fix the issue in a wayland session..
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1813131
Title:
*** This bug is a duplicate of bug 1719945 ***
https://bugs.launchpad.net/bugs/1719945
** This bug has been marked a duplicate of bug 1719945
Silently fails in Wayland session
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-setting
Currently with hybrid systems a wayland session is presented when nvidia
drivers are in use though the user is logged into wayland using the Intel gpu.
So the fact that while in wayland the user can't use nvidia-settings > prime
profiles to *actually* switch back to the Intel gpu makes this bug
Public bug reported:
currently at version 18.0.0~rc5-1ubuntu1 but libglapi-mesa is at version
18.0.5-0ubuntu0~18.04.1
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libosmesa6 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.t
Re: nvidia-setting
previously with alternatives lightdm could affect switch on a og out/in,
however gdm3 needed a reboot.
The message was never changed to reflect this, now that apparently a reboot is
required no matter what dm it would be a good time to edit it.
Old bug - https://bugs.launchpad.
18.04 should really get the new driver, whether it's easier to do before or
after release I don't know but it should be done.
For some reason Debian hasn't added it yet but that shouldn't stop Ubuntu from
doing so.
In addition to bug symptoms there are other advantages to going to 2.1. For
examp
Not affected at all here with Haswell, i.e.
CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19155
clock speeds: max: 3400 MHz 1: 2394 MHz 2: 2394 MHz 3: 2394 MHz 4:
2394 MHz 5: 2394 MHz 6: 2394 M
Public bug reported:
Linking to libmir* seems to be of no value & is a roadblock to some things, ex.
chromecast support in vlc.
Myself see no change when mesa is not patched for mir, if there is no value
anymore then please remove from build.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package
RE: llvm-toolchain-5.0
Works fine here in 16.04.x, no issues, would be great to see it leave proposed
asap.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1716203
Title:
Backport packages for
Sorry, forgot that I don't use wayland in practice as it's not close to ready
but should when testing.
To note: this doesn't occur in a gnome session where the context menu is opened
inside the header bar so maybe add ubuntu-session.
--
You received this bug notification because you are a membe
On 10/08/2017 05:11 AM, Yuriy Padlyak wrote:
> After python-minimal installation and switching to intel the suggested
> relogin doesn't work. I've tried reboot, but now the setting doesn't start
> again. This time with a different error:
> ERROR: The control display is undefined; please run `nvid
Ok, fresh install today's image
1. The manifest say python-minimal is included but it's not installed,
$ apt-cache policy python-minimal
python-minimal:
Installed: (none)
Candidate: 2.7.14-2ubuntu1
Version table:
2.7.14-2ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu artful
I wasn't really sure that it really needed the python package, it seems
toneed /usr/bin/python which should have been installed as it's provided by
the python-minimal package.
When nvidia-settings wouldn't start I just installed the python package
which brought in python-minimal, ect.
When I check
going to mark invalid, how this install, (Beta amd64 (20170929) ended up
without python-minimal is unknown.
Could have been from bad behavior from unattended-upgrades.
For historical info it had been removed as seen here when I installed python
Commit Log for Wed Oct 4 17:19:48 2017
Installed
While I can certainly confirm, what is the use case?
It would seem only useful when in a wayland session to switch from the intel
profile to the nvidia one before rebooting to an xorg session. I guess that
could save a little time/effort.
--
You received this bug notification because you are a
** Changed in: nvidia-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1719945
Title:
Silently fails in Wayland session
To manage noti
** Summary changed:
- Cannot open nvidia-settings on pc with a hybrid device (or use prime-select
+ Cannot open nvidia-settings on pc with a hybrid device (or use prime-select),
missing python
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvi
Public bug reported:
You would see -
$ nvidia-settings
** Message: PRIME: Requires offloading
** Message: PRIME: is it supported? yes
** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child
process “/usr/bin/prime-select” (No such file or directory)
Trace/breakpoint trap
Addit
Regarding the mpv in artful:
You can currently get some vaapi support in wayland session, you'd need to use
hwdec=vaapi-copy
Not as effective as hwdec=vaapi but I don't think they'll be changing that
(commit noted), in near future.
--
You received this bug notification because you are a member o
vaapi in mpv in a wayland session was broken due to this commit
https://github.com/mpv-player/mpv/commit/bba08e38ff9842c4edf9da6a1d54066a01acd982
Testing here a reversion to allow, seems ok for at least me to date, as in
https://launchpad.net/~mc3man/+archive/ubuntu/mpv-tests/+files/mpv_2%3A0.25.
xorg-server-hwe-16.04 (2:1.19.3-1ubuntu1~16.04.1) is working fine here (along
with other related or required -proposed packages listed here.
Additionally with a modification to
/etc/modprobe.d/nvidia-graphics-drivers.conf to enable KMS PRIME
Synchronization is working on my hybrid (optimus) m
Ot to FFe
Bug filed regarding PRIME synchronization with hybrid hardware implemented via
nvidia-prime
Bug 1674304
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1671799
Title:
FFe: xser
Seems ok on both
Intel+NVIDIA hybrid Haswell + NVIDIA GK107M [GeForce GT 755M]
Intel+NVIDIA hybrid Ivybridge + NVIDIA GK107M [GeForce GT 660M]
Though both show an oddity in inxi reporting when on Intel with nvidia drivers
not installed -
Ex.,
intel xserver not installed, no nvidia drivers inst
On 03/16/2017 07:20 AM, Timo Aaltonen wrote:
> 1.19.3-1u0.1 uploaded, please test
>
Does indeed resolve issue when nvidia drivers are not installed.
(out of the scope of this FFe, many optimus users will be expecting
prime synchronization to work. At least here it doesn't when using
nvidia drive
Pretty simple here -
Will only successfully boot to greeter, ect. when nvidia drivers are installed.
If the drivers aren't installed then it either 'hangs' right after the fs check
on sandybridge or goes to low graphics pop up on haswell.
Once the nvidia drivers are installed then boot ups work
Same thing with a lenovo IdeaPad Y580 (sandybridge) except there it
doesn't even make it the low graphic pop up.
In both cases (sandybridge & previous laptop which is haswell) if I install the
nvidia drivers & reboot, it does boot up to an ubuntu session. From there
switching via prime profiles
Here with fresh 17.04 Ubuntu install using today's image -
After adding ppa & upgrading a reboot goes to low graphics screen.
This is on a Lenovo IdeaPad Y510P, nvidia drivers not installed.
Logs seem unremarkable, only way to boot to ubuntu session is thru recovery
(nomodeset
--
You received t
That seems a poor choice as modesetting would prevent users from setting
Intel to use a tearfree option to eliminate tearing when using the Nvidia
drivers
On Sep 29, 2016 4:55 PM, "Vassil Peytchev"
wrote:
> This happened on my Dell M3800 with the Optimus Nvidia GPU and nvidia-
> prime when updat
*** This bug is a duplicate of bug 1610476 ***
https://bugs.launchpad.net/bugs/1610476
** This bug has been marked a duplicate of bug 1610476
booting with nvidia drivers via nvidia-prime results in no display in 14.04.5
--
You received this bug notification because you are a member of Ubu
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1591714
Title:
Why no VAProfileVP9Profile* in libva
To manage notifications about this bug go to:
https://bug
Hmm, sorry about this (I think
A number of users were complaining about this but it turns out it was more
about cursor movement than clicks
(or so combo of the cursor moving then a click on new position after timeout.
In any event it was never intended to prevent cursor movement while typing
So
** Description changed:
- It's no longer working by default nor can it be enabled thru syndaemon.
- It does appear it can be enabled thru libinput (xserver-xorg-input-libinput),
(not default installed), however System Settings > Mouse & Touchpad does not
interface with xserver-xorg-input-libin
** Also affects: unity-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1576685
Title:
Disable touchpad
Public bug reported:
It's no longer working by default nor can it be enabled thru syndaemon.
It does appear it can be enabled thru libinput (xserver-xorg-input-libinput),
(not default installed), however System Settings > Mouse & Touchpad does not
interface with xserver-xorg-input-libinput so
** Tags added: trusty-lts-wily
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in non gnome sessions when using nvidia drivers via
nvidia-prime until sc
I would think this mis-reported issue will also be going on with 14.04.4 lts
which will not include the so-called ubuntu-drivers-common 'fix'
If interested on what really is occurring on optimus laptop & nvidia-prime see
here -
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug
Sorry to report that see same crash with the patch
Tried with both ubuntu & gnome sessions. (shouldn't matter & didn't but
recent mesa issue makes me test both just in case.
On 01/14/2016 01:19 PM, Robert Hooker wrote:
> Chris Wilson from Intel has passed along a patch that may fix it and
> asked
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1532343
Title:
Xorg crashed with SIGABRT in draw_curre
** Changed in: xorg-server (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1528667
Title:
Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
T
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in non gnome sessions when using nvidia drivers via
nvidia-prime until screen goes
Well then hopefully you can get it so this change to modesetting can be
reverted & one isn't forced to get screen to sleep then awake.
My whole point was that this report is claiming that the switch from Intel to
Nvidia fails which is not true is any respect.
It's purely a matter of no visible
** Summary changed:
- No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
+ No visible display in non gnome sessions when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
--
You received this b
Not really fixed so opening again
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: lightdm (Ubuntu)
Status: Invalid => Confirmed
** Changed in: xorg-server (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notifica
A "regression in the intel driver" doesn't seem to explain why this was not an
issue in a gnome session, nor to the fact that -
xset dpms force off
xset dpms force on
returned display both in greeter & session
(and nvidia driver loaded & worked fine, with or without a visible display.
you
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Triaged => Invalid
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Invalid
** Changed in: unity-greeter (Ubuntu)
Status: Confir
** Tags added: lubuntu xubuntu
** Tags removed: amd64
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when using nvidia drivers via
n
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when using
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when u
Demonstration 2
If the autostart script was in place then disable
Alter the sleep time of unity-greeter from 300 to 6 (sec) in
/usr/share/glib-2.0/schemas/com.canonical.unity-greeter.gschema.xml
(at bottom of file, assumes 6 sec is enough time to enter password, if not
increase 6 to something su
** Description changed:
- Please note that this bug is being filed on a recent 15.10 Ubuntu image
- install but from a gnome session
+ ** this appears to be that the display is blanked/asleep at greeter & login.
+ Forcing or waiting for screen to blank/sleep then waking up restores display
+ See c
Also affects Xubuntu
** Also affects: xfce4-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visi
What happens in an ubuntu session is -
After logging in, no display. If the session is left inactive until display is
put to sleep, then awakining it thru keyboard or mouse brings back a visible
display. (default is 5 min. of inactivity
A simple startup script via startup applications demons
** Summary changed:
- No visible display in ubuntu session when using nvidia drivers via
nvidia-prime
+ No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
** Description changed:
Please note that this bug is being filed o
Installed fine in 14.04.3 (using hwe vivid stack), both the lib & -dev packages
Also allowed desmume to install & open
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Ex. of stdout from playing a vid in cli player in an ubuntu session with
nvidia(vdpau), no errors
(obviously I only here sound as there is no visible display
Playing: 1.mp4
(+) Video --vid=1 (*) (h264)
(+) Audio --aid=1 --alang=und (*) (aac)
AO: [pulse] 44100Hz stereo 2ch float
Using hardware d
journalctl from an ubuntu session
** Attachment added: "no-display-journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479223/+files/no-display-journalctl.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
Public bug reported:
Please note that this bug is being filed on a recent 15.10 Ubuntu image
install but from a gnome session
In a nutshell -
Once nividia drivers are installed & used from nvidia-prime there is no longer
a visible display in unity-greeter nor in an ubuntu session once logged in
glxinfo log from an ubuntu session
** Attachment added: "glxinfo.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479226/+files/glxinfo.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ub
journalctl from a gnome session
** Attachment added: "gnome-journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479224/+files/gnome-journalctl.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
gpu-manager log from an ubuntu session
** Attachment added: "gpu-manager-ubuntu.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479225/+files/gpu-manager-ubuntu.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
"Anyone know of a workaround for this?"
Do a fresh install using the 14.04.1 image from Ubuntu old-releases.
If needing for some reason a newer mesa then use a ppa like xorg-edgers fresh X
crack or oibaf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscri
Sorry - 1st. link should have been - Bug #1475038
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1479524
Title:
Totem Crashes at launch from missing libwayland-egl
To manage notifications about
reported this several weeks ago, seems no real progress though certain dev's
were aware -
Bug #1478419
Also affects gnome-shell, gnome-shell extensions, (runtime) & causes FTBFS for
totem & gnome-shell
(because there is no libegl1-mesa-drivers lts version
Bug #1478419
Bug #1478420
--
You rece
nvidia-graphics-drivers-346-updates installs fine with the lts-vivid
kernel
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.n
This will cause an issue with 14.04.3 unless -
either fix 331.xxx or make 340.xxx or 346.xxx available in 14.04.
304.xxx is not suitable for use on Nvidia mobile chips so please address before
releasing 14.04.3
** Tags added: lts-vivid
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1424466 ***
https://bugs.launchpad.net/bugs/1424466
** This bug has been marked a duplicate of bug 1424466
Devel package not installable in 14.04.2 (mesa-lts-utopic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
Tested with -proposed enabled a number of apt-get sims, all looked good.
freeglut3-dev
libglew-dev
libsdl1.2-dev
libsdl2-dev
So will mark verification-done & dupe related bugs that will be fixed.
There still are a few cases open, one is obscure enough not to warrant a
look? (osmesa is not built
And possibly -
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1428972
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1429529
Title:
Unsolvable LTSEnablementStack Mesa packa
To a lesser extent -
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1429529
Title:
Unsolvable LTSEnablementStack Mesa pack
There seems to be quite a number of devel packages that can't be installed or
installed via normal means.
Maybe can be considered dupes of this bug -
https://bugs.launchpad.net/ubuntu/+source/freeglut/+bug/1424466
https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1429464
https://bugs.launchpad.
I meant 1.16.x & 2.99.914-1~exp1ubuntu2/3
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bu
fixed with latest xserver* 1.0.11
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1357746
Title:
Compiz fails to load with xserver-xorg-video-intel
2:2.99.914-1~exp1ubuntu1
If I either blacklist nouveau or remove the xserver-xorg-video-nouveau package
then everything works as expected with the current xserver-xorg-video-intel
package.
This also *seems* to make restarts & shutdowns more reliable & makes going to a
tty not be liable to cause some sort of looping kern
** Also affects: nouveau
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1357746
Title:
Compiz fails to load with xserver-xorg-vid
To clear up -
1. This bug was filed by running apport -cli from a tty, saving the report,
then filing that report from a recovery boot
(if there is a better way to use apport from a tty tell me.
2. The kernel version is *irrelevant*, compiz fails with any kernel inc.
going back to 3.13.x when x
** Description changed:
Logs into a session with
black desktop
no unity panel
a non functional launcher
Nothing can be done in the session except go to a tty
If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then
- all is well & unity loads as expected
+ all is we
Can also be noted that a gnome-flashback > compiz session is likewise affected
though the symptoms are slightly different
(- nothing happens for a while, then booted back to greeter.
It also returns to expected with a downgraded xserver-xorg-video-intel package
If there is any specific means to p
*** This bug is a duplicate of bug 1357746 ***
https://bugs.launchpad.net/bugs/1357746
** This bug has been marked a duplicate of bug 1357746
unity fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- 2:2.99.914-1~exp1ubuntu1 breaks 3d support on some intel hardware
+ 2:2.99.914-1~exp1ubuntu1 breaks unity on some intel hardware
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
w
** Description changed:
- With 2:2.99.914-1~exp1ubuntu1 a normal boot produces a login where -
+ With 2:2.99.914-1~exp1ubuntu1 a normal boot produces a login where -
black desktop background
no unity panel
a non-functional launcher
+ nothing can be done
- If I boot to recovery > resume t
After downgrading & restarting, normal boot -
~$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.0 Mesa 10.2.5
Not software rendered:yes
Not blacklisted:
Public bug reported:
With 2:2.99.914-1~exp1ubuntu1 a normal boot produces a login where -
black desktop background
no unity panel
a non-functional launcher
If I boot to recovery > resume then do get an ubuntu session but using lvmpipe.
ie.
$ /usr/lib/nux/unity_support_test -p
OpenGL vendor str
re-broken in 14.10 with compiz 1:0.9.11+14.10.20140606-0ubuntu1, at least on a
laptop with usb mouse -
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1330198
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://
Bug #1303068
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1200829
Title:
Regression: Enabling typical bindings in "Desktop-based Viewport
Switching" breaks scrollwheel scrolling in
Seems to cause the inability to focus Desktop once any window is open.
Immediate affect is the inability to rename a file on the Desktop if a window
is open
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.laun
Thanks Chris for sticking it out. 2babacea-bab0-11e3-9cee-002481e91f22
is working well here in a short term test & resolves this & the other
open bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.n
excellent, resolved here issues seen on Intel, now only returning FB
configs that have visuals -
Getting matching framebuffer configs
Found 8 matching FB configs.
Getting XVisualInfos
fbconfig id: 0x8a
Chosen visual ID = 0xb0
fbconfig id: 0x8c
Chosen visual ID = 0x45
fbconfig id: 0x90
Chosen visua
Tried for a day plus on 2 laptops to reproduce this bug on fresh 13.10 release
installs & *can not* cause it to happen.
Then updated fully & still it does not occur.
After all that did go ahead & upgrade xserver-xorg-core/common from
-proposed, see no regressions from it.
So from here the upgrad
On 12/19/2013 08:36 AM, Timo Aaltonen wrote:
> Doug, please test if the update fixes it for you.
>
Tim - I was hoping someone who was using 13.10 & affected would test.
Seeing as that's not happening I'll put up a new 13.10 release install & -
See if the invisible cursor behavior happens.
If so,
I may be mis-interpreting this, - if so sorry
While the xorg dev (Peter Hutterer) did comment, "both merged, thanks.",
(http://lists.x.org/archives/xorg-devel/2013-November/039228.html),don't
see that they were yet thru 1.14.5
In the upstream bug he seems to be asking for a test case of the
On 12/05/2013 03:39 AM, Sebastien Bacher wrote:
> Thanks for confirming Doug, I was a bit unsure how to test that one
> since I never ran into it (is it specific to laptops/touchpads?). In any
> case keep looking for it but it's looking good ;-)
>
It could be specific to laptops, here that's all I
Fix appears to be working fine here on 14.04, tested over the day thru numerous
restarts & log out/ins
(though 14.04 wasn't as susceptible as 13.10 for whatever reason
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https
Chris - I opened here newly described,
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257004
(new updated install, defaults only for compiz
added a couple of folders to Desktop *prior* to replacing
xserver-xorg-core/common
After upgrade/restart the existing folders open fine
Any newl
1 - 100 of 220 matches
Mail list logo