Public bug reported:
On previous versions of Ubuntu, after 5 minutes, my monitor would turn
off as per settings. Since I reinstalled fresh 21.10, this is not
happening. Screen becomes black and stays powered on.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersio
** Branch linked: lp:~gerboland/qtmir/nouveau-workaround
--
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/1553328
Title:
Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
especi
I've an ancient NVidia box at home, can try it out. I'm attaching
patches for qtubuntu/qtmir to force Qt to use single threaded GL on
nouveau.
** Branch linked: lp:~gerboland/qtubuntu/nouveau-workaround
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
Actually, might be easier/more-reliable just to edit /etc/environment
and add "QSG_RENDER_LOOP=basic" and restart.
--
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/1553328
Title:
Mir/Unity8 crashe
I have Qt configured (in QtUbuntu/QtMir) to use multi-threaded GL
rendering, so we're probably hitting Nouveau's limitations here.
As workaround, I can add code to QtUbuntu/QtMir use single-threaded GL
for Nouveau.
If this is easily reproduced, can you try
initctl set-env --global QSG_RENDER_LOO
Probably also relevant: https://bugs.launchpad.net/mir/+bug/1560498
** Tags added: unity8-desktop
--
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/1670717
Title:
Unity8/mir working on VMware due
I've hacked qtmir to print the subpixel hint that Mir is supplying.
http://pastebin.ubuntu.com/24007971/ is my output. First I run a simple
qml demo shell as nested server under USC, get "0" hint.
Then I run again as host server, get a hint "1 = RGB".
The "Subpixel hint" output of the 2 cases do
Just testing it now, AFAICS a nested server is not getting the correct
subpixel data passed to it.
--
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/1393578
Title:
Subpixel order not include
Note it is only Unity8 which is mixing GL and GLES calls, clients are
not doing that. Qt clients are only doing GL calls on desktop.
Nothing obvious comes to mind here.
It may be Qt's EGL configuration code is failing - code that QtUbuntu is
using. Another consumer of that same code is the EGL ba
Of course we will. We need to re-land the fix. It was reverted because
it broke something else, but that's been solved now. Sorry for the
delay, but it takes time to get things done just right.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa
** Also affects: qtubuntu
Importance: Undecided
Status: New
** Changed in: qtubuntu
Status: New => Triaged
** Changed in: qtubuntu
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server i
Adding QtMir as from Qt5.5 and later, the QPA plugin can specify the
subpixel hinting to Qt's font renderer (is part of QPlatformScreen
implementation).
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed in: qtmir
Status: New => Triaged
** Changed in: qtmir
I
arm64? Should it not be using a hybris-based driver instead of mesa?
What hardware is this?
--
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/1585942
Title:
Mesa causes a segmentation fault on arm6
Yep. The branch has been approved, will take a while to get it landed.
Note that it will be almost unusable until bug 1585723 is resolved.
--
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/1549455
T
@Emanuele yes I did - but only via SSH. A colleague will verify it works
visually before approving
--
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/1549455
Title:
Unity8-dash on Intel Atom graphic
I've updated the attached branch with my proposed fix.
--
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/1549455
Title:
Unity8-dash on Intel Atom graphics crashes and restarts continuously
[qtubu
Using simple test apps (lp:~gerboland/+junk/openglwindow &
lp:~gerboland/+junk/qquickwindow-debug), it appears that yes Qt is using
OpenGL 1.4 on X for both raw GL and QtQuick apps.
./qquickwindow-debug
Window format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize
24, redBufferSiz
/me has to stop using "Ok, " at the start of his sentences
--
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/1549455
Title:
Unity8-dash on Intel Atom graphics crashes and restarts continuously
[q
Ok, I suspect I have found the issue. Seems this hardware only supports
OpenGL 1.4 compatibility profile. Qt's EGL code is asking for at least
version 2.0, and so getting no valid context back.
Could you please install "mesa-utils" package and run "glxinfo". On the
hardware I have access to, I see
Ok, I figured out hte EGL issue, it was my misunderstanding. Modifying the
tools to act correctly, I get this for eglinfo:
http://pastebin.ubuntu.com/16686113/
and the qteglchooser correctly chooses a valid Mir EGL config. Why Qt itself
cannot do this, I have yet to understand.
--
You received
Ok, progress, my tools can exhibit the problem:
http://pastebin.ubuntu.com/16677278/
Problems include:
1. libEGL warning: DRI3: xcb_connect failed<- should not be trying that
2. EGL version: 8.-1225087968<- this is garbage
I suspect that there is an issue with EGL.
--
You received this
Forgot to say, that was reproduced running the qteglchooser while there
was no X server running, instead just a Mir server running.
--
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/1549455
Title:
Hey Emanuele,
Albert got me the data I wanted from those tools, and the results are still
inconclusive. I think I need access to the hardware to make real progress on
this. So there's no need to bother with the trying those tools.
If you fancy a go, just to play:
1. Install build dependencies (I
Hi Emanuele,
you attached a branch of mine to this bug - it makes our GL/EGL managing code
more robust. I had hoped it would fix this issue, but unfortunately it doesn't.
That's why I didn't attach that branch to this bug.
Annoyingly I don't have the hardware to hand either, so I'm flying
slight
http://paste.ubuntu.com/16357238/ the output Qt gave me for the failing
eglCreateContext
--
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/1549455
Title:
Qt clients on Intel Pineview graphics fail
Just considering the Dash problem, the crash is a symptom of a bigger
problem: seems qtubuntu is unable to choose or manage the egl config
correctly. If a correct/working egl config was chosen, then this code
path wouldn't be entered (which has the "delete when not created" bug
seen here).
The act
Albert was able to reproduce this on his netbook.
The dash issues we suspect are due to:
https://bugs.launchpad.net/qtubuntu/+bug/1580124
https://bugs.launchpad.net/qtubuntu/+bug/1580118
I suspect also that the poor unity8 performance is due to a GL/GLES mismatch in
unity8. Running unity8 with M
The above fix worked for me.however on reboot my touchpad was not
usable.
I had to run - sudo apt-get install xserver-xorg-input-synaptics - to
restore functionality.
Just FYI in the event someone else runs into this issue.
--
You received this bug notification because you are a member of
I guess this has been abandoned because it's marked as fixed, even
though it's not?
--
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/1432194
Title:
Graphics unstable on Ubuntu
On a fresh install I get the following when trying the above solution on
3.16.0-37-generic.
user@user$ sudo apt-get install xserver-xorg xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. Th
Still the same problem for me on 3.16.0-37-generic after a fresh
install. (But at least now I'm able to boot)
Easily reproducible by opening up Google maps, all text becomes garbled.
Other programs that require slight 3d rendering also cause this issue.
15.04 works fine. I suppose I'll try th
I have this fglrx bug after doing a fresh 14.04.2 install today plus my
open source driver won't recognize my monitor and rates it as 1024x768 ,
please fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.la
Public bug reported:
when i try to run optirun command i take this
gerry@Deep-blue:~$ optirun firefox
[ 74.002117] [ERROR]Cannot access secondary GPU - error: [XORG] (EE)
NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 74.002158] [ERROR]Aborting because fallback
Probably not the same issue, but as of 0.1.2+14.04.20131128.1-0ubuntu2,
xmir fails to start for me. Had to disable xmir to start. Can't find any
obvious error in a log file, suggestions?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
Public bug reported:
Have Apple Macbook pro 8,1. With Trusty devel, very occasionally (i.e.
twice in the last 3 weeks) my trackpad has completely stopped
functioning for no reason I can determine.
>From then on, dmesg is full of these messages:
bcm5974: bad trackpad package, length: 8
Removing
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
Dear Chris, I read the comments in bug 1140716 and installed the kernel from
comment 177. So far, my system runs fine. Thanks!
I will report under the other bug when I will have more experiences with the
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
Dear Chris, thanks a lot for looking into the bug. I am not using Unity,
but Gnome 3. However the same kind of crashes happen if I use unity.
The i915_error_state in /sys/kernel/debug is 0 Bytes, so I canno
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
** Attachment added: "xsession-errors.old-second-crash"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170766/+attachment/3653241/+files/xsession-errors.old-second-crash
--
Y
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
** Attachment added: "parts-of kernlog-syslog-after-first-crash.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170766/+attachment/3653238/+files/parts-of%20kernlog-syslog-
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
I would be very glad if someone could have a look at this bug.
Currently, it is almost impossible to do serious work on this computer
due these complete crashes. Today, I encountered two of them.
Please fin
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
** Attachment added: "Xorg.0.log.old-second-crash"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170766/+attachment/3653240/+files/Xorg.0.log.old-second-crash
--
You receive
*** This bug is a duplicate of bug 1140716 ***
https://bugs.launchpad.net/bugs/1140716
** Attachment added: "syslog-after-second-crash"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170766/+attachment/3653239/+files/syslog-after-second-crash
--
You received th
By the way, over the last week, I also (automatically) sent several
apport-gpu error reports. However, I do not know how I can refer to
these here, because the system does not give me any error handling
number or the like.
--
You received this bug notification because you are a member of Ubuntu-X
Public bug reported:
For about two weeks (I assume one of the driver updates caused the
problem), the Intel GPU X driver crashes several times during a session.
Several times a day, a hard reboot is necessary since everything but the
mouse cursor freezes. It is also not possible to switch to text
This is a serious problem. A fresh install of Ubuntu 12.10 followed by
switching to the Nvidia binary drivers will give you a completely blank
desktop on next reboot. Someone new to Linux will have no idea what to
do.
Steps to reproduce:
1. Do a new, clean install of Ubuntu 12.10, and boot into it
Sorry, I spoke to soon: Switching off subpixel rendering was only a
temporary fix; the problem is suddenly back. Worked for a good while
though (tested a while before posting the previous comment).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
It seems I just ran into this problem on Ubuntu 12.04 (final beta) with
nvidia's binary drivers v295.40, using XFCE. Geany would randomly become
extremely slow, sometimes taking seconds to update the text view.
Whenever this happened, Xorg used 60-100% CPU. Switching off subpixel
rendering in XFCE'
*** This bug is a duplicate of bug 859474 ***
https://bugs.launchpad.net/bugs/859474
I have successfully applied the recommendation in post #9 to my Dell
Inspiron 11z laptop. Thanks a million.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 541492 ***
https://bugs.launchpad.net/bugs/541492
Finally seem to have made progress on this.
First thing I tried was upgrade to to the Maverick kernel (2.6.35-20).
That did not fix it, but I was now getting a "Ubuntu is running in low
graphics..." message
Here's the xorg.conf I settled on - its not perfect but it works.
# For Tecra 8200 with CyberbladeXP + 16MB video RAM + 1400x1050 screen
#
Section "Monitor"
Identifier "Monitor0"
DisplaySize 287 215 # mm
VendorName "TOS"
ModelName"50 Panel"
Ho
I was ok until tonight, when I installed all the latest updates.
Got a crash after rebooting, decided to try the 855gm-fix, so I did
the following in a terminal:-
echo options i915 modeset=0 | sudo tee /etc/modprobe.d/i915-kms.conf
Then did:-
sudo add-apt-repository ppa:glasen/855gm-fix
sudo apt
I was plagued with this same problem after upgrading to 10.04.
Machine is a Dell GX260 with an Intel Corporation 82845G/GL[Brookdale-G]/GE
Chipset Integrated Graphics Device (rev 01)
Random crashes, always required an reboot to recover, got so bad I
stopped using the machine for a while.
Googled
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: ubuntu-docs
1 Install procedure.
2 Ubuntu lucid (development branch) release 10.04 beta 2
3 I expected the installation of Ubuntu to detect my graphics chip
(trident cyberblad
on of 1400x1050.
I'm very impressed with the results. Radience theme combined with the
butterfly background gives a very pleasant working environment.
Gerry
--
trident cyberblade not recognised on install
https://bugs.launchpad.net/bugs/569921
You received this bug notification because you ar
** Also affects: xserver-xorg-video-psb (Ubuntu)
Importance: Undecided
Status: New
--
[hardy+ppa]: In widgets, cannot launch images if moko enabling
https://bugs.launchpad.net/bugs/205852
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xse
55 matches
Mail list logo
