... unfortunately I realized that my problem begins NOT with screensaver
activation, but screen LOCK activation.
During test I switched off the LOCK, this is why my problem seemed to be solved.
I found another bug report which describes my problem:
I had this problem on Ubuntu and Gnome Flashback session manager,
switching to Gnome Shell (Gnome Classic) fixes this for me. Can anyone
confirm?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
This bug was fixed in the package xorg-server - 2:1.17.3-2ubuntu1
---
xorg-server (2:1.17.3-2ubuntu1) xenial; urgency=medium
[ Robert Ancell ]
* debian/patches/xmir.patch:
- Update to latest version
* debian/patches/xmir-rootless.patch:
- Merged into xmir.patch
[
Alex N., it will help immensely if you filed a new report with Ubuntu via a
terminal:
ubuntu-bug xorg
Please ensure you have the package xdiagnose installed, and that you
click the Yes button for attaching additional debugging information.
Also, please feel free to subscribe me to it.
**
vilbara, could you please test for this via http://cdimage.ubuntu.com
/daily-live/current/ and advise to the results?
** Changed in: xorg (Ubuntu)
Importance: Low => Medium
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
Public bug reported:
When trying to switch users, desktop computer hangs with blank screen.
It doesn't always happen when switching user. Freeze occurs immediately
i.e. dose not display anything else before hanging.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
@Philip Gemmell
Not sure if the open source driver blacklist has made it into the fix
yet - this caused my screen to be blank after updating.
See previous comments #114 #119 and #120.
I didn't need to change nomodeset, but I did need to add "blacklist
amdgpu" to the end of
On 11-11-15 13:58:08, Philip Gemmell wrote:
> After my update, I had my computer freezing after starting lightdm.
> Going through recovery, I purged lightdm and xorg, so I could at least
> get to work with a tty terminal.
>
> After having followed the instructions on adding wily-proposed to my
>
Just discovered something while working on bug 1513815
Basically, i was running pd on N4 set this env variable
SAL_USE_VCLPLUGIN=gen
which according to bjoern "forces LO to ignore the gtk plugin and uses the old
and trusty X11-only backend" ...figure this is true for all Xapps?
anyhow, i
Thanks, that fixed that problem - I installed fglrx-updates/wily-
proposed fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-
proposed without any further problems, and also reinstalled lightdm,
xorg and ubuntu-desktop. Unfortunately, this is leading to a blank
screen on start-up - I
Hannes Bochmann, to clarify, if you reduce the setup from three monitors
to only two monitors simultaneously, is the flickering still
reproducible?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
After my update, I had my computer freezing after starting lightdm.
Going through recovery, I purged lightdm and xorg, so I could at least
get to work with a tty terminal.
After having followed the instructions on adding wily-proposed to my repository
list (using only command line arguments and
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511244
Title:
Mouse pointer flickers at using DisplayLink
To manage notifications about this bug go to:
(In reply to Andy Furniss from comment #81)
> Recently needed to re-locate and while doing so updated to 4.1.10 = hard
> lock after 7 days uptime. The kernel was not the only difference as I
> attached a usb printer and so have usb module and cups running now, though
> the printer had been off
The notes for 4.2.6 claim to fix one problem that causes GPU locks.
When I added the incremental patch set, the longest it ran was about an
hour (usually it froze within 5 minutes.) I had just stopped a 6 day
run (24/7) on my (ASUS baytrail) T100 specific 4.2.5 kernel (no args,
50% GPU cap) (with
(In reply to John from comment #99)
> To cap frequency I read the max (779 for mine) from
>
> cat /sys/class/drm/card0/gt_max_freq_mhz
>
> To set pick a lower value (as root)
>
> echo 423 > /sys/kernel/debug/dri/0/i915_max_freq
I have a Z3735F baytrail tablet running Debian 8 with a 1 month
(In reply to Andy Furniss from comment #109)
> (In reply to Andy Furniss from comment #81)
>
> Still up OK after 20 days back on 4.1.1.
>
> Strange that 4.1.10 seems to be a regression, there don't seem to be any
> obvious power related i915 commits between the two. Though as I am headless
> I
hi, this is still happening (ubuntu 14.04.3). my system is crashing very
often and the log says always the same:
17 Nov 11 10:53:03 Paula gnome-session[2022]: WARNING: Application
'compiz.desktop' killed by signal 6
18 Nov
No it's not reproducible if I turn off the 3rd monitor which is
connected through DisplayLink.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511244
Title:
Mouse pointer flickers at using
penalvch, thank you for your help.
I don't want to risk a BIOS update for now, so I cannot tell you if the
bug is somehow BIOS-related.
Instead, I have decided to try an update of my graphics drivers using this repo:
ppa:oibaf/graphics-drivers
This "fixes" the crash problem.
So, while it may
Hannes Bochmann, as per
http://support.displaylink.com/knowledgebase/articles/641668-known-
issues-with-displaylink-ubuntu-support only two HD monitors are
officially supported.
Despite this, you may be able to seek support from DisplayLink anyways
following
** Changed in: xorg (Ubuntu)
Milestone: ubuntu-15.04 => None
** Changed in: xorg (Ubuntu Vivid)
Milestone: ubuntu-15.04 => None
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1436952
Same problem with Intel video and Mesa Driver.
--
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/1341037
Title:
Xorg crashed with SIGABRT in OsAbort()
To manage notifications about this
Roger or anyone else affected, there has been a new upload since your
comment #114. The packages in wily-proposed should now blacklist amdgpu.
It would be good if you could verify that it is fixed in bug #1510573.
Please follow the test case and instructions in the bug and mention the
version of
** Changed in: linux (Ubuntu)
Milestone: ubuntu-14.04.3 => None
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Public bug reported:
After I updated to linux 4.2.0.18 Unity becomes very slow and the system
starts to show a high load. Compiz i eating almost all CPU. I'm using
the nouveau driver.
If I return to 4.2.0.7 everything returns to normal.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package:
Only one monitor is plugged into the DisplayLink docking station so I
think the limitation of two monitors is not the problem. If I deactivate
the internal laptop monitor or the monitor plugged directly into the
laptop nothing changes. The mouse keeps flickering on the monitor that
is not
Public bug reported:
VLC doesn't show all frames in a movie, or shows nothing with fglrx-updates
driver.
Before installing fglrx-updates, there was no problem with the
xserver-xorg-video-ati driver.
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517147/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517145/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517144/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517148/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517140/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517138/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Public bug reported:
I just happened, nothing special. Using chrome, typing into the omnibar
to search on Google, and Xorg crashes. No crash on normal domain input.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517143/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517141/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517137/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517151/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517155/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517139/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517142/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517153/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517146/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517150/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517154/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517156/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517149/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517157/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517158/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517159/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517160/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1515368/+attachment/4517152/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
** Also affects: vlc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1515368
Title:
VLC doesn't show all frames in a movie, or
A (bad) workaround is to map the buffer server-side, and then use
glTexImage2D (instead of glTargetTexture2D)
--
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/1406725
Title:
Severe
External indication that adreno drivers have an issue flushing their
texture caches: https://codereview.chromium.org1241433003/
--
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/1406725
Its seeming like the gpu-facing cache is the one that needs invalidation
from the GL/gralloc driver, but is not being flushed. This is a CPU/GPU
coordination issue, and the GPU-based scenarios all work through the
same cache and do not experience this problem. If we use overlays, this
is not an
Hi,
To test this PC I reinstalled lubuntu 15.10 64-bit and used Synaptic
Package manager to install a few bits and pieces.
The PC is behaving much better now and graphics are OK.
Just in time to be given away to a friend who's PC's hard drives has failed
:)
BW,
Ian
--
-- ACCU -
On 11 November 2015 at 19:36, Ian Bruntlett
wrote:
> To test this PC I reinstalled lubuntu 15.10 64-bit and used Synaptic
> Package manager to install a few bits and pieces.
>
> The PC is behaving much better now and graphics are OK.
>
PC graphics are still misbehaving.
the full computer model that I found is: Samsung np-r540-ja07pl
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1512454
Title:
Refresh change colours
To manage notifications about this bug go
This LTS Enablement Stack scares me a lot; I do not want to screw my
system. So if I understand you correctly, I should return to my
previous state with the following command, right?
sudo apt-get remove linux-generic-lts-vivid xserver-xorg-core-lts-vivid
xserver-xorg-lts-vivid
I tried the Live version of Ubuntu 16.04 and installed the DisplayLink
driver. But I couldn't even select the third monitor which is plugged in
through DisplayLink. So I can't tell if the problem exists there too as
the driver for the video output via DisplayLink seems not to work. At
least I
62 matches
Mail list logo