Michal Moravcik, it will help immensely if you filed a new report with Ubuntu
by ensuring you have the package xdiagnose installed, and that you click the
Yes button for attaching additional debugging information running the following
from a terminal:
ubuntu-bug xorg
Also, please feel free to s
Emanuel, it will help immensely if you filed a new report with Ubuntu by
ensuring you have the package xdiagnose installed, and that you click the Yes
button for attaching additional debugging information running the following
from a terminal:
ubuntu-bug xorg
Also, please feel free to subscribe
Nicolas Jungers, could you please capture a failed boot log while using
the latest mainline kernel (4.8-rc8) via
https://wiki.ubuntu.com/DebuggingKernelBoot ?
** Tags removed: kernel-bug-exists-upstream-4.8-rc5
** Tags added: kernel-bug-exists-upstream-4.8-rc8 oneiric precise quantal raring
--
Y
Robert Unverzagt, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608112/comments/3
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yello
grgtvs, to clarify, when I ask about testing results (in newer or older
releases) I'm referring to the PC you originally reported against (Dell
XPS L521X) not some other PC you used.
Hence, could you please answer my questions in that context?
Also, to see if this is already resolved, could you p
I upgraded from Trusty to Xenial. Before the upgrade, the compose key was
working in all applications, except maybe Torchat (which I hadn't used for
months before the upgrade). After the upgrade:
*Konqueror works properly when I use the Dvorak layout and the compose key. If,
however, I switch to
Erik, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1604867/comments/4
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and t
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1607337
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1608112
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
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/1607375
Sounds like this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=85064
** Bug watch added: freedesktop.org Bugzilla #85064
https://bugs.freedesktop.org/show_bug.cgi?id=85064
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
ht
Please see XorgLog.txt for error message.
I worked with same configuration for month or two, and the problems
started after restart yesterday.
** Summary changed:
- X server stopped loading
+ X server stopped loading with "Number of created screens does not match
number of detected devices."
-
Public bug reported:
Basically, it says that "number of created screens does not match number
of detected devices."
I tinkered with Nvidia drivers, and re-installed xorg without any
success.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4
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
Fix needs to be released to 14.04.05 LTS HWE as well
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: Vassil Peytchev (vassil-peytchev) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubunt
Fix needs to be released to 14.04.05 LTS HWE as well
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Vassil Peytchev (vassil-peytchev)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubunt
This happened on my Dell M3800 with the Optimus Nvidia GPU and nvidia-
prime when updating to the 14.04.5 LTS HWE.
The workaround I used was to force the modesetting driver in xorg.config
for the Intel GPU, and not allow changes to xorg.config (see
https://vxlabs.com/2015/02/05/solving-the-ubuntu-
Zisu Andrei, do you have some instructions/link/whatever to solve this
manually under ElementaryOS Freya?
Thanks
On Thu, Sep 29, 2016 at 4:14 PM, Zisu Andrei <1568...@bugs.launchpad.net>
wrote:
> Hey Wolf,
>
> I believe this has been fixed in Loki (I wouldn't know, I'm running with
> oibaf's Int
Sorry I haven'r seen you comment.
As per your 1st question - I don't know that since I've only tried using
3 screens in 16.04, prior to that I had a desktop setup (11.04 to 14.04)
with 2 screens without any problems, either using the nvidia drivers
either the nouveau.
Regarding the nvidia propert
Hey Wolf,
I believe this has been fixed in Loki (I wouldn't know, I'm running with
oibaf's Intel drivers). The issue exsists in Freya since, I believe
there was some update to 12.04 LTS's drivers.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I also want to confirm that this link solution works for me! (I have a
Nvidia GT610 with prop drivers also.)
sudo ln -s /usr/lib/nvidia-361/libGLX_nvidia.so.361.42 /usr/lib/x86_64
-linux-gnu/libGLX_indirect.so.0
Couldn't for the life of me figure out why apps worked on the console,
but not via X
Bug maintainers: Looks like this should be marked as "Confirmed" for
elementary OS and not "Fix released" based on the past few comments...
--
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
Forgot to mention I am running
GeForce 9800 GT with driver: Nvidia 340.96
Ubuntu 16.04.1 with latest updates/patches
Linux 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux
compiz 0.9.12.2+16.04.20160823-0ubuntu1
--
You received this bug notification beca
I also just bumped into this issue.
That's what's written in my log:
Sep 29 12:28:09 mycoolpc kernel: [14246.377138] NVRM: Xid (PCI::01:00): 13,
Graphics Exception: ChID 0003, Class 8297, Offset 15e0, Data
I will disable x11-sync for now and see how this is going.
If someon
Public bug reported:
Both Chrome and Firefox actually were extremely slow regarding visual
update (1 second after clicking a tab, lagging when entering text).
Examining this old report: https://bugs.launchpad.net/ubuntu-
gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
framebuffer
** Changed in: webkit2gtk (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1615871
Title:
Poor performance with WebKit on yakkety with
not an X bug, reassigning
and my use case for getting "<|>" on an US layout is actually already
available via altgr-shift-{8,9,i}, so I don't need hacks anymore
but I think you can drop your custom layouts in /etc/X11/xkb(/symbols?),
clean up the cache in /var/lib/xkb and restart the server.. may
27 matches
Mail list logo
